Comment by nonethewiser 11 hours ago What bugs have you encountered? It's been a smooth experience for me. 2 comments nonethewiser Reply yaur 11 hours ago Not a big exactly but if pip doesn’t work it goes straight to pip —break-system instead of realizing it needs a venvAlso if a prisma migration fails it will say “this is dev it’s ok to erase the database” before rerunning the command with —accept-data-loss abustamam 10 hours ago Given how many projects I've seen that run prisma migrations on prod from their local CLI instead of CI...This scares me.
yaur 11 hours ago Not a big exactly but if pip doesn’t work it goes straight to pip —break-system instead of realizing it needs a venvAlso if a prisma migration fails it will say “this is dev it’s ok to erase the database” before rerunning the command with —accept-data-loss abustamam 10 hours ago Given how many projects I've seen that run prisma migrations on prod from their local CLI instead of CI...This scares me.
abustamam 10 hours ago Given how many projects I've seen that run prisma migrations on prod from their local CLI instead of CI...This scares me.
Not a big exactly but if pip doesn’t work it goes straight to pip —break-system instead of realizing it needs a venv
Also if a prisma migration fails it will say “this is dev it’s ok to erase the database” before rerunning the command with —accept-data-loss
Given how many projects I've seen that run prisma migrations on prod from their local CLI instead of CI...
This scares me.