@Sqh3rd is attempting to deploy a commit to the NuxtLabs Team on Vercel.

A member of the Team first needs to authorize it.

I love this concept!

Just noticed that the type definition I added does not properly handle the case when there's multiple relationParts defined. I'll take a look today and tomorrow in order to fix that

Right now we're waiting for the Drizzle Team to add API support for Drizzle Studio MySQL and SQLite in v1.

Then we'll need to fix a bug with nuxt db squash now that there's no more journal, and document the requireddrizzle-kit up command for upgrading.

thanks a lot for your support! If you need/want any support from me please ping me, otherwise I'll mark this PR in my mind as "basically completed" 😄

@RihanArfan hey, could you enable https://pkg.pr.new for this PR? :)

npm i https://pkg.pr.new/@nuxthub/core@825

commit: 55e4f03

Hey @Sqh3rd, just a heads up — Drizzle v1.0.0-rc.1 shipped a breaking change to the casing API (it's no longer set on the db instance but on the table/view/schema), so the casing option in the generated drizzle({...}) templates will need a rework before this can be merged. 🙂

Sqh3rd#1

Hey @Sqh3rd, just a heads up — Drizzle v1.0.0-rc.1 shipped a breaking change to the casing API (it's no longer set on the db instance but on the table/view/schema), so the casing option in the generated drizzle({...}) templates will need a rework before this can be merged. 🙂

Sqh3rd#1

Hey, thanks a lot for supporting @adamkasper. I'm starting to think that with the increases in template modification it may make more sense to use a templating engine (e.g. Mustache) to handle these things. Would it be fine to introduce sth like that? I'm not a 100% certain yet, whether that'd make it better. I'll try to write a poc in a few hours to get a feel for how that could look.