Tom added a comment - 2015-02-01 02:59 There is a related question. Dynamic columns allow BINARY values. JSON cannot in general represent binary data. At present, if a dynamic column has a BINARY value then COLUMN_JSON just puts it in quotation marks and sends it. If the document is utf8 then this usually means that the document returned is not valid JSON. Most JSON encoders reject inputs that cannot be encoded with an error but Maria instead returns an invalid document that cannot be decoded using normal JSON libraries. However, I don't know what the right behavior should be.

Claudio Galdiolo added a comment - 2016-04-07 17:54 - edited Server version: 10.1.13-MariaDB - Homebrew -- this returns a valid json string SELECT COLUMN_JSON(COLUMN_CREATE( 'test' , 'Text "escape"' )) AS json; +----------------------------+ | json | +----------------------------+ | {"test":"Text \"escape\""} | +----------------------------+ -- this does not return a valid json string SELECT COLUMN_JSON(COLUMN_CREATE( 'test' , 'First line\nSecond line' )) AS json; +-----------------------------------+ | json | +-----------------------------------+ | {"test":"First line Second line"} | +-----------------------------------+ The valid json output for the last query should be: +------------------------------------+ | json | +------------------------------------+ | {"test":"First line\nSecond line"} | +------------------------------------+