studio VS kysely

If this is likely to be a "once and done" type endeavor, I would just use Prisma Studio. https://www.prisma.io/studio

Thin Backend provides you with an IDE that has custom business logic and serverless functions, while Prisma gives you a visual database browser called Prisma Studio. In this section, we will dive deeper into how these database technologies help us in design and model database schemas.

Yes. This is it https://www.prisma.io/studio

Prisma Studio: GUI client para tu base de datos.

Both Prisma and PlanetScale have convenient to use GUIs, Prisma Studio and the PlanetScale beta Console.

Download the Prisma Studio app

You will also be able to access Prisma Studio locally to create your and your team's users.

Run this command to open up Prisma Studio, a simple way to explore and manipulate the data in the database:

Prisma Studio tool that helps to manage data easily.

> Making calendar scheduling work for everyone.

Well... if that were the case then this would support caldav as an open standard or at the very least mention it- as it stands it only seems to support Google Calendar. And all other (prorietary) solutions this software wants to integrate with are marked "coming soon".

For a claims like

> Our mission is to connect a billion people by 2031.

and

> What email has done to communication, we hope Calendso will do to meetings.

Thats not a lot.

Anyway I tried to run it.

This is a step that should not be neccessary

> 7. Open the prisma schema with [Prisma Studio](https://www.prisma.io/studio)

to manually create a user in the database - presumably there is a way to

Did you check https://github.com/koskimas/kysely ? It was great when I used it. It has great TS support.

That’s where Kysely comes to the rescue: Kysely is a type-safe and devX-friendly typescript SQL query builder. It was designed to work with PostgreSQL and MySQL, but it exposes a few classes that can let us write queries without being connected to an actual relational database.

prisma (mentioned in the article), zapatos, pgtyped and kysely are the most popular currently I think.

switch between a limited interface and a query builder (MikroORM, TypeORM). This feels like using two different libraries, switching between two different sets of limitations. Kysely is a nice query builder with good TS support, but MikroORM is using Knex instead so you're losing TS, and TypeORM has a custom query builder, less user-friendly than Knex.

I'd love to see Kysely as an option.

Kysely[1] and zapatos[2] are excellent solutions for type-safe typescript query builders. It’s hard to go back to the days of spending 20-30% of your time in the object mapping layer.

[1] https://github.com/koskimas/kysely

Querying the database (PostgreSQL) should not be ground breaking. Personally I like to have full type-safety so we can easily catch bugs during the development time without introducing any tests that are just testing the data type from our datastore to match the data type our API expects. I like to go database schema first, which means that we generate types from the database schema and work with those. Any change to the schema of the database is made with SQL migrations and after that, the typescript types are regenerated. Another approach is to use a code-first tool like TypeORM or Prisma. However in my experience such tools often produce not efficient SQL queries and are less easy to extend. In my projects I use library kysely (https://github.com/koskimas/kysely) with kysely-codegen (https://github.com/RobinBlomberg/kysely-codegen) to have a full type-safe SQL builder.