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.
Context
migration 0073 is not running in production
this is due to a subtly in the way django creates many-to-many tables.
previously the many to many relationship was established via the
Citation
model that had a foreign key to both thechat_message
andfile
, where there maybe many citations with referencing the samechat_message
andfile
. The django ManyToMany relationship creates a very similar through model but it enforces a uniqueness constraint on the foreign keys which caused the error.Changes proposed in this pull request
chat_message
andfile
, note that this fails with the same error we see in prodcould not create unique index "redbox_core_chatmessage__chatmessage_id_file_id_bd4360c8_uniq"
Guidance to review
Relevant links
Things to check