Results for “Input constraints”
Small, practical examples. Search by task or narrow things down below.
Undo a multi-row transfer atomically
SQLite: The first transaction commits the fixtures. Rolling back the second transaction restores both sides of the attempted transfer.
SQLite✓ Tested
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
Unstage a file while keeping its contents
Git: Unstage a file while keeping its contents inside the disposable repository created by the input setup.
Git✓ Tested
Update a value through a pointer
Update a value through a pointer using a complete Go program with explicit sample inputs.
Go✓ Tested
Update rows selected by a related table
SQL: Use EXISTS to limit updates based on an independent eligibility table.
SQL✓ Tested
Update rows selected by a related table
SQL Server: Use EXISTS to limit updates based on an independent eligibility table.
SQL Server✓ Tested
Update rows selected by a related table
Postgres: Use EXISTS to limit updates based on an independent eligibility table.
Postgres✓ Tested
Update rows selected by a related table
SQLite: Use EXISTS to limit updates based on an independent eligibility table.
SQLite✓ Tested
Update several classifications in one statement
SQL: A CASE expression computes the new value for each row covered by the update predicate.
SQL✓ Tested