Issues when running Drizzle studio on Vercel Postgres
DB Pushing went fine (using Vercel), I can confirm the test table exists, but getting this issue when trying to use studio. It's a sample project using create-t3-app scaffold.
Solution:Jump to solution
Yeah it seems to be because of the - in the table name. Are you going through Theo tutorial also?
26 Replies
additional info:
ubuntu 22 lts, node 20.12.2, pnpm 9.0.4
looks like similar to someone else's question posted 4 hours ago as well
Solution
Yeah it seems to be because of the - in the table name. Are you going through Theo tutorial also?
@Gaz Hey! Can you please share your schema?
that was it
it is a bug
it should work with any names in table
we are trying to reproduce it
removing the hyphens solved it
full was this:
just messing around with the create t3 scaffold
did you push after removing -?
yes sir
and db studio started working
we will fix it
trying to find the cause
if I had to guess, I know pgsql doesn't like hyphens in db/tablenames ideally, and may require some escaping there
t3app should likely convert hypens to underscores or something
no, it was working on our side
yesterday
we did an upgrade to studio
which may broke something here
if it helps, my vercel db also has a hyphen
Same here
@Gaz @g0053 if you will upgrade to latest drizzle-kit, will it work?
I see you have 0.20.14
no sir, I actually installed latest via
pnpm add drizzle-kit@latest -D
after posting this question to see if it helped but it did notgot it
we really can't reproduce it
trying more
it's almost 4:30 am but I can try to create a test repo later to help, should be easy enough
We will deploy a fix for UUIDs in another thread, and maybe we accidentally fixed this one too; that's why it's working for us
I'll ping you once it's live
ok
but you can check any time you want, it's really late for you
or I would say really early
yep, will check here when I get up 🙂
good "night"
yeah, we did fix it accidentally
and were trying to reproduce on a fixed studio
:tired:
It's updated and should be fixed, please try it!
looks resolved, thanks!
yeah confirm fixed for me also