Check constraint: Difference between revisions

Revision as of 06:43, 24 February 2023

Revision as of 19:59, 21 November 2023

Line 4:

For example, in a table containing products, one could add a check constraint such that the price of a product and quantity of a product is a non-negative value:

PRICE price >= 0

QUANTITY quantity >= 0

If these constraints were not in place, it would be possible to have a negative price (−$30) or quantity (−3 items).

Line 16:

Each check constraint has to be defined in the <code>CREATE TABLE</code> or <code>ALTER TABLE</code> statement using the syntax:

CREATE TABLE ''table_name'' (

...,

CONSTRAINT ''constraint_name'' CHECK ( ''predicate'' ),

...

)

ALTER TABLE ''table_name''

ADD CONSTRAINT ''constraint_name'' CHECK ( ''predicate'' )

If the check constraint refers to a single column only, it is possible to specify the constraint as part of the column definition.

CREATE TABLE ''table_name'' (

...

''column_name'' ''type'' CHECK ( ''predicate'' ),

...

)

==NOT NULL constraint==

A <code>NOT [[Null (SQL)|NULL]]</code> constraint is functionally equivalent to the following check constraint with an <code>IS NOT NULL</code> predicate:

CHECK (''column'' IS NOT NULL)

Some [[relational database management system]]s are able to optimize performance when the <code>NOT NULL</code> constraint syntax is used as opposed to the <code>CHECK</code> constraint syntax given above.<ref>PostgreSQL 13 Documentation, Chapter 5. ''Data Definition'', Section 5.4.2. ''Not-Null Constraints'', Website: https://www.postgresql.org/docs/13/ddl-constraints.html, Accessed on Jan 9, 2021</ref>