phrrngtn / sqlite-jsoncons

SQLite extension around a small part of the jsoncons library

SQLite wrapper for JSON-related functions in jsoncons and nlohmann::json

Function include

• jmespath_search (from jsoncons)
• json_diff (from jsoncons)
• json_patch (from jsoncons)
• json_from_diff and json_apply_patch (from nlohmann::json)
• json_flatten and json_unflatten (from nlohmann::json)

sqlite_jsoncons is distributed under the Boost Software License (same license used for jsoncons)

examples

From https://github.com/danielaparker/jsoncons/blob/master/doc/ref/jmespath/jmespath.md

select jmespath_search('{"people":[{"age":20,"other":"foo","name":"Bob"},{"age":25,"other":"bar","name":"Fred"},{"age":30,"other":"baz","name":"George"}]}', 'people[?age > `20`].[name, age]');

[["Fred",25],["George",30]]

sqlite-jsoncons's Issues

get builds working for macos on arm64 and x86

The objective is to have a binary for modern macs. I thought that vcpkgs on macos-latest would cross-compile if triplet set to arm64-macos (see hack in a9cfc5d) but an examination of the build artifacts showed that it was an x86_64 binary.

Look into hosted runners from third-parties or a self-hosted runner (e.g M2 Mac mini)

unzip foobar-macos-latest-arm64-osx-19.zip
  inflating: libsqlite_jsoncons.dylib
file libsqlite_jsoncons.dylib
libsqlite_jsoncons.dylib: Mach-O 64-bit x86_64 dynamically linked shared library, flags:<NOUNDEFS|DYLDLINK|TWOLEVEL|WEAK_DEFINES|BINDS_TO_WEAK|NO_REEXPORTED_DYLIBS>

get the build working with github actions

Tried to set up github actions following instructions in https://github.com/lukka/CppCMakeVcpkgTemplate/tree/v11

When I added the vcpkg.json file and made vcpkg a submodule, I got it to work perfectly with local builds with VS Code if we DO NOT have the CMakePresets.json that comes from the CppCMakeVcpkgTemplate project. I added the demo file to the repo and committed to see if it would work with github actions and the step involving that file was the step that failed on all platforms. I am very encouraged by the fact that all the other steps seemed to work fine so I hope it will just be a case of debugging that file.