Support migration to datomic, support for saving datoms in nippy, refactoring of core #6
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR makes the following contributions to Wanderung:
transact-datoms-to-datomic
for putting data into datomicwanderung.core
and the commandline interface.An important change that I made to the interface of the program is that instead of passing a
-d
or--direction
option specifying the type of source and target databases on the commandline, the type of database is instead stored under the key:wanderung/type
in the database configuration. I am happy to discuss whether this is a good or bad idea. So for instance, the config of a datomic database now looks like this:and, for example, the configuration for a file that stores nippy-encoded datoms looks like this:
The main reason for this change is that it leaves less room for mistakes since it is no longer possible to specify a direction with the
-d
flag that is inconsistent with the configurations.We wrote this code at Jobtech to be able to create and restore backups of our Taxonomy database.