MySQL 8.0 is now generally available • Hacker News Board

Re: MySQL 8.0 is now generally available

#41

Post by morgo » Thu, Apr 19, 2018, 3:52 PM UTC

willvarfar wrote: post #38

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…

Mariadb has JSON it just doesn't call it that - it's terminology is dynamic columns. Source: have code that works on both.

It has both (now). It's a stretch to say Dynamic columns are on the same level. For example, could you index them with virtual generated columns? The syntax is also not as transparent to applications as the ->> JSON operator.

Re: MySQL 8.0 is now generally available

#42

Post by johannes1234321 » Thu, Apr 19, 2018, 3:52 PM UTC

willvarfar wrote: post #38

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…

Mariadb has JSON it just doesn't call it that - it's terminology is dynamic columns. Source: have code that works on both.

There s a difference: MySQL has specific a datatype for JSON aside from only having JSON-related functions working n strings, which has a few benefits:

* The JSON datatype guarantees the content is valid JSON

* access to fields can be faster even without dynamic/virtual columns

* since 8.0 there are special optimizations for doing partial updates, which means that not the full JSON data has to be rewritten on small changes https://mysqlserverteam.com/partial-update-of-json-values/

Re: MySQL 8.0 is now generally available

#43

Post by ta65377777 » Thu, Apr 19, 2018, 3:58 PM UTC

I demand satiation.

Re: MySQL 8.0 is now generally available

#44

Post by semiquaver » Thu, Apr 19, 2018, 3:58 PM UTC

superice wrote: post #15

orf wrote: post #5

Earlier quoted context omitted.

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?

There are some nice features that MySQL lacks. Personally, the thing I like best in Postgres is transactional DDL. In MySQL, if halfway through a database transformation your migration script fails, you are in a broken state and you are on your own. Postgres rolls the whole transaction back. Ofcourse there are some other features MySQL lacks, such as variable length character columns (varchar) where you don't need to…

> The transactional DDL seems to be introduced in MySQL per 8.0 though

I thought so as well from the release note wording, thanks to theptip for confirming in the docs that DDL is not transactional in 8.0, just crash-safe. see https://news.ycombinator.com/item?id=16876549.

Re: MySQL 8.0 is now generally available

#45

Post by pmuk » Thu, Apr 19, 2018, 4:01 PM UTC

Does anyone have any idea when this will be available on Amazon RDS?

Re: MySQL 8.0 is now generally available

#46

Post by weavie » Thu, Apr 19, 2018, 4:05 PM UTC

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.

This confused me for ages. Only after reading your comment do I finally understand what happened here!

Re: MySQL 8.0 is now generally available

#47

Post by willvarfar » Thu, Apr 19, 2018, 4:17 PM UTC

morgo wrote: post #41

willvarfar wrote: post #38

Earlier quoted context omitted.

Mariadb has JSON it just doesn't call it that - it's terminology is dynamic columns. Source: have code that works on both.

It has both (now). It's a stretch to say Dynamic columns are on the same level. For example, could you index them with virtual generated columns? The syntax is also not as transparent to applications as the ->> JSON operator.

Oracle owns the JavaScript trademark and has started enforcing it. Kinda wise in hindsight that Mariadb didn't call it json?

I think Mariadb was there first. I think the format is very similar at the bit level, but the MySQL has nicer API with automatic returning it as text to apps rather than exposing the bits. I dislike json_extract and wish >> worked but it doesn't seem to on my percona server :(

Anyhow, you'll look back when you've got more distance from Oracle and realize that you don't need to try and convince yourself that MySQL was better quite so hard ;)

Re: MySQL 8.0 is now generally available

#48

Post by riku_iki » Thu, Apr 19, 2018, 4:26 PM UTC

pmuk wrote: post #45

Does anyone have any idea when this will be available on Amazon RDS?

Default comment in such topics )

Re: MySQL 8.0 is now generally available

#49

Post by cdevnull » Thu, Apr 19, 2018, 4:28 PM UTC

dancek wrote: post #2

There 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 main reason I don't use mariaDb is the non support of nullable spatial index.

https://mariadb.com/kb/en/library/spatial-index/

Re: MySQL 8.0 is now generally available

#50

Post by morgo » Thu, Apr 19, 2018, 4:29 PM UTC

willvarfar wrote: post #47

morgo wrote: post #41

Earlier quoted context omitted.

It has both (now). It's a stretch to say Dynamic columns are on the same level. For example, could you index them with virtual generated columns? The syntax is also not as transparent to applications as the ->> JSON operator.

Oracle owns the JavaScript trademark and has started enforcing it. Kinda wise in hindsight that Mariadb didn't call it json? I think Mariadb was there first. I think the format is very similar at the bit level, but the MySQL has nicer API with automatic returning it as text to apps rather than exposing the bits. I dislike json_extract and wish >> worked but it doesn't seem to on my percona server :( Anyhow, you'll lo…

JSON is part of the SQL 2016 standard and exists in other databases as well. I don't see how the trademark is relevant here.

I wish we could be more civil and not resort to petty insults. Is there anything I wrote you can dispute with a source?