Skip to content

Update from code changes: double-quoted SQL filter identifiers #345

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
mintlify wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Update from code changes: double-quoted SQL filter identifiers #345

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
17 changes: 17 additions & 0 deletions docs/search/filtering.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -198,6 +198,23 @@ path must be wrapped in backticks.
AND `nested with space`.`inner with space` < 2
```

You can also escape identifiers with SQL-standard double quotes (`"`). LanceDB rewrites
double-quoted identifiers to backticks before running the filter, so the two forms are
equivalent. Single quotes (`'`) always denote string literals, never identifiers.

```sql
"UpperCaseName" = '3' AND "column name with space" IS NOT NULL
```

Double-quoted identifiers work in every operation that accepts a filter: search
filters, row counts, updates, deletes, and merge insert conditions.

<Warning>
In older SDK versions, double-quoted tokens were parsed as string literals. A filter
like `"UpperCaseName" = '3'` compared two strings and silently matched no rows. If you
target older versions, use backticks to escape identifiers.
</Warning>

<Warning>
Field names containing periods (.) are NOT supported.
</Warning>
Expand Down
Loading