You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When i create associations between objects and use the sync() method, it generate the tables with the good foreign keys column/attrs on the DBMS side but i didn't see any foreign key References on the table itself when i do a show create table statement.
It means there are no controls from the DBMS regarding any potential foreign key violations during CRUD operations. Thus i don't see any interests to put by default the InnoDB engine as long InnoDB support this feature and this is the main interest to use this engine by default. ( or i totally miss something 😋 )
it is something complicated to implement ? do u need some help to implement it ? is there any PoC about this feature ?
Thx
The text was updated successfully, but these errors were encountered:
Not really a issue but more an observation.
When i create associations between objects and use the sync() method, it generate the tables with the good foreign keys column/attrs on the DBMS side but i didn't see any foreign key References on the table itself when i do a show create table statement.
It means there are no controls from the DBMS regarding any potential foreign key violations during CRUD operations. Thus i don't see any interests to put by default the InnoDB engine as long InnoDB support this feature and this is the main interest to use this engine by default. ( or i totally miss something 😋 )
it is something complicated to implement ? do u need some help to implement it ? is there any PoC about this feature ?
Thx
The text was updated successfully, but these errors were encountered: