Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Migrate away from Prisma #16

Open
dogamak opened this issue Jan 8, 2024 · 0 comments · May be fixed by #20
Open

Migrate away from Prisma #16

dogamak opened this issue Jan 8, 2024 · 0 comments · May be fixed by #20

Comments

@dogamak
Copy link
Member

dogamak commented Jan 8, 2024

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.

@dogamak dogamak linked a pull request Oct 12, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant