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
Prisma has very limited support for custom SQL while still maintaining the benefits of it's typed API. With the introduction of multi-language fields, which are JSONB encoded language code - value pairs, the search functionality is impossible to implement without resorting to using raw untyped SQL.
Prisma is also proving to be a PITA to work with in a monorepo setting. I would like to switch to a monorepo-type project organization in order to include a separate job runner application for #2 and #9 in the same repo as the frontend and the API server. Using Prisma has made this almost impossible, even with @prisma/nextjs-monorepo-workaround-plugin.
The two alternatives for Prisma, that I am currently considering, are Drizzle ORM, and Postgres.js paired with a schema validation library such as Zod.
The text was updated successfully, but these errors were encountered:
Prisma has very limited support for custom SQL while still maintaining the benefits of it's typed API. With the introduction of multi-language fields, which are JSONB encoded language code - value pairs, the search functionality is impossible to implement without resorting to using raw untyped SQL.
Prisma is also proving to be a PITA to work with in a monorepo setting. I would like to switch to a monorepo-type project organization in order to include a separate job runner application for #2 and #9 in the same repo as the frontend and the API server. Using Prisma has made this almost impossible, even with @prisma/nextjs-monorepo-workaround-plugin.
The two alternatives for Prisma, that I am currently considering, are Drizzle ORM, and Postgres.js paired with a schema validation library such as Zod.
The text was updated successfully, but these errors were encountered: