Skip to main content Module starts_with Copy item path Source starts_with_case_sensitive starts_with is case-sensitive: a lowercase prefix must not match records
whose values only start with the uppercase equivalent. starts_with_empty_prefix starts_with with an empty prefix — DynamoDB rejects empty string key values. starts_with_empty_prefix_sql starts_with with an empty prefix on SQL — lowers to LIKE ‘%’, matches all rows. starts_with_no_match starts_with with a prefix that matches nothing — returns empty result. starts_with_non_key_attr starts_with on a non-key attribute. On DynamoDB this uses FilterExpression;
on SQL: SQLite/Turso use GLOB, MySQL uses BINARY LIKE, PostgreSQL uses ^@. starts_with_optional_field starts_with on an Option<String> field — matches non-null values with
the given prefix; rows with NULL values are excluded. starts_with_partition_key_error starts_with on the partition key — on scan-capable drivers (DynamoDB) this
falls back to a table scan with a begins_with filter and succeeds; on
non-scan NoSQL drivers it returns an error. starts_with_sort_key starts_with on the sort key. On DynamoDB this uses KeyConditionExpression;
on SQL: SQLite/Turso use GLOB, MySQL uses BINARY LIKE, PostgreSQL uses ^@. starts_with_special_chars starts_with prefix containing LIKE wildcards (%, _) and the escape
char (!). These must match literally on all backends.