Sounds good, I’ll have a look at it. We have some protocols for different index structures in datahike, where we can also persist it to some sql dbs at some point.
pretty cool @mihaelkonjevic, i'll try it out later, i was thinking on doing a proof-of-concept driver with Redis using konserve-carmine
@bandarra This is how my patched datahike.api
file looks now
I’ll have a look.
thanks ♥️
With the new index protocols and schema integration, we moved a little bit this part, but it should be easy integrating it in the new namespaces.
@konrad.kuehne Do you think it would be possible to make it so we can use either multimethods or records instead of strings to setup the storage backends? It would make it easier to extend it from outside, and probably extend storage capabilities (for instance you could pass in a storage that is using a db pool)
That is the plan. I’m thinking of something similar of what I’m doing with different indices.
you can see the current version here: https://github.com/replikativ/datahike/blob/32-index-protocol/src/datahike/index.cljc
at the moment I have only some ideas how to do that, but if you like I could share my thoughts on the datahike wiki.
@konrad.kuehne that would definitely be helpful
a proof-of-concept implementation of pluggable stores using multimethods https://github.com/purrgrammer/datahike/pull/1/files
not sure if is what @konrad.kuehne had in mind tho