From 117967a957128c3b4d78555e492d5567a9045270 Mon Sep 17 00:00:00 2001 From: "jason.lee" Date: Wed, 6 Sep 2023 15:26:08 -0700 Subject: [PATCH] Adding a unique constraint solution correction Correct solution to instruct app code to follow unique constraint before db constraint is deployed --- docs/incompatibilities.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/incompatibilities.md b/docs/incompatibilities.md index ecff7b3..90a5bf0 100644 --- a/docs/incompatibilities.md +++ b/docs/incompatibilities.md @@ -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