Results for “Input constraints”
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 a repository-specific configuration value
Git: The local scope makes configuration lookup predictable for this practice repository.
Git✓ Tested
Read a secret from a mounted file
Docker / Compose: Compose secrets make a file available under /run/secrets.
Docker / Compose✓ Tested
Read a tab-separated table
PowerShell: ConvertFrom-Csv accepts an explicit delimiter instead of requiring comma-separated input.
PowerShell✓ Tested
Read a URL’s host and path
Read a URL’s host and path using a complete Go program with explicit sample inputs.
Go✓ Tested
Read an annotated tag’s message
Git: for-each-ref can inspect annotation contents without including a commit diff.
Git✓ Tested
Read an HTTP query parameter
Read an HTTP query parameter using a complete Go program with explicit sample inputs.
Go✓ Tested
Read an image’s default command
Docker / Compose: Config.Cmd contains the command arguments stored in the image.
Docker / Compose✓ Tested
Read an unpressed button with an internal pull-up
Arduino / C: An open input configured with INPUT_PULLUP reads high.
Arduino / C✓ Tested