open-kanban VS Prisma

I've just started this project with [email protected] ande prisma. On my local machine this is what went down:

Hey there, I work at Prisma, we're building an ORM that helps with exactly that workflow :)

Hey, Alex here from the Prisma team.

You can use something like https://www.prisma.io/. Which is an ORM (Object-Relational Mapping) that talks to the DB, but easier for you if you know Node/JavaScript.

- Remix for framework - Prisma for ORM - Planetscale for database - Vercel for hosting

Even if it supports many relational databases, there is one notable absence in the list: Oracle. It can be restrictive if you are working for a bank or a large corporation that is used to working with this database. There is an ongoing issue if you want to follow this topic.

Prisma is a recent TypeScript ORM taking a different approach from its predecessors and focusing on type safety thanks to TypeScript.

That's right, using prisma as my ORM. The app is an electron app so the build configuration can be tricky for 'native' dependencies, which SQLite falls under.

One of Prisma's best features is its TypeScript client generated from Prisma schema. For me, it is a killer feature that differentiates Prisma from other JavaScript ORMs. By using the generated TypeScript client, I don't need to worry about writing custom types no matter how complex my queries are. Even better, Prisma's code generator system is designed to be extensible, so we can make it generate more than just TS client.

It's true that partial indexes are not yet natively supported in the Prisma schema, we have an open issue for that here. It would be great if you could leave a +1 on the issue and ideally a comment with your use case, this helps us prioritize and hopefully implement this soon!

This is indeed a frequently requested feature that we're planning to look at soon! You can find an open issue for that on GitHub (again, it would be nice if you could +1 and comment on the issue).