On 21-01-18 17:15, Brian Curley wrote: > Well, I did oversimplify to just say 'pipe it through', but it's really > more like a sed usage. > > You wouldn't see much difference if you'd pipe your delimited output > through sed or awk either, unless you threw in some directives, or a > script. It would require some planning on the part of the user, but there's > a cookbook on the jq site that covers this. > > > https://github.com/stedolan/jq/wiki/Cookbook#convert-a-csv-file-with-headers-to-json > > > There's other takes on this same recipe out there, on StackExchange, etc. > > As with any such localized solution, once you get it working, you can use > it seamlessly as a function or an aliased call. > > Regards. > > Brian P Curley > > > > > On Jan 21, 2018 10:15 AM, "Luuk" <luu...@gmail.com> wrote: > > On 21-01-18 16:05, Brian Curley wrote: >> Is there even a need to embed it into sqlite itself? Since you're on the >> shell, and in keeping with the whole 'do one thing well' mandate: pipe it >> through jq instead. >> >> Beautiful creature that jq... >> >> Regards. >> >> Brian P Curley >> >> > luuk@opensuse:~/tmp> echo 'select * from test;' | sqlite test.db > 1 > 2 > 3 > luuk@opensuse:~/tmp> echo 'select * from test;' | sqlite test.db | jq > 1 > 2 > 3 > > Can you give an example please? > _______________________________________________ >
Thanks, will look at it, when i'm doing someting with JSON, and CSV _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
