Skip to content

Commit

Permalink
Adding a unique constraint solution correction
Browse files Browse the repository at this point in the history
Correct solution to instruct app code to follow unique constraint before db constraint is deployed
  • Loading branch information
jasonlee-alation authored and David-Wobrock committed Sep 8, 2023
1 parent 3503367 commit 117967a
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion docs/incompatibilities.md
Original file line number Diff line number Diff line change
Expand Up @@ -163,7 +163,7 @@ At some point, start using the new column and delete the old one once the migrat
3. rollback your DB to drop the unique constraint, and it should work again

:white_check_mark: **Solutions**:
- Do a multistep deployment. First, make sure that the code is only pushing a value if it is not unique.
- Do a multistep deployment. First, make sure that the code is only pushing a value if it is unique.

### :arrow_forward: Importing a model in a RunPython migration

Expand Down

0 comments on commit 117967a

Please sign in to comment.