hey, we're using prisma.executeRaw for db migratio...
# prisma-migrate
j
hey, we're using prisma.executeRaw for db migrations, but it seems that long running db queries can time out?! does prisma have a timeout for queries? and can we increase it somehow? cheers
hm. maybe it's better we just place the queries in a sql file and run next to prisma
a
If you are interested in using raw SQL/DDL statements in migrations, we may have something of your interest coming up in migrate pretty soon. Would you be interested in validating it and providing feedback? If yes, can you please let me know the best way to contact you? Slack, email? 🙂
j
@Alberto Perdomo slack is fine! we're actually not interested in raw sql but it is the only option when you're transitioning to p2. We ran the prisma-upgrade queries in a migration script (via umzug). The problem that came up was that a larger UPDATE query to update types on about 10k rows from text to jsonb made our migrate script blow up half way through (due to timeout in
$executeRaw
). We only experienced this surprise on Production sadly, our staging and dev servers only have a few rows so queries take no time. umzug is now gone and its migration scripts and we've gone all in with prisma migratee