Comments - Dynamic Columns

hello - i was under the assumption that when i switched over from mysql to mariadb, anything mysql did, mariadb does too, or at least will do it soon enough.

will we ever see the binary json data types ?

May be, but not necessarily.

Here're a couple of emails {1} and {2} with a very quick benchmark that have shown that

• MySQL binary json format is not more compact, simple VARCHAR take basically the same amount of space
• MySQL binary json is much faster than VARCHAR (7.6 seconds vs. 5.5 minutes). Obviously MySQL needs binary json format for json to be usable.
• MariaDB 10.2 is as fast on VARCHAR as MySQL on binary json, we do not need binary json for that, we're fast already.

Note that SQL standard has no JSON data type, all JSON functions should work on VARCHAR and other text data types.

Given that, there is no reason at the moment for MariaDB to support very non-standard binary JSON storage format.

i am only asking because i am trying to get a "connector" between MariaDB and deepstream.io. here is what i was told by the deepstream founder regarding using MariaDB:

The ones that work best are the ones that provide support for binary json - searchable JSON docs a la *Postgres *or *MySQL *or pub/sub as Postgres

MariaDB 10.2.3 has searchable json, but it's not stored as binary internally. MySQL's binary json is a storage format, not something that affect connectors. That is, as far as a connector is concerned, it does not matter how json is stored — binary or text. It's only important to be able to search within json documents.

ok - and lets hope this is enough to get the deepstream people to finish the connector.