You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I don't quite understand why is this library has been deprecated in favour of dev-local.
I haven't found a way to use dev-local to manage an in-memory DB.
If that's true, then this library is still fulfilling a very important use-case, isn't it?
This library was really only intended to bridge the gap of local testing for Datomic Cloud. As Jaret said in his response, Datomic On-Prem already has the tools available to do this sort of thing. Dev-local entirely supersedes this library. It includes the complete feature set the most recent version of Datomic supports (tuples, xform, index-pull, etc). It will also fail in the same ways Datomic Cloud client calls will fail.
dev-local does create and maintain DB data on the filesystem. With a small bit of work, you can make it work just like the in-memory library. We have released dev-local-tu to help with this. As far as I can tell, this will give you everything that you had before with Datomic free + datomic-client-memdb. I have also written a small accompanying blog post on using dev-local for tests. I'd be curious to hear if you hit a particular case this new approach does not cover.
I don't quite understand why is this library has been deprecated in favour of
dev-local
.I haven't found a way to use
dev-local
to manage an in-memory DB.If that's true, then this library is still fulfilling a very important use-case, isn't it?
I did ask about this on the Datomic forum too just now:
https://forum.datomic.com/t/dev-and-test-locally-with-dev-local/1518/11?u=onetom
The text was updated successfully, but these errors were encountered: