-
Notifications
You must be signed in to change notification settings - Fork 16
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.
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
Drizzle integration select keys gets overridden by column names #96
Comments
I suspect this is because schemas are not supported yet. db0/src/integrations/drizzle/index.ts Line 15 in 62c0e01
|
Yeah that seems likely. I wouldn't have guessed it was schema support but it seems to be the same kind of thing happening in #70 |
(sorry i'm little bit busy on other projects but in the meantime if anyone want to pick on this to support it is more than welcome ❤️ ) |
@pi0 I am available to work on it. Can I get some pointers on how exactly do you want to implement it? (Assuming something special is needed since it was left as a TODO) |
Nothing special on db0 side but i think we need to:
|
Got it, I will raise a PR and will wait for active feedbacks from your end. |
Just a quick question, might be basic, why are we using SQLite Dialect by default? How does it work when someone uses Postgres for example with drizzle? |
We should add MySQL and Postgres dialect support too indeed. Main goal of current db0 RC was to start with sqlite compatible providers. |
Environment
node: v22.1.0
pnpm: 9.1.4
better-sqlite3: ^11.0.0
db0: ^0.1.4
drizzle-orm: ^0.31.0
Reproduction
https://github.com/Twitch0125/db0-drizzle-select-bug
Describe the bug
I first noticed this in a nuxt project but it seems to be happening using only db0.
when passing an object to
select()
from the db0 drizzle integration it doesn't seem to honor the given keys, unlike using a drizzle instance directly.Additional context
No response
Logs
No response
The text was updated successfully, but these errors were encountered: