My Drizzle Story: How I wasted a week for lack of reading

[waynesbrain]

I got sick of the stiffness of the typed-ORM/query-builder style after using Kysely, Objection and others for years especially surrounding dynamic queries. When I looked for alternatives I found Drizzle but without even looking any further into the documentation, upon seeing this:

// Access your data
await db
  .select()
  .from(countries)
  .leftJoin(cities, eq(cities.countryId, countries.id))
  .where(eq(countries.id, 10))

...I noped out.

If only I had spent an extra few minutes to read about the sql tagged template literal with schema helpers and seen this:

await db.execute(sql`select * from ${usersTable} where ${usersTable.id} = ${id}`)

...then I wouldn't have built my own kit that does the same exact thing but worse - https://github.com/waynesbrain/ttsql

I see also that you guys even have the TypeBox integration that I require 🤣 which is probably the main reason I built my own thing, because I didn't want to do double-work defining table schemas + JSON schemas for OpenAPI and other validation purposes...

Welp, at least it should be easy to convert to Drizzle!

The end.

[AndriiSherman]

Or, soon you can use another library that we’ve already built - we’re just finishing the docs for it. It’s a pure SQL template tag that comes with all the integrations and drivers drizzle offers. I’ll ping you here once it’s live

[waynesbrain]

Thanks!