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

MySQL 8.0 is now generally available

mysqlserverteam.com

Post reply on HN
Print view View original

31–40 of 105 posts

Re: MySQL 8.0 is now generally available

#31

Post by gtirloni »

tenken wrote: post #13
yrro wrote: post #10

Earlier 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…

> maybe you're saying the 5 hasnt changed in ages

Well, how could it be anything else? You have a major version that has been maintained since 2005 [0]

0 - https://en.wikipedia.org/wiki/MySQL#Release_history

Re: MySQL 8.0 is now generally available

#32

Post by morgo »

trizinix wrote: post #14
go_prodev wrote: post #3

Woohoo 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!

As far as I am aware there is no good reason to not use MariaDB instead of MySQL. The creator of MariaDB, Monty Widenius, was on a episode of the changelog podcast if you want to hear some background as to why.

Former MySQL Product Manager here (no longer affiliated).

I've been to a Monty talk about this subject, and let me say it was interesting...

Monty starts by saying that he does not acknowledge MySQL 5.6's existence since some new features are an abomination (usually citing GTIDs).

He then compares MySQL 5.5 to MariaDB (of which MariaDB is based on MySQL 5.5; so it contains the superset of features).

MySQL 5.5 was released in 2010. Support for it will end at the end of this year.

Development has diverged a lot since 2010. For a more balanced comparison, I recommend this one: https://www.percona.com/blog/2017/11/02/mysql-vs-mariadb-rea...

Re: MySQL 8.0 is now generally available

#33

Post by jdub »

Something1234 wrote: post #26
purerandomness wrote: post #17

Earlier quoted context omitted.

Redshift is forked off an ancient Postgres version, consider using a more recent (10 or 11 beta) real Postgres version.

Like AWS redshift the nosql database or what? What is redshift postgres?

Redshift is a columnar SQL database, based on an old version of PostgreSQL.

Re: MySQL 8.0 is now generally available

#34

Post by geirhoydalsvik »

johannes1234321 wrote: post #12
crazygringo wrote: post #8

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 6 was used some 10+ years ago and has seen some alphas. Over time most things in there have been backported into the 5 series and some ideas for 6.0 didn't work out (i.e. Falcon storage engine) and were stopped. When/how 7 was used I'm not sure, but jumping from 5.7 to 8 simply drops the first digit, which was meaningless for a while already. (jumps from 5.5 to 5.6 and 5.6 to 5.7 were huge as well)

7 is used for MySQL Cluster, see also https://mysqlrelease.com/2018/03/mysql-8-0-it-goes-to-11/ Geir

Re: MySQL 8.0 is now generally available

#35

Post by dpcx »

giancarlostoro wrote: post #9
crazygringo wrote: post #8

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…

People are going to start to think tech companies don't know how to count or something. Jokes aside... I'm wondering the same.

"start to think" ?

Microsoft went from Windows 2000 to Windows XP then to Vista and then to 7. If people haven't already been thinking that, this isn't what's going to start it, IMHO.

Re: MySQL 8.0 is now generally available

#36

Post by alexanderchr »

da_chicken wrote: post #28
tenken wrote: post #13

Earlier quoted context omitted.

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…

The same thing happened with Java. After Java 1.4 they just dropped the 1 and released Java 5.

React too - 0.14.9 -> 15.0.0

Re: MySQL 8.0 is now generally available

#37

Post by meritt »

morgo wrote: post #27
meritt wrote: post #7

Earlier quoted context omitted.

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.

Former MySQL Product Manager here (no longer affiliated). To cover your specifics: MySQL was first in offering JSON with 5.7. It is still well ahead, for example, there is no JSON_TABLE, aggregate functions, native type or partial update in MariaDB. Some examples of the value here: https://mysqlserverteam.com/mysql-8-0-from-sql-tables-to-jso... Both have always had GIS support, but have taken it in a different direct…

> I am not sure which feature you refer to here

The same complaint that every single person brings up about MySQL when being compared to Postgres, including in this thread: DDL changes made during transactions cannot be rolled back.

Re: MySQL 8.0 is now generally available

#38

Post by willvarfar »

morgo wrote: post #27
meritt wrote: post #7

Earlier quoted context omitted.

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.

Former MySQL Product Manager here (no longer affiliated). To cover your specifics: MySQL was first in offering JSON with 5.7. It is still well ahead, for example, there is no JSON_TABLE, aggregate functions, native type or partial update in MariaDB. Some examples of the value here: https://mysqlserverteam.com/mysql-8-0-from-sql-tables-to-jso... Both have always had GIS support, but have taken it in a different direct…

Mariadb has JSON it just doesn't call it that - it's terminology is dynamic columns.

Source: have code that works on both.

Re: MySQL 8.0 is now generally available

#39

Post by morgo »

meritt wrote: post #37
morgo wrote: post #27

Earlier quoted context omitted.

Former MySQL Product Manager here (no longer affiliated). To cover your specifics: MySQL was first in offering JSON with 5.7. It is still well ahead, for example, there is no JSON_TABLE, aggregate functions, native type or partial update in MariaDB. Some examples of the value here: https://mysqlserverteam.com/mysql-8-0-from-sql-tables-to-jso... Both have always had GIS support, but have taken it in a different direct…

> I am not sure which feature you refer to here The same complaint that every single person brings up about MySQL when being compared to Postgres, including in this thread: DDL changes made during transactions cannot be rolled back.

MariaDB does not have that feature: https://mariadb.atlassian.net/browse/MDEV-4259
Post reply on HN