MySQL 8.0 is now generally available
mysqlserverteam.com
MySQL 8.0 is now generally available
1–10 of 105 posts
Re: MySQL 8.0 is now generally available
#2There are some very useful features there, but I can't help but think that MySQL should have had them a long time ago.
Is there something MariaDB doesn't have? I'm genuinely curious as I've only really followed PostgreSQL development.
Re: MySQL 8.0 is now generally available
#3Woohoo I've been eagerly awaiting this. I use redshift postgres and SQL server at work and looking to migrate from postgres to MySQL for my personal ML projects.
Window functions have been a long time coming and I personally can't wait!
Re: MySQL 8.0 is now generally available
#4> Reliability: DDL statements have become atomic and crash safe, meta-data is stored in a single, transactional data dictionary. Powered by InnoDB!
To clarify, does this mean that DDL is now fully transactional the way it is in postgres?
Re: MySQL 8.0 is now generally available
#5Woohoo I've been eagerly awaiting this. I use redshift postgres and SQL server at work and looking to migrate from postgres to MySQL for my personal ML projects. Window functions have been a long time coming and I personally can't wait!
There are a lot of postgres fans on HN, would you mind giving some more info on why you want to go from PG to MySQL?
Re: MySQL 8.0 is now generally available
#6There are some very useful features there, but I can't help but think that MySQL should have had them a long time ago. Is there something MariaDB doesn't have? I'm genuinely curious as I've only really followed PostgreSQL development.
No, at this point Maria has surpassed MySQL, however over time we'll likely see the two diverge as MySQL creates new storage types and heads in a different strategic direction.
Re: MySQL 8.0 is now generally available
#7There are some very useful features there, but I can't help but think that MySQL should have had them a long time ago. Is there something MariaDB doesn't have? I'm genuinely curious as I've only really followed PostgreSQL development.
The big features that MySQL has been lacking, MariaDB has had since at least 10.2 (Apr 2016) or earlier. Specifically I'm talking about Windowing functions, CTEs, JSON support, GIS support, Metadata in transactions (DDL statements).
At this point MySQL is playing catch-up to MariaDB.
Re: MySQL 8.0 is now generally available
#8Side question, but why the jump from 5.7 to 8.0?
What happened to 6.0 and 7.0?
Edit: found a kind of answer, though I never heard of 6 and 7 being "used" before. [1]
> Why did MySQL version numbering skip versions 6 and 7 and go straight to 8.0?
> Due to the many new and important features we were introducing in this MySQL version, we decided to start a fresh new series. As the series numbers 6 and 7 had actually been used before by MySQL, we went to 8.0.
[1] https://dev.mysql.com/doc/refman/8.0/en/faqs-general.html#fa...
Re: MySQL 8.0 is now generally available
#9Side question, but why the jump from 5.7 to 8.0? What happened to 6.0 and 7.0? Edit: found a kind of answer, though I never heard of 6 and 7 being "used" before. [1] > Why did MySQL version numbering skip versions 6 and 7 and go straight to 8.0? > Due to the many new and important features we were introducing in this MySQL version, we decided to start a fresh new series. As the series numbers 6 and 7 had actually bee…
People are going to start to think tech companies don't know how to count or something. Jokes aside... I'm wondering the same.
Re: MySQL 8.0 is now generally available
#10Side question, but why the jump from 5.7 to 8.0? What happened to 6.0 and 7.0? Edit: found a kind of answer, though I never heard of 6 and 7 being "used" before. [1] > Why did MySQL version numbering skip versions 6 and 7 and go straight to 8.0? > Due to the many new and important features we were introducing in this MySQL version, we decided to start a fresh new series. As the series numbers 6 and 7 had actually bee…
The usual radix promotion that tends to occur when the major version becomes ossified.
5.8.0 -> 8.0