pgroll/examples/16_set_nullable.json

{
  "name": "16_set_nullable",
  "operations": [
    {
      "alter_column": {
        "table": "reviews",
        "column": "review",
        "nullable": false,
        "up": "(SELECT CASE WHEN review IS NULL THEN product || ' is good' ELSE review END)",
        "down": "review"
      }
    }
  ]
}
Implement the set column `NOT NULL` operation (#63) Implement the operation to make an existing column `NOT NULL`. The migration looks like this: ```json { "name": "16_set_not_null", "operations": [ { "set_not_null": { "table": "reviews", "column": "review", "up": "product \|\| ' is good'" } } ] } ``` This migration adds a `NOT NULL` constraint to the `review` column in the `reviews` table. * On `Start`: * Create a new column with a `NOT VALID` `NOT NULL` constraint * Backfill the new column with values from the existing column using the `up` SQL to replace `NULL` values * Create a trigger to populate the new column when values are written to the old column, rewriting `NULLs` with `up` SQL. * Create a trigger to populate the old column when values are written to the new column. * On `Complete` * Validate the `NOT VALID` `NOT NULL` constraint on the new column. * Add `NOT NULL` to the new column. * Remove triggers and the `NOT VALID` `NOT NULL` constraint * Drop the old column * Rename the new column to the old column name. * On `Rollback` * Remove the new column and both triggers. 2023-08-29 16:53:29 +03:00			`{`
fix(#132): consistent naming for nullable columns in migration files (#181) Realated Issue: #132 This PR includes BREAKING CHANGES, existing migrations that add a not null constraint using the `not_null` property will not work anymore. The migration strategy would be to rename those `not_null` fields in `alter_column` operations to `nullable`. 2023-10-11 15:14:34 +03:00			`"name": "16_set_nullable",`
Implement the set column `NOT NULL` operation (#63) Implement the operation to make an existing column `NOT NULL`. The migration looks like this: ```json { "name": "16_set_not_null", "operations": [ { "set_not_null": { "table": "reviews", "column": "review", "up": "product \|\| ' is good'" } } ] } ``` This migration adds a `NOT NULL` constraint to the `review` column in the `reviews` table. * On `Start`: * Create a new column with a `NOT VALID` `NOT NULL` constraint * Backfill the new column with values from the existing column using the `up` SQL to replace `NULL` values * Create a trigger to populate the new column when values are written to the old column, rewriting `NULLs` with `up` SQL. * Create a trigger to populate the old column when values are written to the new column. * On `Complete` * Validate the `NOT VALID` `NOT NULL` constraint on the new column. * Add `NOT NULL` to the new column. * Remove triggers and the `NOT VALID` `NOT NULL` constraint * Drop the old column * Rename the new column to the old column name. * On `Rollback` * Remove the new column and both triggers. 2023-08-29 16:53:29 +03:00			`"operations": [`
			`{`
Move `set_not_null` operation into `alter_column` (#93) Build on #91 and #92 and move the `set_not_null` operation into the `alter_column` operation. The pattern is the same as for the operations already moved: * Update the example migration to use the new operation type * Remove serialization and deserialization logic for the individual operation. * Make the `alter_column` operation construct the right type of 'inner operation'. * Update tests for the foreign key and check constraint ops to use the `alter_column` operation. A migration to set a column `NOT NULL` now looks like: ```json { "name": "16_set_not_null", "operations": [ { "alter_column": { "table": "reviews", "column": "review", "not_null": true, "up": "(SELECT CASE WHEN review IS NULL THEN product \|\| ' is good' ELSE review END)", "down": "review" } } ] } ``` The `not_null` field is currently only allowed to be set `true`, as removing this kind of constraint is currently unsupported. 2023-09-14 07:47:16 +03:00			`"alter_column": {`
Implement the set column `NOT NULL` operation (#63) Implement the operation to make an existing column `NOT NULL`. The migration looks like this: ```json { "name": "16_set_not_null", "operations": [ { "set_not_null": { "table": "reviews", "column": "review", "up": "product \|\| ' is good'" } } ] } ``` This migration adds a `NOT NULL` constraint to the `review` column in the `reviews` table. * On `Start`: * Create a new column with a `NOT VALID` `NOT NULL` constraint * Backfill the new column with values from the existing column using the `up` SQL to replace `NULL` values * Create a trigger to populate the new column when values are written to the old column, rewriting `NULLs` with `up` SQL. * Create a trigger to populate the old column when values are written to the new column. * On `Complete` * Validate the `NOT VALID` `NOT NULL` constraint on the new column. * Add `NOT NULL` to the new column. * Remove triggers and the `NOT VALID` `NOT NULL` constraint * Drop the old column * Rename the new column to the old column name. * On `Rollback` * Remove the new column and both triggers. 2023-08-29 16:53:29 +03:00			`"table": "reviews",`
			`"column": "review",`
fix(#132): consistent naming for nullable columns in migration files (#181) Realated Issue: #132 This PR includes BREAKING CHANGES, existing migrations that add a not null constraint using the `not_null` property will not work anymore. The migration strategy would be to rename those `not_null` fields in `alter_column` operations to `nullable`. 2023-10-11 15:14:34 +03:00			`"nullable": false,`
Allow the set `NOT NULL` operation to take `down` SQL (#85) For consistency with other operations, flexibility and the ability to more easily combine operations into one 'alter column' operation, allow the set `NOT NULL` operation to take user-supplied`down` SQL to be run when moving values from the new to the old schema. Previously, the `down` SQL was assumed to be just a straight copy of the value from the new to the old column. 2023-09-11 12:57:51 +03:00			`"up": "(SELECT CASE WHEN review IS NULL THEN product \|\| ' is good' ELSE review END)",`
			`"down": "review"`
Implement the set column `NOT NULL` operation (#63) Implement the operation to make an existing column `NOT NULL`. The migration looks like this: ```json { "name": "16_set_not_null", "operations": [ { "set_not_null": { "table": "reviews", "column": "review", "up": "product \|\| ' is good'" } } ] } ``` This migration adds a `NOT NULL` constraint to the `review` column in the `reviews` table. * On `Start`: * Create a new column with a `NOT VALID` `NOT NULL` constraint * Backfill the new column with values from the existing column using the `up` SQL to replace `NULL` values * Create a trigger to populate the new column when values are written to the old column, rewriting `NULLs` with `up` SQL. * Create a trigger to populate the old column when values are written to the new column. * On `Complete` * Validate the `NOT VALID` `NOT NULL` constraint on the new column. * Add `NOT NULL` to the new column. * Remove triggers and the `NOT VALID` `NOT NULL` constraint * Drop the old column * Rename the new column to the old column name. * On `Rollback` * Remove the new column and both triggers. 2023-08-29 16:53:29 +03:00			`}`
			`}`
			`]`
			`}`