hey hn, supabase ceo here the Val Town team were kind enough to share this article with me before they released it. Perhaps you know from previous HN threads that we take customer feedback very seriously. Hearing feedback like this is hard. Clearly the team at Val Town wanted Supabase to be great and we didn’t meet their expectations. For me personally, that hurts. A few quick comments 1. Modifying the database in pr…
Migrating from Supabase
131–136 of 136 posts
Re: Migrating from Supabase
#132hey hn, supabase ceo here the Val Town team were kind enough to share this article with me before they released it. Perhaps you know from previous HN threads that we take customer feedback very seriously. Hearing feedback like this is hard. Clearly the team at Val Town wanted Supabase to be great and we didn’t meet their expectations. For me personally, that hurts. A few quick comments 1. Modifying the database in pr…
Just wanted to add I’ve been using the local development and migrations workflow and it has been fantastic. Honestly the only issue I’ve really had is how frustratingly difficult it is to change an id field from int8 to uuid if I mistakenly don’t choose the right one at first and the migrations get stuck on that and I have to resort to manual hacking. Setting up local/staging/prod with this new system seems really ea…
Re: Migrating from Supabase
#133Earlier quoted context omitted.
Personally I like both projects, as I hope I made clear in the OP - I sense that there's some history and strife here that I'm not clued into as an outsider.
> Personally I like both projects, as I hope I made clear in the OP You did, but it generally sounded like Kysely doesn't have a bunch of things, when in fact it does. A more balanced comment would've suggested both projects have X, but I like Y's implementation better. So I jumped in, to inform and give my 2 cents. :) > I sense that there's some history and strife here that I'm not clued into as an outsider. There's…
I would have wanted to see Kysely have the ability to generate migrations for example. I also personally prefer the approach that Drizzle takes when it comes to more adoption (in my case, CockroachDB).
Just a personal preference - the project is awesome.
Re: Migrating from Supabase
#134Curious why have you decided for Drizzle over Kysely. I was recently exploring the space, and Kysely came on top as a framework with broader adoption. https://npmtrends.com/drizzle-orm-vs-kysely
edit: while not exhaustive, I'm seeing better perf (by about 20%) using kysely compared to drizzle for identical queries on planetscale. Take this with a grain of salt since I've made no attempt to measure exhaustively, or optimize -- just using "as-is" so to speak, but thought it would be with noting and nothing to indicate to me that drizzle offers big perf improvement over kysely as has been suggested. Thanks for this post btw. Drizzle is hot and shiny right now (Theo just promoted big time), but after taking a second look at drizzle and in the process of writing up my thoughts here, it's become clear to me that I'm sticking w/ kysely.
Re: Migrating from Supabase
#135Curious why have you decided for Drizzle over Kysely. I was recently exploring the space, and Kysely came on top as a framework with broader adoption. https://npmtrends.com/drizzle-orm-vs-kysely
I've been evaluating both (kysely, drizzle), and I'm leaning towards Kysely. Drizzle is the latest, but both are moving fast if you look at the git insights. I find Kysely more enjoyable and straightforward -- intellisense autocompletions work better (for me at least), and the expression builder combined w/ helper methods like jsonArrayFrom offer a lot of flexibility over how to shape the output, so you're in full co…
Re: Migrating from Supabase
#136Earlier quoted context omitted.
> Personally I like both projects, as I hope I made clear in the OP You did, but it generally sounded like Kysely doesn't have a bunch of things, when in fact it does. A more balanced comment would've suggested both projects have X, but I like Y's implementation better. So I jumped in, to inform and give my 2 cents. :) > I sense that there's some history and strife here that I'm not clued into as an outsider. There's…
My personal problem with Kysely is that the migrations are not aligned with what I needed personally. I would have wanted to see Kysely have the ability to generate migrations for example. I also personally prefer the approach that Drizzle takes when it comes to more adoption (in my case, CockroachDB). Just a personal preference - the project is awesome.
atlasgo io looks promising to handle migrations and is open source as well. I am currently using prisma.