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
There are 4 tables that have children through inheritance.
note
file_base
translation
file_secondary_attachment
There does not seem clear reasons why inherited tables are used. Covert all to regular tables. Then convert the used serial columns to use IDENTITY.
The reason for this is for clarity and improved code quality. Table inheritance is is often misunderstood.
From the Postgres docs, "Unique constraints and primary keys are not inherited in the current implementation. This makes the combination of inheritance and unique constraints rather dysfunctional."
The text was updated successfully, but these errors were encountered:
For files, I would like to change the design: to have one central file storage table with link tables to attach the files to other entities. This allows deduplication of files linked to more than one entity.
It will also remove the need for file_secondary_attachment.
For files, I would like to change the design: to have one central file storage table with link tables to attach the files to other entities. This allows deduplication of files linked to more than one entity. It will also remove the need for file_secondary_attachment.
I have not looked at the details yet, but that is inline with my first impressions.
There are 4 tables that have children through inheritance.
There does not seem clear reasons why inherited tables are used. Covert all to regular tables. Then convert the used serial columns to use IDENTITY.
The reason for this is for clarity and improved code quality. Table inheritance is is often misunderstood.
From the Postgres docs, "Unique constraints and primary keys are not inherited in the current implementation. This makes the combination of inheritance and unique constraints rather dysfunctional."
The text was updated successfully, but these errors were encountered: