samtechie
Migrate an existing database with a column that has a uniqueness constraint and a not-null constraint
Lets say I have an existing database and I want to add a column that has a uniqueness constraint and a non-null constraint. For the non-null constraint a solution would be something like this add :newcolumn, :string, default: "defaultvalue", null: false. But my migration would still not work because of my uniqueness constraint. I was thinking something like default: fragment(now()) but my column has the string datatype. Also, there is the problem that the default is called at compile-time and you might end up with the same value in the records and violating the unique constraint. What is the best way I can solve it?
Marked As Solved
LostKobrakai
Generally the solution is adding the column as nullable, then backfill the contents by whatever means you have to do so, and only in a seconds step make it not nullable. This becomes even more important if you have multiple nodes and rolling deployments, as nodes with the old version might run at the same time as nodes with the new version. There you can only add the “not null” after all nodes have been updated, but the column needs to exist before the first one updates.
Popular in Questions
Other popular topics
Latest on Elixir Forum
Sponsor Spotlight
Supporting innovation across the BEAM ecosystem.
Categories:
Sub Categories:
Forums
Our Sponsors
Build Elixir applications with speed and confidence.
Supporting innovation across the BEAM ecosystem.
We build reliable cloud platforms for business-critical systems.
Catch errors, track performance, monitor hosts and more.
Practical resources that improve the lives of professional developers.
Producing high quality Elixir screencasts since 2017.
Enabling companies to succeed by building software people love.
Courses that'll move you from confusion to "Aha, now I get it!"