[purerandomness]

No DDL transactions, no materialized views, the list is endless.

There's almost no reason to pick MySQL for a new project.

[tfigment]

MySQL and mariadb have first class temporal tables. Pg has compile requirement and so cannot use in AWS RDS.

[lowercased]

I was aware maria had temporary tables, but not mysql proper. Any links you can point me to? Every search is coming up with 'temporary' table info, not temporal.

[dragonwriter]

> MySQL and mariadb have first class temporal tables. Pg has compile requirement and so cannot use in AWS RDS.

There’s a pl/pgsql reimplementation of temporal tables specifically for that use case.

[phonon]

https://news.ycombinator.com/item?id=26768220

[lowercased]

mysql8 has gis/spatial stuff built in now. may not quite be on par with postgis, but... i also don't have to futz with "doesn't come baked in". Dealt with someone who wrote a whole bunch of lat/lon/spatial stuff in client code because we're on postgres but ... he couldn't get postgis installed (then even if he could, figuring out how to convince the ops people to add a new 'thing' in production would have been a delay).

having stuff baked in is often a win.

[aseipp]

MySQL has transactions for DDL changes since 8.0.

[tpetry]

MySQL has atomic ddl, which means if a ddl operation fails it is reverted. But PostgreSQL has really transactional ddl which means you can do ddl operations in a transaction and you can commit/rollback multiple ddl operations at once and not each by it‘s own like MySQL does.

https://dev.mysql.com/doc/refman/8.0/en/atomic-ddl.html