Results for “persistent data”
Small, practical examples. Search by task or narrow things down below.
Read the next row’s value
Postgres: LEAD reads a later ordered row without a self join and supports a fallback at the end.
Postgres✓ Tested
Read the next row’s value
SQLite: LEAD reads a later ordered row without a self join and supports a fallback at the end.
SQLite✓ Tested
Read the smallest and largest values
SQL: Use MIN and MAX without sorting and fetching every row.
SQL✓ Tested
Read the smallest and largest values
SQL Server: Use MIN and MAX without sorting and fetching every row.
SQL Server✓ Tested
Read updated base-table values through a view
SQL: An ordinary view reflects later changes to its underlying data.
SQL✓ Tested
Read updated base-table values through a view
SQL Server: An ordinary view reflects later changes to its underlying data.
SQL Server✓ Tested
Read updated base-table values through a view
Postgres: An ordinary view reflects later changes to its underlying data.
Postgres✓ Tested
Read updated base-table values through a view
SQLite: An ordinary view reflects later changes to its underlying data.
SQLite✓ Tested
Read values generated by INSERT
Capture an IDENTITY value with OUTPUT.
OUTPUT✓ Tested
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