[Feature Request] Portable mode: "insensitive" on string comparison (postgresql and sqlite)
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- postgresql, sqlite, typescript
- Domain
- database
Research direction
The starting point is the validation that rejects mode: "insensitive" when the provider is sqlite; find where the query engine checks mode against the dialect and compare it with the postgresql branch that already supports it. Read that validation path first, then the sqlite query translation for string comparison. Done means sqlite either behaves like postgresql or silently accepts/documentedly ignores the option — the issue lists three alternatives and none has been chosen, so confirm the intended one with maintainers before writing code.
Written by the indexing model from the issue text.
Description
Is your feature request related to a problem? Please describe.
As of zenstack 3.6.4 using
mode: "insensitive" for string search is supported with postgresql dialect but not with sqlite dialect (it throws at validation).
IMHO, orm should offer an abstraction for this, or propose to enable one.
I use postgresql for production and sqlite for tests and I want to avoid writing code to test which underlying DB is in use. I think ORM should abstract this for the dev.
Describe the solution you'd like
Possible solutions :
- perform lowercase string comparison on sqlite to achieve the same effect by default
- add a config option to enable lowercase string comparison on sqlite if not enabled by default
- just ignore it, or propose a config option to silently ignore it on sqlite, aka. ignore validation
Describe alternatives you've considered
IDK
Additional context
none
- Dominant language
- TypeScript
- Stars
- 2.9k
- Forks
- 157
- Avg merge
- 11h 42m
- Merged PRs (30d)
- 20
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from zenstackhq/zenstack
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
zenstackhq/zenstack#2873 ·
Maintainers usually reply within 1 day
-
runtime
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
zenstackhq/zenstack#2868 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
zenstackhq/zenstack#2694 · 3 comments ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 68/100
zenstackhq/zenstack#2659 · 2 comments ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
zenstackhq/zenstack#2542 · 1 comment ·
Maintainers usually reply within 1 day
All issues in zenstackhq/zenstack
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 75/100
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
jaegertracing/jaeger-ui#4596 ·
Maintainers usually reply within 1 day
-
area:tui enhancement platform:macos
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
anthropics/claude-code#101490 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
netlify/netlify-mcp#75 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day