Results for “Commit history & revision selection”
Small, practical examples. Search by task or narrow things down below.
Read a page after a known unique key
SQL: A keyset predicate avoids scanning and discarding an increasing offset on a suitable index.
SQL✓ Tested
Read a page after a known unique key
SQL Server: A keyset predicate avoids scanning and discarding an increasing offset on a suitable index.
SQL Server✓ Tested
Read a page after a known unique key
Postgres: A keyset predicate avoids scanning and discarding an increasing offset on a suitable index.
Postgres✓ Tested
Read a page after a known unique key
SQLite: A keyset predicate avoids scanning and discarding an increasing offset on a suitable index.
SQLite✓ Tested
Read the final array item with a negative index
JavaScript: at supports negative positions counted from the end.
JavaScript✓ Tested
Read the final array item with a negative index
TypeScript: at supports negative positions counted from the end.
TypeScript✓ Tested
Report duplicate business values and their frequency
SQL: Group by a candidate business key and retain only groups with multiple rows.
SQL✓ Tested
Report duplicate business values and their frequency
SQL Server: Group by a candidate business key and retain only groups with multiple rows.
SQL Server✓ Tested
Report duplicate business values and their frequency
Postgres: Group by a candidate business key and retain only groups with multiple rows.
Postgres✓ Tested
Report duplicate business values and their frequency
SQLite: Group by a candidate business key and retain only groups with multiple rows.
SQLite✓ Tested
Return all rows tied for the maximum in a group
SQL: An equality comparison with a grouped maximum retains ties rather than choosing one arbitrary row.
SQL✓ Tested
Return all rows tied for the maximum in a group
SQL Server: An equality comparison with a grouped maximum retains ties rather than choosing one arbitrary row.
SQL Server✓ Tested