5 ms·

Reason 34,583,498 to use Postgres instead of MySQL.

• q3k 7y ago
  Also to not use the TIMESTMAP type in general, which is full of similar by-default footguns (off the top of my head: default 1-second precision, connection-local timezone autoconversion). At least for non-historic events. Use uint64 as nanoseconds from epoch. Explicitly convert to/from UTC in your application code. Smear your leap seconds. This will last you until 2554, by which time I hope computers as we know are dead. Bonus: these make for decent strong-read-ordered internal UUIDs, given good retry logic.
  • jpeg_hero 7y ago
    I am looking at just this design pattern now (pseudo uuid) can you elaborate on “given good retry logic”?
    • thecopy 7y ago
      I assume that on conflict just retry again, the timestamp will be different.
• deleted 7y ago
  [deleted]
• nwallin 7y ago
  Reason #-2147483648 to use PostgreSQL instead of MySQL.