"At the time, MySQL existed ..."

You had to be careful with MySQL back then as constraints were syntactic sugar but not enforced. PostgreSQL was indeed much tougher to manage but more full-featured.

▲

da_chicken 3 days ago | parent | next [-]

Really, you've always had to be careful with MySQL. It really was the PHP of RDBMSs.

The silent "SHOW WARNINGS" system, nonsense dates like Feb 31, implicit type conversions like converting strings to 0s, non-deterministic group by enabled by default, index corruption, etc.

▲

makeitrain 2 days ago | parent [-]

Good enough for Wordpress.

	▲	augusto-moura 2 days ago \| parent [-]
		We are circling back to PHP, aren't we?

▲

Izkata 3 days ago | parent | prev | next [-]

Not just constraints, transactions were also a no-op. The MyISAM engine is still available in modern versions if you want to experience this, it's just not default anymore.

	▲	jamesfinlayson 3 days ago \| parent [-]
		Yep, I've had to work with a MyISAM project with no transactions - it's a reasonably simple system thank goodness but a little scary all the same (and lots of boilerplate to deal with partial failures).

▲

tomnipotent 3 days ago | parent | prev [-]

I love Postgres in 2026, but it really was not a viable enterprise option before 2010. MySQL had decent binlog replication starting in 2000 which made up for a lot of the horrible warts it had.

▲

bombcar 3 days ago | parent [-]

mysql was great in 2000 if you knew all the foot guns to avoid and set it up correctly (and not just what sounded correct).

	▲	tomnipotent 3 days ago \| parent [-]
		Not to mention there was Percona, and both Google & Facebook contributed a number of patches that made monitoring MySQL top notch (such as finding slow running queries, unused indexes, locks etc.).