Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

MySQL 5.7.6 is out

datacharmer.blogspot.com

Post reply on HN
Print view View original

61–70 of 70 posts

Re: MySQL 5.7.6 is out

#61

Post by JohnBooty »

morgo wrote: post #53
JohnBooty wrote: post #46

Earlier quoted context omitted.

> 3. It's performance is predictable. 99% of issues > with performance are easily solved with the right index This is one of my least favorite things about MySQL. The "explain" feature is much less informative than that offered by MSSQL or Postgres, so figuring out what indexes or tuning to apply is harder than it needs to be. And then when you do have everything indexed correctly, MySQL is significantly dumber (edit…

If you do not like explain, may I suggest using `EXPLAIN FORMAT=JSON` - it is new to MySQL 5.6, and contains additional meta data. There is also optimizer trace, which provides significantly more meta data. Some good examples in these slides: http://www.slideshare.net/oysteing/how-to-analyze-and-tune-s... I believe your example might be http://mysql-nordic.blogspot.ca/2015/01/with-latest-verions-... - Fixed in 5.7.5.…

That's great to see. Thank you for the correction. I did not know that information was available. I wonder if there are others like me who didn't know this because they've been doing the plain-vanilla EXPLAIN like always.

Re: MySQL 5.7.6 is out

#62

Post by dschiptsov »

taf2 wrote: 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…

Try this. Download mysql sources. Install clang 3.6. Try to compile with all sanitizers. Last time I did it (it was percona code) it found a leak somewhere in SQL parsing code. No kidding.

It is my habit from old days to compile everything.

Re: MySQL 5.7.6 is out

#64

Post by joshstrange »

eropple wrote: post #29
joshstrange wrote: post #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. P…

I know what you're saying, but when I hear people being excited about data stores, I get a little worried. (Being excited about data stores gave us the rise of MongoDB. MySQL tables corrupting because you used MyISAM like a well-intentioned fool is "exciting", too.) I've moved to Postgres for most things because it's not at all exciting for the majority of use cases. It does a thing, does it well, and doesn't break.…

Yes, "Excite" is probably not the right word to use there. I share a wariness towards too much "excitement" about a new DB (I never really trusted Mongo and only used it to play with). In this case I don't see postgres as "new and unproven" but rather "proven and pushing the envelope" which is what excites me.

Re: MySQL 5.7.6 is out

#66

Post by DonHopkins »

morgo wrote: post #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 qu…

"The old syntax was meant to be only deprecated, but it was accidentally completely removed."

How could Oracle have possibly "accidentally completely removed" the old syntax for setting a password even though it "was meant to be only deprecated", without being completely incompetent?

I can not in my wildest imagination come up with a scenario in which a competent developer could possibly "accidentally remove" something like that. If they made such a huge "accident" with that security feature, what other terrible negligent "accidents" lurk just beneath the surface of this new release of MySQL?

How can you "LOL" away such an incompetent "accident" like that?

Re: MySQL 5.7.6 is out

#67

Post by datacharmer »

DonHopkins wrote: post #66
morgo wrote: post #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 qu…

"The old syntax was meant to be only deprecated, but it was accidentally completely removed." How could Oracle have possibly "accidentally completely removed" the old syntax for setting a password even though it "was meant to be only deprecated", without being completely incompetent? I can not in my wildest imagination come up with a scenario in which a competent developer could possibly "accidentally remove" somethi…

"LOL away?" What gave you the impression that I was making fun of it? I am the one who found the bug and reported it, and this is the explanation I got. Since the person I talked to is someone I trust, I don't have reason to think otherwise. I can elaborate further and tell you why this particular error was likely to happen: it's because since the beginning MySQL was built with root user without password, and most of the tests were running in such conditions. That was the culture of rapid growth that gave MySQL its popularity and the developers are paying now the technical debt that has left so many features with poor testing behind. What Oracle is doing now is trying to redress that situation by strengthening the defaults, for which I commend them. Being a QA developer, I am less pleased with the quality of tests that let such mistake pass, but I know that such things happen, and it does not necessarily mean that there is a can of worms behind this bug.

Re: MySQL 5.7.6 is out

#68

Post by DonHopkins »

datacharmer wrote: post #67
DonHopkins wrote: post #66

Earlier quoted context omitted.

"The old syntax was meant to be only deprecated, but it was accidentally completely removed." How could Oracle have possibly "accidentally completely removed" the old syntax for setting a password even though it "was meant to be only deprecated", without being completely incompetent? I can not in my wildest imagination come up with a scenario in which a competent developer could possibly "accidentally remove" somethi…

"LOL away?" What gave you the impression that I was making fun of it? I am the one who found the bug and reported it, and this is the explanation I got. Since the person I talked to is someone I trust, I don't have reason to think otherwise. I can elaborate further and tell you why this particular error was likely to happen: it's because since the beginning MySQL was built with root user without password, and most of…

It's not my impression that you're making fun of it, but that you're trying to excuse it as an inconsequential "accident" instead of incompetence. Accidents like that don't happen without causes like incompetence or negligence or malice. Accidents like that are a symptom that something is deeply wrong.

Re: MySQL 5.7.6 is out

#69

Post by morgo »

DonHopkins wrote: post #66
morgo wrote: post #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 qu…

"The old syntax was meant to be only deprecated, but it was accidentally completely removed." How could Oracle have possibly "accidentally completely removed" the old syntax for setting a password even though it "was meant to be only deprecated", without being completely incompetent? I can not in my wildest imagination come up with a scenario in which a competent developer could possibly "accidentally remove" somethi…

This is noted in the release notes, and I have a blog post on it here: http://www.tocker.ca/2015/03/10/heads-up-mysql-5-7-dmr6-cont...

To describe our process: We have at least 2 code reviews, ~90% test coverage before we release a feature in a development milestone. It was then caught by at least 3 people that I know of prior to public release. Since this is not a GA release, it was decided to fix the bug in the next version.

Re: MySQL 5.7.6 is out

#70

Post by kidmenot »

Buttons840 wrote: post #56
kidmenot wrote: post #31

Earlier quoted context omitted.

>4. I don't find myself needing many SQL features beyond the basics. That's probably why you still like it. As it stands, MySQL has so many shortcomings it's not even funny. Version 5.7 is the first one to support multiple triggers per event. Beyond that, and just to name a few, you can't have subselects in views, you don't have CTEs (good luck storing hierarchical data in an adjacency list), no materialized views, C…

There have been several times in my career where I have missed full SQL support in MySQL databases other people have setup and left for me to maintain. Choosing MySQL isn't the worst thing one can do when building a new system, but just because the initial designers don't intend to use advanced SQL features doesn't mean future use cases wont benefit from full SQL support.

Indeed. Just these days the lack of materialized view has been giving me troubles. It would make a certain process about 50 times faster without touching code at all, and it would take me all of three queries.

Granted, the real problem is a poor design of the system, but materialized views would enable me to improve what others have left behind.

Post reply on HN