diff options
Diffstat (limited to 'doc/development/database/constraint_naming_convention.md')
| -rw-r--r-- | doc/development/database/constraint_naming_convention.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/development/database/constraint_naming_convention.md b/doc/development/database/constraint_naming_convention.md index debf74d3b40..3faef8aee09 100644 --- a/doc/development/database/constraint_naming_convention.md +++ b/doc/development/database/constraint_naming_convention.md @@ -9,7 +9,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w The most common option is to let Rails pick the name for database constraints and indexes or let PostgreSQL use the defaults (when applicable). However, when needing to define custom names in Rails or working in Go applications where no ORM is used, it is important to follow strict naming conventions to improve consistency and discoverability. The table below describes the naming conventions for custom PostgreSQL constraints. -Please note that the intent is not to retroactively change names in existing databases but rather ensure consistency of future changes. +The intent is not to retroactively change names in existing databases but rather ensure consistency of future changes. | Type | Syntax | Notes | Examples | |--------------------------|---------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------| |