examples-next-prisma-starter VS kysely

Here's an example of testing: https://github.com/trpc/examples-next-prisma-starter/blob/ma...

{ e.preventDefault(); const $form = e.currentTarget; const values = Object.fromEntries(new FormData($form)); type Input = inferProcedureInput< AppRouter["dailyActivity"]["addDailyActivity"] >; // ^? const input: Input = { name: values.title as string, timeSpent: values.text as string, }; try { await addActivity.mutateAsync(input); $form.reset(); } catch (cause) { console.error({ cause }, "Failed to add post"); } }} > Title: Text:
{addActivity.error && (

{addActivity.error.message}

)}

)

So I am copying/learning the logic from https://github.com/trpc/examples-next-prisma-starter. In this code, there is no ID provided in the query, yet in my code, I get the error that I need to provide an ID. Since the ID in the prisma schema is cuid() doesn't that mean that is autogenerated? What am I missing?

In this quick blog post, I will use one of TRPC's examples available on GitHub to explain this concept in real life and then show you how to handle default values in development mode.

A bit of heresy to post this in the GraphQL subreddit but another alternative is tRPC + Prisma. I was testing both Pothos and tRPC yesterday and the latter is just so simple while still giving you full end-to-end type safety.

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.