datahike.experimental.versioning — io.replikativ/datahike 0.6.1592

Git-like versioning tools for Datahike.

branch! clj

(branch! conn from new-branch)

Create a new branch from commit-id or existing branch as new-branch.

branch-as-db clj

(branch-as-db store branch)

Loads the database stored at this branch.

branch-history clj

(branch-history conn)

Returns a go-channel with the commit history of the branch of the connection in form of all stored db values. Performs backtracking and returns dbs in order.

commit-as-db clj

(commit-as-db store commit-id)

Loads the database stored at this commit id.

commit-id clj

(commit-id db)

Retrieve the commit-id for this db.

delete-branch! clj

(delete-branch! conn branch)

Removes this branch from set of known branches. The branch will still be accessible until the next gc. Remote readers need to release their connections.

force-branch! clj

(force-branch! db branch parents)

Force the branch to point to the provided db value. Branch will be created if it does not exist. Parents need to point to a set of branches or commits.

Be careful with this command as you can render a db inaccessible by corrupting a branch. You will also conflict with existing connections to the branch so make sure to close them before forcing the branch.

merge! clj

(merge! conn parents tx-data)

(merge! conn parents tx-data tx-meta)

Create a merge commit to the current branch of this connection for parent commit uuids. It is the responsibility of the caller to make sure that tx-data contains the data to be merged into the branch from the parents. This function ensures that the parent commits are properly tracked.

NOTE: Currently merge! requires that you release all connections to conn and reconnect afterwards to reset the writer state. This will be fixed in the future by handling merge! through the writer.

parent-commit-ids clj

(parent-commit-ids db)

Retrieve parent commit ids from db.