Datomic Pro full changelog

Improvement: Getting log value from a connection is now much faster
Improvement: `restore-db` now prints basis of restored database
Improvement: Metrics can now be enabled during backup/restore
Fixed bug: `:db.fn/retractEntity` no longer throws an exception when passed an invalid entity identifier

New feature: Query timeout
Improvement: The datalog engine will now do self-unification within a single
clause.
Improvement: Better semantics for query function `/`

Note: We are looking for feedback on this initial release of `not` clauses and
or` clauses described below. The API is subject to change based on this feedback.
New feature: `not` clauses
New feature: `or` clauses

New feature: Pull
New feature: Query find specifications
New feature: Query pull expressions
New: `Peer.getDatabaseNames`

Notice: PostgreSQL is no longer shipped with the Datomic peer library.
If you are using PostgreSQL, see the section in the storage docs about
JDBC drivers for help with configuring your peer with this upgrade:
http://docs.datomic.com/storage.html#sql-database

New: The transactor and peer now require Clojure 1.6.0 or greater
Fixed bug that could cause a transactor to become unresponsive after waking
from laptop sleep

This release optimizes the repair job introduced in 0.9.4880 to minimize its impact on live systems.

Fixed bug where processes would sometimes prefer an old ident over a new one after a restart.

Transactors now use the G1 garbage collector, and require Java 7 or later. (Peers continue to work with Java 6 or later.)
Database backups to S3 can now use '--encryption sse' to request server-side encryption
Better defaults and more configuration options for I/O utilization during backup and restore. The defaults are now good for most scenarios.
Updated AMIs across all regions with current Amazon Linux distributions and support for HVM-based instances
SQL storage users can now configure the pool validation query via datomic.sqlValidationQuery`, default is "SELECT 1".
Re-enable metrics that were inadvertently disabled in 0.9.4815, e.g.
StorageGetMsec` and `StoragePutMsec`.
Integrity validations added in newer versions of Datomic no longer
prevent loading older non-compliant databases.

Transactors now use the G1 garbage collector, and require Java 7 or later. (Peers continue to work with Java 6 or later.)
Database backups to S3 can now use '--encryption sse' to request server-side encryption
Better defaults and more configuration options for I/O utilization during backup and restore. The defaults are now good for most scenarios.
Updated AMIs across all regions with current Amazon Linux distributions and support for HVM-based instances
Added support for more Amazon instance types
Prevented race condition in `deleteDatabase` that could tie up a thread writing error messages in the log
Fixed bug where peers that were offline during a transaction would not see fulltext for the offline time until next indexing job completes
Better protection against retracting schema entities. If you encounter the following error
java.lang.IllegalArgumentException: :db.error/invalid-install-attribute
at datomic.error$arg.invoke(error.clj:55)