Help Center/ GaussDB/ Developer Guide(Distributed_3.x)/ Development and Design Proposal/ Database Object Design/ Constraint Design
Updated on 2024-05-07 GMT+08:00
View PDF
Share

Constraint Design

DEFAULT and NULL Constraints

  • If all the column values can be obtained from services, you are advised not to use the DEFAULT constraint. Otherwise, unexpected results will be generated during data loading.
  • Add NOT NULL constraints to columns that never have NULL values. The optimizer automatically optimizes the columns in certain scenarios.
  • Explicitly name all constraints excluding NOT NULL and DEFAULT.

Unique Constraints

  • The constraint name should indicate that it is a unique constraint, for example, UNIIncluded columns.

Primary Key Constraints

  • The constraint name should indicate that it is a primary key constraint, for example, PKIncluded columns.

Check Constraints

  • The constraint name should indicate that it is a check constraint, for example, CKIncluded columns.
Parent topic: Database Object Design