Results for “fresh”
Small, practical examples. Search by task or narrow things down below.
Reference a parent identified by two columns
SQL: A composite foreign key checks the complete referenced key rather than either column independently.
SQL✓ Tested
Reference a parent identified by two columns
SQL Server: A composite foreign key checks the complete referenced key rather than either column independently.
SQL Server✓ Tested
Reference a parent identified by two columns
Postgres: A composite foreign key checks the complete referenced key rather than either column independently.
Postgres✓ Tested
Reference a parent identified by two columns
SQLite: A composite foreign key checks the complete referenced key rather than either column independently.
SQLite✓ Tested
Reject a negative quantity with CHECK
SQL: Combine NOT NULL and CHECK because an unknown NULL check result is normally accepted.
SQL✓ Tested
Reject a negative quantity with CHECK
SQL Server: Combine NOT NULL and CHECK because an unknown NULL check result is normally accepted.
SQL Server✓ Tested
Reject a negative quantity with CHECK
Postgres: Combine NOT NULL and CHECK because an unknown NULL check result is normally accepted.
Postgres✓ Tested
Reject a negative quantity with CHECK
SQLite: Combine NOT NULL and CHECK because an unknown NULL check result is normally accepted.
SQLite✓ Tested
Reject duplicate business identifiers
SQL: A UNIQUE constraint protects a business key independently of the primary key.
SQL✓ Tested
Reject duplicate business identifiers
SQL Server: A UNIQUE constraint protects a business key independently of the primary key.
SQL Server✓ Tested
Reject duplicate business identifiers
Postgres: A UNIQUE constraint protects a business key independently of the primary key.
Postgres✓ Tested
Reject duplicate business identifiers
SQLite: A UNIQUE constraint protects a business key independently of the primary key.
SQLite✓ Tested