One Giant Leap for SQL: MySQL 8.0 Released

Re:One Giant Leap for SQL: MySQL 8.0 Released by kasabali on Wednesday April 25, 2018 @04:46PM (#16925956)

> It isn't correct to "upgrade" someone to a different piece of software, and it definitely wasn't "graceful". The whole source of my rage comes from the fact that everything was inexplicably broken and I did not know why.

> And of course, the response to "man mysql" makes no sense, because MariaDB is not MySQL.

MariaDB was supposed to be a drop-in replacement. This is why Debian (and other distros like Fedora) chose to name it and help transition of existing users. Distributions tried their best to make it as painless as possible. Sorry it wasn't the case for you but I guess it still helped more people than it hurt.

> (And bear in mind, I was working from a script, so unless I sit there reading every line while it builds the VM, all of this unauthorized breakage of my machine is silent and without consulting me.)

It was documented in Release Notes [0]. You should've read it before upgrading your script. It is always a good idea to read it regardless of this specific issue.

Even if you didn't read release notes, banner text of `mysql' command makes it very clear it's MariaDB:

  $ mysql
  Welcome to the MariaDB monitor.  Commands end with ; or \g.
  Your MariaDB connection id is 32
  Server version: 10.1.26-MariaDB-0+deb9u1 Debian 9.1

[0]: https://www.debian.org/releases/stable/amd64/release-notes/c...

[ Parent | on HN ]

Re:One Giant Leap for SQL: MySQL 8.0 Released by ivanhoe on Thursday April 26, 2018 @04:08AM (#16929901)

> MariaDB was supposed to be a drop-in replacement.

"Supposed to" is a key point here, cause it's not: Explain works different if you need a certain thread info, AFAIK no JSON data type, GIS functions are different, lots of subtle differences that will bite you in the arse if you presume it's exactly the same engine. And as the time goes by the list of differences is just growing.

[ Parent | on HN ]