You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This has been a stick in my boot since day 1 - mostly due to their client having a very limited feature set especially with regard to transactions. It slows us down a lot to be forced to write wallet touching code in plpgsql as each change, significant or not, requires a migration.
Anyway, the part of prisma that's worth using is the migration tool mostly because it allows us to express the current schema in a human readable way.
I've been very happy with https://github.com/porsager/postgres. I've been using it for https://outer.space and we should replace all usage of the prisma client with that. Most of our queries are hand written anyway as the prisma client doesn't support ltree.
The text was updated successfully, but these errors were encountered:
This has been a stick in my boot since day 1 - mostly due to their client having a very limited feature set especially with regard to transactions. It slows us down a lot to be forced to write wallet touching code in plpgsql as each change, significant or not, requires a migration.
Anyway, the part of prisma that's worth using is the migration tool mostly because it allows us to express the current schema in a human readable way.
I've been very happy with https://github.com/porsager/postgres. I've been using it for https://outer.space and we should replace all usage of the prisma client with that. Most of our queries are hand written anyway as the prisma client doesn't support ltree.
The text was updated successfully, but these errors were encountered: