kysely-bun-worker and kysely-bun-sqlite are two different dialects that work with bun:sqlite. However, internally the naming used for the kysely-bun-worker dialect is called bun-sqlite. At first glance the name implies that kysely-bun-sqlite is what is used internally. It took me sometime to figure out why my setup wasn't working because of this confusion.
In my app I am using kysely-bun-sqlite and I am unable to use codegen. I'd like to propose we rename the current dialect from bun-sqlite to bun-sqlite-worker and include the kysely-bun-sqlite dialect to avoid future confusion.
Upvote & Fund
We're using Polar.sh so you can upvote and help fund this issue.
We receive the funding once the issue is completed & confirmed by you.
Thank you in advance for helping prioritize & fund our backlog.
kysely-bun-worker and kysely-bun-sqlite are two different dialects that work with
bun:sqlite
. However, internally the naming used for the kysely-bun-worker dialect is calledbun-sqlite
. At first glance the name implies thatkysely-bun-sqlite
is what is used internally. It took me sometime to figure out why my setup wasn't working because of this confusion.In my app I am using
kysely-bun-sqlite
and I am unable to use codegen. I'd like to propose we rename the current dialect frombun-sqlite
tobun-sqlite-worker
and include thekysely-bun-sqlite
dialect to avoid future confusion.Upvote & Fund