Simon. You want something like MySQL but using SQLite's shallower column type awareness? Reference:
https://dev.mysql.com/doc/refman/5.7/en/mysql-shell-json-output.html Would you include a header variable when headers are turned on? Column types too? There are a number of design choices to work out, but the new code and test cases would be entirely isolated to shell.c The output mode is just formatting and indentation changes and the input mode can crib from json1.c input routine. Have you considered writing a reference implementation for a new mode_json case of shell_callback to work out a practical design? The other possibility would be to upgrade json1.c to allow update/insert/delete and readout/writeout of current table in JSON format. Given the trouble with integrating SQLite shell into every situation, such a readout mode for json1.c could have wider utility. Others have run into the same portability problem with the read only csv.c extension. Peter On Sun, Jan 21, 2018 at 11:54 AM, Simon Slavin <slav...@bigfraud.org> wrote: > > > On 21 Jan 2018, at 6:56pm, Brian Curley <bpcur...@gmail.com> wrote: > > > In short, yes...you can get jq to convert both ways. > > > > It's not exactly as simple as just piping it through jq though, just to > > reiterate my earlier self-correction. > > Hi, Brian. Thanks for your detailed example which I read. I can see that > the tasks can be done by jq. But I think the SQLite shell tool, which > knows which key/column names to use, will do them faster and with far less > work from the user. > > Simon. > _______________________________________________ > sqlite-users mailing list > sqlite-users@mailinglists.sqlite.org > http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users > _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users