Update collect tables #5
Draft
Conversation
This file contains 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
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.
***** Work in progress
This is a draft PR in order for EMLO-Collect to be compatible with the new EMLO-Site Edit .
Although we have put great emphasis on keeping the database schema as intact as possible, some changes have been necessary.
A change has been made to all the entity Collect tables to add a single, standard
idcolumn.The reason for this change is that the primary key in the old database was a composite key and Django does not support composite primary keys.
The problem is that, although SQL obviously will support composite keys, Django needs a primary key for various methods.