Conversation
The subtype tables repeated their own type as a column, pinned with a DEFAULT and a CHECK, which the table name already said. They now carry only the basetype's key and their own foreign key. The basetype's owner_type draws from an enumerable table rather than a CHECK list, so admitting a new type is an INSERT. Exclusivity between subtypes is no longer enforced in Postgres as a result, and the page says so rather than claiming otherwise; T-SQL can still enforce it with cross-table constraints. The quoted delete error matches the constraint Postgres reports now. Also drops the closing tool section, which ended an argument about data modelling on a feature list, and cuts the stock phrasing and contrastive reveals throughout.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.