Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Taking the Drizzle Challenge

ben.mk

Post reply on HN
Print view View original

11–14 of 14 posts

Re: Taking the Drizzle Challenge

#11

Post by monssoen »

andrewstuart wrote: post #10

Seriously folks - just write straight up SQL. Your database is incredibly powerful and the best way to program it is with SQL. There's a vast array of features and capabilities that can best be made use of by ........ writing SQL. ChatGPT is incredibly good at writing SQL so its super easy. AND, BONUS ...... you get to carry accumulated knowledge forward because you are actually learning SQL instead of yet another ab…

Rado can be described as sql behind function calls that achieves type safety in Typescript. It does not include any of the ORM abstractions that Drizzle has.

Re: Taking the Drizzle Challenge

#12

Post by monssoen »

tmjdev wrote: post #3

It looks like as an ORM gets more expressive it looks more like regular SQL. What is a reasonable argument for using an ORM over writing SQL? I always feel like I'm missing something because it looks like you have to learn a specific library instead of a general purpose language.

This library tries to get as close to sql as possible. Basically write sql through function calls. Your IDE will autocomplete which method to call. What you gain is type safety. Change the name or type of a column and it propagates through your codebase.

Re: Taking the Drizzle Challenge

#13

Post by monssoen »

theogravity wrote: post #2

We're starting a new project and we've used Drizzle for the past two weeks and started having issues around migrations. For example, if we wanted to remove a table, removing the drizzle schema def doesn't generate a migration for it. What's worse is there's no traditional up / down migration for those familiar with knex. There's no "down" at all from what we saw. There is an issue opened on Drizzle about it and they…

I tried Kysely while evaluating libraries before writing my own. Its heavy reliance on strings for everything was a turn-off because it stops you from using any of the refactoring options Typescript offers. You cannot rename a column for example and have it applied automatically.

Re: Taking the Drizzle Challenge

#14

Post by arresin »

monssoen wrote: post #13
theogravity wrote: post #2

We're starting a new project and we've used Drizzle for the past two weeks and started having issues around migrations. For example, if we wanted to remove a table, removing the drizzle schema def doesn't generate a migration for it. What's worse is there's no traditional up / down migration for those familiar with knex. There's no "down" at all from what we saw. There is an issue opened on Drizzle about it and they…

I tried Kysely while evaluating libraries before writing my own. Its heavy reliance on strings for everything was a turn-off because it stops you from using any of the refactoring options Typescript offers. You cannot rename a column for example and have it applied automatically.

Can you link to the one you wrote?
Post reply on HN