3 ms·
No, it's not at the moment. Sorry! The most useful part is doing set intersection operations on JSON array's. Probably the second is extracting a value by path
by veggieroll 2y ago
No, it's not at the moment. Sorry!
The most useful part is doing set intersection operations on JSON array's. Probably the second is extracting a value by path across both.
It's not crazy to implement, SQLite was the harder side. Just a bit of fiddling with `json_each`, EXISTS, and aggregate functions.
- nbbaier 2y agoMight give it a whirl. Is the library pure sql or is it written in something else?
- veggieroll 2y agoI've been using Go with Goqu [1] for SQL for a lot of things lately. But, the language shouldn't matter much. The functions are just building the appropriate SQL clauses. For some of the operations, the method I was using required marshaling the inputs to JSON before sending them over the wire. And that's nicer in a non SQL programming language. But both db's ultimately do have json_build_array/json_build_object for PostgreSQL or json_array/json_object for SQLite3. [1] https://github.com/doug-martin/goqu https://github.com/doug-martin/goqu