3 ms·
Every time people would champion vitess / PS as a drop in fix this the caveat that would slow them down or stop them. This feature truly is a game-changer for
by leetrout 3y ago
Every time people would champion vitess / PS as a drop in fix this the caveat that would slow them down or stop them.
This feature truly is a game-changer for adoption IMO.
Congrats on shipping to all involved!
- shlomi-noach 3y agoThank you!
- irq-1 3y ago> At this time, foreign key constraint support is limited to unsharded/single shard databases.
- AYBABTME 3y agoThe Venn diagram of people needing sharding and still using foreign keys is probably empty.
- leetrout 3y agoWorth noting, the competing products from Neon and Cockroach Labs support FKs.
- AYBABTME 3y agoCockroach supports it, but like for MySQL, PG, PlanetScale, or most DBs at scale, you shouldn't use them. Neon isn't in the same league at all so I think what they support doesn't matter.
- nikita 3y agoNeon is not a shared nothing architecture but shared storage. Makes it 100% compatible with Postgres that supports FK constraints since 1989
- nikita 3y agoAlso would be useful to add a disclaimer that you work for PlanetScale.
- adam_gyroscope 3y ago(And you work for neon)
- beachy 3y ago> but like for MySQL, PG, PlanetScale, or most DBs at scale, you shouldn't use them. Tell that to the people who have been successfully building massive databases in RDBMS for decades making extensive use of FKs and FK constraints.