Live data from Hacker News

MySQL 5.7.6 is out

datacharmer.blogspot.com

1–10 of 70 posts

Re: MySQL 5.7.6 is out

#3

For the effort to absorb "big changes" I would also weigh porting to PostgreSQL.

Its clickbait headline, or maybe they're going for outright sarcasm given how little is changing.

Technically its true that the install process is a little different but not much, and theres some minor changes in user configuration. I've looked into it and the most exciting "DBA level" changes are YEAR(2) is finally utterly expunged, and there's some new reserved words "NONBLOCKING" and "OPTIMIZERCOSTS". Thats about as exciting as it gets.

Its not transparent upgrade but its not like they're changing the default db engine to an embedded nosql engine, or changing the default char encoding to EBCDIC.

Re: MySQL 5.7.6 is out

#4
MySQL doesn't excite me at all anymore. It used to be my DB of choice but as of late I've been using postgres and other than tools being somewhat lacking (this is getting better all the time, there are now GUI browsers for postgres that rival sequel pro). Nothing was really keeping me on MySQL other than it was generally the prefered DB for most OS projects and I had used it in professional settings multiple times. Postgres's JSON store is very interesting and I've read a number of articles on other cool things in Postgres all while MySQL was more or less silent. I'd love to setup a postgres server at work and benchmark it against our MySQL DB, the one thing really holding me back is our use of ENUMs but I don't think that's going to be a big barrier and I hate them anyways.

Re: MySQL 5.7.6 is out

#5

MySQL doesn't excite me at all anymore. It used to be my DB of choice but as of late I've been using postgres and other than tools being somewhat lacking (this is getting better all the time, there are now GUI browsers for postgres that rival sequel pro). Nothing was really keeping me on MySQL other than it was generally the prefered DB for most OS projects and I had used it in professional settings multiple times. P…

> the one thing really holding me back is our use of ENUMs but I don't think that's going to be a big barrier and I hate them anyways

Postgres has proper support for ENUM as defined in the SQL Standard. You have to create a new type and declare it as being an ENUM type:

http://www.postgresql.org/docs/9.4/static/datatype-enum.html

Re: MySQL 5.7.6 is out

#6
post #5

MySQL doesn't excite me at all anymore. It used to be my DB of choice but as of late I've been using postgres and other than tools being somewhat lacking (this is getting better all the time, there are now GUI browsers for postgres that rival sequel pro). Nothing was really keeping me on MySQL other than it was generally the prefered DB for most OS projects and I had used it in professional settings multiple times. P…

> the one thing really holding me back is our use of ENUMs but I don't think that's going to be a big barrier and I hate them anyways Postgres has proper support for ENUM as defined in the SQL Standard. You have to create a new type and declare it as being an ENUM type: http://www.postgresql.org/docs/9.4/static/datatype-enum.html

Very interesting! Thanks for the link, even with that I'd rather convert the ENUMs to just VARCHARs as our MVC framework doesn't support ENUMs but it "Just works" because it sends strings to MySQL and MySQL stores them as INTs that map to ENUM values. Because of this the test framework never played nice with creating test DB's that used ENUMs.

Re: MySQL 5.7.6 is out

#7
post #3

For the effort to absorb "big changes" I would also weigh porting to PostgreSQL.

Its clickbait headline, or maybe they're going for outright sarcasm given how little is changing. Technically its true that the install process is a little different but not much, and theres some minor changes in user configuration. I've looked into it and the most exciting "DBA level" changes are YEAR(2) is finally utterly expunged, and there's some new reserved words "NONBLOCKING" and "OPTIMIZERCOSTS". Thats about…

I would say the biggest change is that the default SQL mode will be the equivalent to 5.6's ONLY_FULL_GROUP_BY,STRICT_TRANS_TABLES,NO_ENGINE_SUBSTITUTION,ERROR_FOR_DIVISION_BY_ZERO, NO_ZERO_DATE,NO_ZERO_IN_DATE,NO_AUTO_CREATE_USER.

This means that a number of statements that produced warnings (but proceeded) will now produce errors.

I have some slides on it here: http://www.slideshare.net/morgo/upcoming-changes-in-mysql-57 (see slide 33 onwards).

Re: MySQL 5.7.6 is out

#8
So much MySQL hate these days... I should try Postgres out but here's why I still like and trust MySQL or MariaDB/Percona...

  1. It's reliable/durable

  2. I know the tools (mysql command line is friendly to me)

  3. It's performance is predictable.  99% of issues with performance are easily solved with the right index

  4. I don't find myself needing many SQL features beyond the basics.
Also, I'm a happy user of other tools to compliant mysql. Including redis and elasticsearch. Both of these tools IMO compliant MySQL.

I'm no fan of Oracle by any means but at least MySQL is still an open source database. Perhaps when I have free time before the next startup I'll give Postgres a good look. For now I'll probably try it out with AWS redshift...

Re: MySQL 5.7.6 is out

#9
Community Manager for MySQL here!

A better overview link for what's new in 5.7.6 specifically is this one: http://mysqlserverteam.com/the-mysql-5-7-6-milestone-release...

To understand what's new in 5.7 overall: http://dev.mysql.com/doc/refman/5.7/en/mysql-nutshell.html

Specific to this blog post. Here is the page on upgrading: http://dev.mysql.com/doc/refman/5.7/en/upgrading-from-previo...

I'm happy to answer any questions, please feel free to ask away.

Re: MySQL 5.7.6 is out

#10
post #8

So much MySQL hate these days... I should try Postgres out but here's why I still like and trust MySQL or MariaDB/Percona... 1. It's reliable/durable 2. I know the tools (mysql command line is friendly to me) 3. It's performance is predictable. 99% of issues with performance are easily solved with the right index 4. I don't find myself needing many SQL features beyond the basics. Also, I'm a happy user of other tools…

Well it's HN, outside of Postgres / Redis everything sucks. And yes you're right on MySQL it's reliable. Honest question here, is there an equivalent of Percona tools for Postregres?
Post reply on HN