Add MySQL to the Database section.

[akopytov]

No description provided.

[kozross]

Based on this rather detailed writeup, I don't consider MySQL to be something I can recommend. If this is out-of-date, or you disagree, I'd love to hear your reasoning, but as it stands, I don't think this belongs on this list.

[akopytov]

Oh dear. Almost everything on that list is wrong these days. Where do I start explaining?

Even if that was still the case, MySQL would still not be going away regardless of your personal attitude. Just like other databases in the Database section, all of which have their own lists of bugs, gotchas and architectural shortcomings. I could probably write up a similar essay on PostgreSQL, for example. I am personally familiar with a person who could write up a similar list of issues with LMDB. Both are on the list, however.

[kozross]

@akopytov Thanks for the reply - I'm certainly not as familiar with these things as I could be, and I appreciate you taking the time to explain. Good that all (or most) of the stuff there is no longer current. With that in mind, I'll merge happily. Thanks for the contribution!

As an aside, I'd be interested in both the LMDB and PostgreSQL writeups, as well as someone pointing out why most of the thing I linked is no longer current.

[akopytov]

Thank you for merging!

Commenting on all points in the article is going to take me some time. I've presented a number of talks on the recent changes in MySQL, but they are in Russian.

The following articles provide a good overview of the current state:

• "One Giant Leap For SQL: MySQL 8.0 Released" (note that even that one is already outdated, because MySQL 8.0 now supports CHECK constraints)
• "Showdown: MySQL 8 vs PostgreSQL 10"

As to LMDB, there is a fork of it called libmdbx, and its README lists improvements over LMDB.

[kozross]

@akopytov Thank you for the links, I will read them. I'll also check out that fork sometime this coming weekend - if it's that much better, I might just replace LMDB with it.