Results for “Schema design & transactions”
Small, practical examples. Search by task or narrow things down below.
Undo only the work after a savepoint
SQL: After committing the fixtures, roll back a trial change while keeping earlier work in the second transaction.
SQL✓ Tested
Undo only the work after a savepoint
SQL Server: After committing the fixtures, roll back a trial change while keeping earlier work in the second transaction.
SQL Server✓ Tested
Undo only the work after a savepoint
Postgres: After committing the fixtures, roll back a trial change while keeping earlier work in the second transaction.
Postgres✓ Tested
Undo only the work after a savepoint
SQLite: After committing the fixtures, roll back a trial change while keeping earlier work in the second transaction.
SQLite✓ Tested
Initialize structure fields by name
C: Designated initializers make field assignments independent of their declaration order.
C✓ Tested
Accept either of two conditions
Postgres: Use OR to keep matching names or out-of-stock rows.
Postgres✓ Tested
Add an interval to a date
Perform calendar arithmetic with an interval literal.
INTERVAL✓ Tested
Add values across several rows
Postgres: Use SUM to calculate a total quantity.
Postgres✓ Tested
Apply a default when an insert omits a column
SQL: A default supplies an omitted value; an explicit NULL still follows the column’s nullability rules.
SQL✓ Tested
Apply a default when an insert omits a column
SQL Server: A default supplies an omitted value; an explicit NULL still follows the column’s nullability rules.
SQL Server✓ Tested
Apply a default when an insert omits a column
Postgres: A default supplies an omitted value; an explicit NULL still follows the column’s nullability rules.
Postgres✓ Tested
Apply a default when an insert omits a column
SQLite: A default supplies an omitted value; an explicit NULL still follows the column’s nullability rules.
SQLite✓ Tested