Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Database Schema #142

Open
ovflowd opened this issue Sep 18, 2016 · 4 comments
Open

Database Schema #142

ovflowd opened this issue Sep 18, 2016 · 4 comments

Comments

@ovflowd
Copy link
Owner

ovflowd commented Sep 18, 2016

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)..

@ovflowd
Copy link
Owner Author

ovflowd commented Sep 18, 2016

Observation: NHibernate spend a really expansive time to create the Database Schema..

@BurakDev
Copy link
Collaborator

I think database schema is going on wrong way, a lot of useless tables.

@ovflowd
Copy link
Owner Author

ovflowd commented Sep 20, 2016

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.

@TheDoct0r11
Copy link
Collaborator

Please read up on OOP Inheritance Mapping:
http://nhibernate.info/doc/nhibernate-reference/inheritance.html

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

3 participants