Fork me on GitHub
#asami
<
2022-09-05
>
simongray08:09:47

Is there a built-in way to make a unified graph that is both in-memory, but with certain triples persisted on disk? I need to store some user-generated content, but most of the data is generated afresh from an input dataset of XML files on restarts and only exists in-memory.

quoll11:09:09

Such a thing is written but is not yet exposed in any way (I was actually working on it last night). It's a graph that is a Union of in-memory and on disk data. It's in: https://github.com/quoll/asami/blob/main/src/asami/wrapgraph.cljc

🙏 1
quoll11:09:28

You COULD insert data into a database, get the graph out of it, wrap it, and then build a new connection to that graph

quoll11:09:01

It would actually only be a few function calls

quoll11:09:46

The Database history won't work properly yet. This is part of what I hope to do today

quoll11:09:11

Another feature I’d like to have is the ability to query graph unions, like in SPARQL (I use this feature a lot, and I want it for Asami too)

quoll11:09:41

But… I don't have the resources to get that done soon

simongray11:09:54

Thank you, Paula!

simongray11:09:19

I’ll experiment with it

quoll22:09:20

Have you ever written code that took you far too long to get done, and when you've got to that "it compiles!" point you have a sense of relief, and you just want to celebrate, even though you have yet to run and test it?

quoll22:09:38

Well... that's where the with function is now.

quoll22:09:44

at long last

1
🙌 1
quoll22:09:57

tests will be forthcoming, and then I can make a release

💯 2