Skip to content

Support for != operator on numerical fields #45

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

Jump to bottom
Open
Dannyscholz opened this issue Nov 17, 2023 · 1 comment
Open

Support for != operator on numerical fields #45

Dannyscholz opened this issue Nov 17, 2023 · 1 comment

Comments

@Dannyscholz
Copy link

Current version is lacking support for the != on numerical fields.
@tharropoulos
Copy link
Contributor

tharropoulos commented Apr 8, 2025 •
edited
Loading

The Python client isn't responsible for that. The filter string will be passed as normal to the Typesense Server API.
This means that any string being passed to the filter_by parameter will be valid as far as the client is concerned. You can try it out with a newer version of Typesense to verify that it is the case

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@Dannyscholz @tharropoulos