jsonparser VS textql

In this article, I will introduce you to a new package called astjson that I have been working on for the last couple of weeks. It is a Go package that allows you to transform and merge JSON objects with unmatched speed. It is based on the jsonparser package by buger aka Leonid Bugaev and extends it with the ability to transform and merge JSON objects at unparalleled performance.

Use this to extract the data value, and handle/unmarshal it accordingly.

jsonparser can decode, but can't encode

Best I've found is this: https://github.com/buger/jsonparser

I was actually just trying to get it into a []byte to use this package which claims it works well for unknown data structures.

`jj` is a little tool I wrote that uses https://github.com/buger/jsonparser

If you don't know the schema or you only need to access one or two fields in a much larger JSON object, I would recommend https://github.com/buger/jsonparser as it provides an easy API to access specific values without fully unmarshaling. This is an unusual use case though, 9 times out of 10 I would tend to use easyjson.

Reading and navigating arbitrary JSON: I've used https://github.com/tidwall/gjson, many others like https://github.com/buger/jsonparser are also out there.

I like textql [0] better for this use case, as it's simpler in my mind.

[0] https://github.com/dinedal/textql

Primarily, you are right. SQL is for working with structured data and that largely covers RDBs. However, there are tools (like textql) that allow you to query CSV files and the effort works with most other text files that have some kind of structure.

As the author of textql ( https://github.com/dinedal/textql ) - thanks for the shoutout!

Looks great, I love more options in the space for CLI based data analysis tools! Fantastic work!

Apparently, there were many who thought the same thing; Tools to execute SQL against CSV were trdsql, q, csvq, TextQL. They were highly functional, hoewver, had many options and no input completion. I found it just a little difficult to use.

Reminds me of the textQL extension that's available in Asciidoc.

Point it to an external CSV file, enable TextQL, and bam, there's your query returned as a table. Handy for parts lists, inventory, that kind of crap.

https://github.com/dinedal/textql

https://gist.github.com/mojavelinux/8856117

Through more magic, you COULD of course use stuff like Spark, or easier with programs like TextQL, sq, OctoSQL.

Somewhat-kinda related, the textql extension for Asciidoctor is so dang useful it should be in core.

https://gist.github.com/mojavelinux/8856117

I use this as a "centralized parts repository" for big ol' maintenance manuals. Refresh from PDM/PLM/LSA/Whatever. Rebuild for new parts data.

Built on TextQL, natch

https://github.com/dinedal/textql