Side 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…
MySQL 8.0 is now generally available
11–20 of 105 posts
Re: MySQL 8.0 is now generally available
#12Side 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…
Re: MySQL 8.0 is now generally available
#13Side 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
verb past tense: ossified; past participle: ossified 1. turn into bone or bony tissue. "these tracheal cartilages may ossify" synonyms: turn into bone, become bony, calcify, harden, solidify, rigidify, petrify "the cartilage may ossify" 2. cease developing; be stagnant or rigid. "ossified political institutions" synonyms: become inflexible, become rigid, fossilize, calcify, rigidify, stagnate "the old political institutions have ossified"
... it would seem to me by whatever logic is employed, the same thing will occur at 10.0 because the version format may "appear" to change (with 2 leading digits now).
Ohh ... maybe you're saying the 5 hasnt changed in ages, well now was a silly time to change it still because they were .2 releases until it did change, which was mentioned by the other poster that mysql has already used versions 6 and 7 prior ....
I still don't agree that ossified is a valid usage in this case (it was still .2 releases from changing) -- when the original x.y.z versioning scheme was defined it was understood that there could be 0-N minor "y" updates before X is incremented; that's by definition not ossification, simply the versioning scheme at work.
geez. what a mess versioning is ... :P
Re: MySQL 8.0 is now generally available
#14Woohoo 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
#15Woohoo 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?
The transactional DDL seems to be introduced in MySQL per 8.0 though
Re: MySQL 8.0 is now generally available
#16There is a separate blog post highlighting it: https://mysqlserverteam.com/mysql-8-0-announcing-ga-of-the-m...
1. https://dev.mysql.com/doc/x-devapi-userguide/en/devapi-users...
Re: MySQL 8.0 is now generally available
#17Woohoo 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
#18Earlier quoted context omitted.
The usual radix promotion that tends to occur when the major version becomes ossified. 5.8.0 -> 8.0
In what way is 5.8.0 "ossified"? I swear you're just making up terms now :P ... verb past tense: ossified; past participle: ossified 1. turn into bone or bony tissue. "these tracheal cartilages may ossify" synonyms: turn into bone, become bony, calcify, harden, solidify, rigidify, petrify "the cartilage may ossify" 2. cease developing; be stagnant or rigid. "ossified political institutions" synonyms: become inflexibl…
Re: MySQL 8.0 is now generally available
#19Woohoo 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
#20Earlier quoted context omitted.
The usual radix promotion that tends to occur when the major version becomes ossified. 5.8.0 -> 8.0
In what way is 5.8.0 "ossified"? I swear you're just making up terms now :P ... verb past tense: ossified; past participle: ossified 1. turn into bone or bony tissue. "these tracheal cartilages may ossify" synonyms: turn into bone, become bony, calcify, harden, solidify, rigidify, petrify "the cartilage may ossify" 2. cease developing; be stagnant or rigid. "ossified political institutions" synonyms: become inflexibl…
In other words, the major version became meaningless as the "minor" version changes when the major should