Results for “portable paths”
Small, practical examples. Search by task or narrow things down below.
Insert a row with named columns
Add a record without relying on implicit column order.
INSERT✓ Tested
Insert only keys absent from a destination
SQL: NOT EXISTS supports a set-based missing-row insert in a single-writer example.
SQL✓ Tested
Inspect changes to a container’s writable layer
Docker / Compose: diff marks added, changed, and deleted filesystem paths.
Docker / Compose✓ Tested
Join a parent to pre-aggregated totals
SQL: Aggregate the child rows first to produce at most one joined row per parent.
SQL✓ Tested
Join related rows from two tables
SQL: Match a category key to its display label with an explicit join condition.
SQL✓ Tested
Join through a lookup table
SQL: Use explicit aliases and join keys when enriching records through two relationships.
SQL✓ Tested
Keep children while clearing a deleted relationship
SQL: ON DELETE SET NULL requires a nullable foreign-key column.
SQL✓ Tested
Keep parent rows while filtering joined children
SQL: Put a child filter in ON when unmatched parents must remain in the result.
SQL✓ Tested
Keep rows matching a condition
SQL: Use WHERE to select rows with a particular category.
SQL✓ Tested
Keep unmatched rows with LEFT JOIN
Show every product even when stock is missing.
LEFT JOIN✓ Tested
Label rows with CASE
Derive a readable label from a condition.
CASE✓ Tested
List changed files without the full diff
Inspect affected paths before staging.
diff✓ Tested