Results for “ps”
Small, practical examples. Search by task or narrow things down below.
Find parents whose every child meets a rule
SQL Server: Combine existence with the absence of a violating child to exclude parents with no children.
SQL Server✓ Tested
Find parents whose every child meets a rule
Postgres: Combine existence with the absence of a violating child to exclude parents with no children.
Postgres✓ Tested
Find parents whose every child meets a rule
SQLite: Combine existence with the absence of a violating child to exclude parents with no children.
SQLite✓ Tested
Find parents with at least two child rows
SQL: Use a correlated count when testing a per-parent threshold.
SQL✓ Tested
Find parents with at least two child rows
SQL Server: Use a correlated count when testing a per-parent threshold.
SQL Server✓ Tested
Find parents with at least two child rows
Postgres: Use a correlated count when testing a per-parent threshold.
Postgres✓ Tested
Find parents with at least two child rows
SQLite: Use a correlated count when testing a per-parent threshold.
SQLite✓ Tested
Find records without any related rows
SQL: NOT EXISTS avoids the NULL pitfalls of NOT IN when the subquery column can be missing.
SQL✓ Tested
Find records without any related rows
SQL Server: NOT EXISTS avoids the NULL pitfalls of NOT IN when the subquery column can be missing.
SQL Server✓ Tested
Find records without any related rows
Postgres: NOT EXISTS avoids the NULL pitfalls of NOT IN when the subquery column can be missing.
Postgres✓ Tested
Find records without any related rows
SQLite: NOT EXISTS avoids the NULL pitfalls of NOT IN when the subquery column can be missing.
SQLite✓ Tested
Generate every combination of two sets
SQL: CROSS JOIN creates one result per possible pair, so the output size is the product of the input sizes.
SQL✓ Tested