you are viewing a single comment's thread
view the rest of the comments
[–] 23 points 5 months ago* (last edited 5 months ago) (5 children)

Using integer primary keys often creates race conditions (that result in collisions) when you have multiple database shards, so UUIDs have become the standard. (2 different webservers can create a record in 2 different database that then sync with eachother in the background). Using UUIDs for SQLite is less common though as SQLite is mostly used for small or local applications, but developers are used to UUIDs now and even consider them the standard for primary keys now so you do see them in SQLite databases. (Oh and there's some SQLite compatible sharding servers too)

  • source
  • parent
  • hideshow 5 child comments
  • [–] 2 points 5 months ago (2 children)

    Can't you just reserve X bits of the primary key to store a shard ID?

  • source
  • parent
  • hideshow 2 child comments
  • [–] 3 points 5 months ago

    If you are owning every little part of the design in every nuance, sure. But how do you configure this in mysqll, postgres, etc etc. does your favorite framework support this easily.

  • source
  • parent