Hacker News Reader

Comment by willvarfar | Hacker News Reader

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/

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 ;)

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?

Reply on news.ycombinator.com