Clojurians Log v2

Yes, i think it is heading there, but @grounded_sage would be able to tell you more.

@robert.mather.rmm we are working on this right now. Hoping to have an initial version soon. But still bit of work to go for full API and before we would declare it stable.

@robert.mather.rmm It's a little more work than it sounds like because with Cljs if the storage is durable (indexDB or whatever, vs in memory) then all of the IO operations have to be async, which means all of the query logic has to be adapted to accomodate this.

However, if you need durability but aren't expecting a ton of data, you could always just write to disc, but query the data from an in-memory db, till a proper indexdb implementation is ready.

@grounded_sage Is that work going on somewhere public?

@metasoarous You mean like sync the whole db to LocalStorage after each op? Fortunately I found Mamulengo (https://github.com/wandersoncferreira/mamulengo), which seems to work and saves to LocalStorage. Not sure of the internals, maybe just doing what I would have done to hack it together. This should hold me for a while.

Yeah, that should get you by ok. I'll note though that since that project seems to store transactions individually, eventually you'll get so many transactions that it may take a while for it to boot up. Unless it's also periodically taking snapshots of the EAV index to boot from. Probably fine if you're just looking to tide yourself over until we get this full support in datahike.

@robert.mather.rmm work is currently happening on a fork. When we have it in a decent shape for others to start experimenting with it this will be placed onto a feature branch of the official repository.