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
I see the Emulator updating the Schema, and we have a tons of tables. Are the Database schema in correct way? Since we have, as an example, an unique table for each Catalogue Page Layout (omg)..
The text was updated successfully, but these errors were encountered:
I think the way how NHobernate is Creator the schema is wrong... We have really a lot of tables. Some tables in my opinion need to be columns from tables. A lot of foreign keys also are created. This make the database more heavy.
There are basically two ways to map OOP Inheritance:
Table per Subclass or Table per Hierarchie. The problem with TPH is that it would force us to allow NULL values.
I see the Emulator updating the Schema, and we have a tons of tables. Are the Database schema in correct way? Since we have, as an example, an unique table for each Catalogue Page Layout (omg)..
The text was updated successfully, but these errors were encountered: