DT
Drizzle Team•7mo ago
g0053

Drizzle Kit Studio: Object is not iterable

Hey guys when trying to run Drizzle Studio I am getting this error. This is the details in the log: length: 90, severity: 'ERROR', code: '42601', detail: undefined, hint: undefined, position: '76', internalPosition: undefined, internalQuery: undefined, where: undefined, schema: undefined, table: undefined, column: undefined, dataType: undefined, constraint: undefined, file: 'scan.l', line: '1241', routine: 'scanner_yyerror' drizzle-kit: v0.20.16 drizzle-orm: v0.29.5 Any ideas?
No description
20 Replies
AfonsoHell
AfonsoHell•7mo ago
From my testings the issue occurs when a table name contains a "-" is this your case? And if so, I've opened an issue on github: https://github.com/drizzle-team/drizzle-kit-mirror/issues/367
g0053
g0053•7mo ago
Yeah mine does. Thank you. I had a thought it could that. Should I change table name or is it likely to get fixed
AfonsoHell
AfonsoHell•7mo ago
It is probably gonna get fixed soon, the new version has only been up for 12 hours.
Andrii Sherman
Andrii Sherman•7mo ago
We are working on fixing it
AfonsoHell
AfonsoHell•7mo ago
Thanks for the hard work guys 🙂
âš¡Z.E.U.Sâš¡
⚡Z.E.U.S⚡•7mo ago
@g0053 Hey! Can you please share your schema?
g0053
g0053•7mo ago
No description
g0053
g0053•7mo ago
Yeah that is what it is. Its part of a tutorial Theo (Youtube channel) is doing. I havent edited it at all yet. This is the code that the t3 stack outputs
Andrii Sherman
Andrii Sherman•7mo ago
It's updated and should be fixed, please try it! @g0053 @AfonsoHell you can check now should work well
AfonsoHell
AfonsoHell•7mo ago
@Andrew Sherman Just tested and it seems to be working again. Once again thanks for the great work you guys are doing!
g0053
g0053•7mo ago
yeah fixed for me also. Thanks heaps keep up the good work
migs
migs•7mo ago
for some reason its still not fixed for me, maybe pnpm is caching something from the previous one and I just updated to 20.17
Yiannis
Yiannis•6mo ago
Doesn’t work for me either I can also confirm removing dashes fixes the issue
Yiannis
Yiannis•6mo ago
Turning this off fixed it for me
No description
Yiannis
Yiannis•6mo ago
Meaning I can use dashes as well
Andrii Sherman
Andrii Sherman•6mo ago
@âš¡Z.E.U.Sâš¡
âš¡Z.E.U.Sâš¡
⚡Z.E.U.S⚡•6mo ago
@Yiannis Hey! Can you hard refresh your browser and try again with rows count?
Yiannis
Yiannis•6mo ago
Hey, absolutely! Currently in a meeting but done in 5-10. Once I check I will report back! Sorry for the delay, got to love Mondays... All fixed! Thank you guys so much!
pineappaul
pineappaul•6mo ago
I am also getting this error (same error code) upon running drizzle-kit push:pg to my local postgres. Drizzle-Kit version 0.20.17 Drizzle-ORM version 0.30.9 using pg version 8.11.3 Also made sure there are no dashes (- )in any fields nor table names. What is most strange is that when this runs, drizzle will recognize the metadata from the journal and ask about each of the tables that should be created or replaced. After running through the whole, set I can notice two of the many tables get created on Drizzle-Studio, while the rest remain uncreated and the console throws the error user g0053 shared. You can see my package for drizzle db stuff and schema here: https://github.com/paulmikulskis/product-eng/tree/main/packages/db Thank you very much for any help!
migs
migs•6mo ago
all fixed on my side too. The only small detail I've noticed is that the db:push always says "Changes Applied" even when there's no changes. It used to be able to distinguish this
Want results from more Discord servers?
Add your server