← Back to team overview

maria-discuss team mailing list archive

Fwd: Re: The future of Dynamic Columns



Sorry I forgot to put in in the list.

-------- Forwarded Message --------
Тема: 	Re: [Maria-discuss] The future of Dynamic Columns
Дата: 	Wed, 28 Jan 2015 23:44:39 +0100
Від: 	Oleksandr Byelkin <sanja@xxxxxxxxxxxxxxxx>
Кому: 	Roberto Spadim <roberto@xxxxxxxxxxxxx>

Hi, Roberto!

On 28.01.15 23:13, Roberto Spadim wrote:
Hi Peter :) i will talk about what i used and what i consider
interesting to have,

2015-01-28 19:25 GMT-02:00 Peter Laursen <peter_laursen@xxxxxxxxxx

    @Roberto.  A comment to "i think it's a nice human readable format
    for arrays/objects, nothing less nothing more".

    But why will you then need to **store** as JSON?

about "store":
1) it's nice to read data without any tool (function), it's easy to
read a object or a array, maybe could use YAML or any other format (i
don't like XML cause it consume too many space)
2) saving json could optimize cpu use at php/application server
without decode data every read (if you use json a lot, not my case)
3) could be nice to export/import data? i don't know, today i use
table dump when i need, or a small script or pre defined data format

about "json internally implemented at database / store":
1)seach with index, jpath/xpath or others functions, consume less
space when possible json/xml specific field type
2)today when i use json i save using a blob column and execute a
compress() function when possible, sometimes i don't care about
datasize, and only save at blob columns (or maybe varchar when data is
Actually saving JSON as is looks so inefficient that even MongoDB store