Connection
Related Docs:
object Connection
| package datomisca
Retrieves a value of the database for reading.
Retrieves a value of the database for reading.
Does not communicate with the transactor, nor block.
the current value of the database.
Retrieves a value of the log for reading.
Retrieves a value of the log for reading.
Note: the mem db has no log, and thus for it log will return null.
(Copied from Datomic docs.)
the current value of the log.
Request the release of resources associated with this connection.
Request the release of resources associated with this connection. Copied from Datomic Javadoc: Method returns immediately, resources will be released asynchronously. This method should only be called when the entire process is no longer interested in the connection. Note that Datomic connections do not adhere to an acquire/use/release pattern. They are thread-safe, cached, and long lived. Many processes (e.g. application servers) will never call release.
Used to coordinate with other peers.
Used to coordinate with other peers.
Returns a future that will acquire a database value with basisT >= t.
database() is the preferred way to get a database value,
as it does not need to wait nor block. Only use sync(t)
when coordination is required, and prefer over sync() when
you have a basis t.
Does not communicate with the transactor, so the future may be available immediately. The future can take arbitrarily long to complete. Waiters should specify a timeout.
a basis t.
an implicit execution context.
Returns a future that will acquire a database value guaranteed to include all transactions that were complete at the time sync was called.
Used to coordinate with other peers.
Used to coordinate with other peers.
Returns a future that will acquire a database value guaranteed to include all transactions that were complete at the time sync was called. Communicates with the transactor.
database() is the preferred way to get a database value, as
it does not need to wait nor block. Only use sync() when
coordination is required, and you don't have a basis t.
Communicates with the transactor. The future can take arbitrarily long to complete. Waiters should specify a timeout.
an implicit execution context.
Returns a future that will acquire a database value guaranteed to include all transactions that were complete at the time sync was called.
Used to coordinate with background excision.
Used to coordinate with background excision.
Returns a future that will aquire a database value that is aware
of excisions through time <= t.
Does not communicate with the transactor, so the future may be available immediately. The future can take arbitrarily long to complete. Waiters should specify a timeout.
a basis t.
an implicit execution context.
Returns a future that will acquire a database value
that is aware of excisions through time <= t.
Used to coordinate with background indexing jobs.
Used to coordinate with background indexing jobs.
Returns a future that will acquire a database value that is indexed through time <= t.
Does not communicate with the transactor, so the future may be available immediately. The future can take arbitrarily long to complete. Waiters should specify a timeout.
a basis t.
an implicit execution context.
Returns a future that will acquire a database value that is indexed through time <= t.
Used to coordinate with background schema changes.
Used to coordinate with background schema changes.
Returns a future that will acquire a database value that is aware of all schema changes through time <= t.
Does not communicate with the transactor, so the future may be available immediately. The future can take arbitrarily long to complete. Waiters should specify a timeout.
a basis t.
an implicit execution context.
Returns a future that will acquire a database value that is aware of all schema changes through time <= t.