safeql VS Prisma

Be sure to follow this issue if you're interested - https://github.com/ts-safeql/safeql/issues/14

SafeQL is currently in its very early stages, but we can make it better with the community's help! If you have any ideas/improvements/bugs to share, be sure to file an issue in our GitHub repository.

Besides svelte/sveltekit, it uses Zod and tRCP connected to a Supabase postgres database via Prisma and deployed on vercel.

Maybe starting a level lower is also an option, in which case something like https://www.prisma.io/ might be interesting.

Prisma - is an ORM that enables us to write type safe queries to our database. It is a server-side library that helps developers read and write data to the database in an intuitive, efficient and safe way. It is easy to integrate into your framework of choice => Next.js, Graphql, Apollo, nest, Express e.t.c. Prisma simplifies database access, saves repetitive CRUD boilerplate and increases type safety. Its the perfect companion for building production-grade, robust and scalable web applications.

Supporting Postgres' `SET` across queries of a request #5128

In this article we will cover Prisma, which is a top tier choice for ORM in your next application.

Tabular formats fundamentally don't fit with the usual programming model of JSON-based objects. Something like Prisma, which I use across all my projects, eliminates this gap between programming model of thinking with objects, and SQL way of thinking with very standardized rows.

Soft deletes (e.g. deleted_at) #3398

Prisma: a great ORM to work with databases. We use Prisma because of its type-safety and auto-completion, providing great developer experience with typescript added.