2 ms·
Too bad it doesn't support a whole bunch of MySQL features which probably makes it a non starer for us. Some of them are quite boring, like auto increment. htt
by petre 4y ago
Too bad it doesn't support a whole bunch of MySQL features which probably makes it a non starer for us. Some of them are quite boring, like auto increment.
https://vitess.io/docs/14.0/reference/compatibility/mysql-compatibility/ https://vitess.io/docs/14.0/reference/compatibility/mysql-co...
It's more dissapointment on my part rather than criticism.
- tyre 4y agoThey document why auto_increment has issues across shards and the sequence solution that they’ve developed. https://vitess.io/docs/14.0/reference/features/vitess-sequences/ https://vitess.io/docs/14.0/reference/features/vitess-sequen... Is there a use case that sequences don’t handle for you?
- petre 4y agoYeah, we would need to redesign everything from the ground up. And sequences are only useful on unsharded keyspace.
- harshitgangal 4y agoSequences actual use is for sharded keyspace. For unsharded you can just continue to use auto_increment. Maybe your application has some special logic which is complex enough to unwind. I am just clarifying for the second statement.