summaryrefslogtreecommitdiff
path: root/doc/development/database/not_null_constraints.md
diff options
context:
space:
mode:
Diffstat (limited to 'doc/development/database/not_null_constraints.md')
-rw-r--r--doc/development/database/not_null_constraints.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/development/database/not_null_constraints.md b/doc/development/database/not_null_constraints.md
index 9d1850f5504..48b198b46bd 100644
--- a/doc/development/database/not_null_constraints.md
+++ b/doc/development/database/not_null_constraints.md
@@ -175,7 +175,7 @@ class CleanupEpicsWithNullDescription < ActiveRecord::Migration[6.0]
end
```
-#### Validate the text limit (next release)
+#### Validate the `NOT NULL` constraint (next release)
Validating the `NOT NULL` constraint will scan the whole table and make sure that each record is correct.
@@ -201,7 +201,7 @@ end
## `NOT NULL` constraints on large tables
-If you have to clean up a text column for a [high-traffic table](../migration_style_guide.md#high-traffic-tables)
+If you have to clean up a nullable column for a [high-traffic table](../migration_style_guide.md#high-traffic-tables)
(for example, the `artifacts` in `ci_builds`), your background migration will go on for a while and
it will need an additional [background migration cleaning up](../background_migrations.md#cleaning-up)
in the release after adding the data migration.