Hacker News Reader

Comment by morgo | Hacker News Reader

MySQL has done well also.

Disclosure: I work on this team. Take a look at new features in 5.7 for example: http://www.thecompletelistoffeatures.com/

View on HN

Really great to see native JSON support in MYSQL finally.

Also, "Random password generated by default on installation"

This has been a long time coming. I can't tell you how many mysql servers I've cracked into with "root"

This is fantastic. It'd be good see more products list new features (and changes) so nicely, especially those links to the manual. Thanks for the list.

Couldn't help posting it: https://news.ycombinator.com/item?id=12181637

Are MySQL and MariaDB going to diverge or stay parallel?

They started diverging at MySQL 5.5.

I wish the 3rd party tool makers would keep up though - the change in the authentication mechanism in the mysql.user table means that tools like Navicat tend to make a real mess of things.

We had to downgrade a project here from 5.7 back to 5.6 because of the issues that 3rd party tools were having. And we were using latest releases of the tools too!

Or perhaps 5.7 should have some sort of fallback or wrapper functions for tools that insist on doing a SET on the password column?

You can do something like this for doing a cross version approach:

  SELECT /*!50706 authentication_string as */ password FROM mysql.user;

I wrote about the rationale to some of the password changes here: http://www.tocker.ca/2014/09/05/proposed-changes-to-user-man...

That's an awesome list of features. It knocks a few entries out of my list of "Features I wish MySQL had". (Yes, I actually have such a list.)

I am curious as to how features get prioritized, though. I would think certain things would be higher priority, such as supporting a full outer join and ensuring that cascaded deletes/updates fire triggers.

Prioritization is based on a few things (customer demand, trends in the market in general). Besides prioritization, there is a resourcing component too (the server is split into several teams with specific expertise).

In general I would say that we like to understand the use case more than the feature :) If the workaround viability is low, the priority goes up.

Yeah... if the AWS team ported them all to Aurora that would be great.

.... Oracle bought a domain name just to list the new features in a minor version release?

I know MySQL doesn't use Semver at all, and I know the domain probably cost 3/5 of fuck all, but still...

I bought the domain name.

It's not a minor release.

MySQL predates semver. It is not alone here (see Mac OS X; PostgreSQL etc.). But you will be happy to hear that the next version will be called 8.0.

5.7... to 8..

Oh right, Oracle. Like how Java 1.5 became Java 5, eh.

Is >=8 going to be Semver?

6.0 was a canceled release.

7.x. is used by Cluster.

8.0 is the next number along, and makes it easy to follow as "it just drops the 5".

Dude, Oracle is bad but when they bought Sun, they were already on Java 6. The "1.4 to 5" move was all Sun, back in 2004 -- and to be honest, it wasn't even a bad move.

Looking at WHOIS, I think morgo bought the domain as an individual.

Reply on news.ycombinator.com