public/django-migration-linter
15
0 Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Adding a unique constraint solution correction

Browse Source 
Correct solution to instruct app code to follow unique constraint before db constraint is deployed
This commit is contained in:
jason.lee authored and David Wobrock committed 2023-09-08 15:05:23 +02:00
1 parent 3503367f1f
commit 117967a957
1 file changed
+1 -1
Download Patch File Download Diff File Expand all files Collapse all files
docs/incompatibilities.md
+1 -1
View File
@@ -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 3. rollback your DB to drop the unique constraint, and it should work again
:white_check_mark: **Solutions**: :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 ### :arrow_forward: Importing a model in a RunPython migration