Results for “Input streams & redirection”
Small, practical examples. Search by task or narrow things down below.
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 upstream tracked by the current branch
Git: The upstream shorthand resolves the configured remote-tracking branch.
Git✓ 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
Receive a result from a goroutine
Receive a result from a goroutine using a complete Go program with explicit sample inputs.
Go✓ Tested
Recognize an untracked file
Git: Recognize an untracked file inside the disposable repository created by the input setup.
Git✓ 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
Reference a parent identified by two columns
SQLite: A composite foreign key checks the complete referenced key rather than either column independently.
SQLite✓ Tested