@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? Could not something like "SELECT .. INTO JSON ..." do the trick? (with hindsight: "SELECT .. INTO XML ..." could have been implemented in MySQL when other XML functionalities were implemented but never was, it seems. You can mysqldump to XML but not "SELECT .. INTO XML ..." - using OUTFILE or not - refer http://dev.mysql.com/doc/refman/5.6/en/select-into.html) -- Peter On Wed, Jan 28, 2015 at 7:29 PM, Roberto Spadim <[email protected]> wrote: > i think a good start is "expression indexes" and after json syntax to SQL > language, and some new functions to handle json/etc > > CREATE INDEX name ON table ( some_function(field) ) > maybe dynamic column functions, or json functions? or any function > deterministic (for example, NOW() function can't be used) > > and use it at WHERE clausules > > WHERE some_function(field) ='1234' <- use index > WHERE some_function(table.field) ='1234' > WHERE some_function(field) IN ( sub select ) > WHERE some_function(field) LIKE "blabla%" > WHERE some_function(field) LIKE "%blabla%" > WHERE some_function(field) LIKE "%blabla" > > _______________________________________________ > Mailing list: https://launchpad.net/~maria-discuss > Post to : [email protected] > Unsubscribe : https://launchpad.net/~maria-discuss > More help : https://help.launchpad.net/ListHelp > >
_______________________________________________ Mailing list: https://launchpad.net/~maria-discuss Post to : [email protected] Unsubscribe : https://launchpad.net/~maria-discuss More help : https://help.launchpad.net/ListHelp
