I've been using SQL on CSV and JSON lately as it's mostly easiest for me, but I can think back a few times where I've used an *awk for a specific need, AND had to deal with CSV parsing at the same time.
I've been using SQL on CSV and JSON lately as it's mostly easiest for me, but I can think back a few times where I've used an *awk for a specific need, AND had to deal with CSV parsing at the same time.
confirmed it by looking at the site just now.
You could probably use gron with awk pretty easily, since gron stands for “greppable json”.
But I also wonder how an awk with native json support would look like.
An awk with json support would for the most part need to be able to loop on hashes and arrays, and provide ways to travel in-depth. So far regular awk can travel through arrays (line-separator), and "in-depth" (e.g. nested "arrays") via regular loops & cie. Probably easier to think about it with a few concrete examples though.
[0]: http://doc.cat-v.org/bell_labs/structural_regexps/se.pdf
You mean only for strictly tabular JSON, i.e. no nesting beyond rows and columns?