Different code behave different, what you need to do is to study your business model, and find a best fit.
I'm going to talk about the nontechnique thing, and hope it can help.
Mysql is spliting, when saying Mysql, we always need to think about Mysql of Oracle or Mariadb. both database have their own road map, you cannot benifit from both.
if you finaly choice "Mysql", actually, you will still face to another choice, Mysql or Mariadb. Assume you select Mysql, you will always face to new choices, for example, some tools(or practice) is for Mariadb, whether it can work with Mysql; some good features is included by Mariadb, what about or when for mysql; some business model that Maradb code can fit well, but Mysql code cannot, and so on.
Thanks
Denny Wang
On Wed, Mar 13, 2019 at 12:09 AM Michael Nolan <htfoot@gmail.com> wrote:
The MySQL manual says that INNODB 'adheres closely' to the ACID model, though there are settings where you can trade some ACID compliance for performance.
I've been running PostgreSQL for a client since 2005, we're on our 5th hardware platform in that time period. We also run a MySQL/MariaDB database to support our website, it is currently on an AWS RDB server which is refreshed from the PostgreSQL server. I also administered an Oracle system for a well-known educational publisher for about 10 years. Given my druthers, I'd take PostgreSQL over either Oracle or MySQL.
