>
> At least in Cosmos, there’s a good story with the indexing policy that’s
> very configurable. (Including fully automated if that’s what you need)
>
Indeed! We're using CosmosDB elsewhere in the suite, so I'm going to make a
demo on the weekend where the "reports" are saved in Cosmos. The
tps://sqldownunder.com/> |
About Greg: https://about.me/greg.low
From: Greg Keogh via ozdotnet
Sent: Friday, 2 September 2022 10:52 AM
To: ozDotNet
Cc: Greg Keogh
Subject: Re: Indexed JSON documents (file system)
I found this: https://github.com/ketanip/dbjson hope it helps.
If I had to do it myse
>
> I found this: https://github.com/ketanip/dbjson hope it helps.
>
If I had to do it myself I'd probably do something similar, maybe use
SQLite to hold an index of the properties of JSON documents. I would have
to walk every document's tree (fragile) and the hierarchy of properties
would have
And also this: https://github.com/SleekwareDB/sleekwaredb
regards,
Preet, in Auckland NZ
On Fri, 2 Sept 2022 at 12:28, Preet Sangha wrote:
> I found this: https://github.com/ketanip/dbjson hope it helps.
>
> regards,
> Preet, in Auckland NZ
>
>
>
> On Fri, 2 Sept 2022 at 11:20, Greg Keogh
Folks, back to work.
I'm trying to convince some colleagues that they should persist "reports"
from a product as JSON instead of a fiddly custom text format. Each
"report" looks a lot like a self-contained document to me, with a few
sections containing the parameters, layout and data of the
