- Generation of the models using the
- Adding elements to a junction table that has additional fields
The technical issue/limitation is the following:
Many-to-many relationships (with a junction table) are not detected properly, and as a result the two sides of the relationship get a
HasMany with the junction table instead of a
BelongsToMany with the other side of the relationship.
This only occurs if the junction table has additional fields, while the documentation specifies:
We detect Many-to-Many relationships when we detect a simple junction table. We are able to detect a junction table when it contains 2 foreign keys. It can optionally contain additional fields like a primary key and technical timestamps.
It is not clear from the documentation if this is restricted to "primary key"and “timestamps” fields, and I don’t see any reason for not having additional fields in the relationship.
The real impact from having the
HasMany instead of the
BelongsToMany relationship is the following:
When creating new entries in the junction table collection, we either have to specify both the related elements and their ids, “Member” and “Member id” / “Proposal” and “Proposal id”, (when keeping the default generated models):
Or if we manually remove the “memberId” and “proposalId” from the generated model, we get an "Id’ field, automatically added to the schema while not being in the model, that blocks creation as there is no id field on the db (and that seems to result from the
Only having the “Member” and “Proposal” fields on the UI when adding an element, without the “Member id” and “Proposal id”, and also not having that “Id” field that doesn’t correspond to anything.
This would be either by generating the
BelongsToMany relations instead of
HasMany, if that makes sense or in some other way if it doesn’t make sense to do so.
- Project name: Collective.work
- Team name: Admin
- Environment name: Production or Preprod (both have the case where we have to specify both the element and its id in two different fields)
- Agent type & version: forest-express-sequelize 8.5.3 (Got the issue on 8.2.2, and updated to the latest in case it was a bug that was fixed)