OriginChainDB / Release notes
The product is now OriginChainDB, at originchaindb.com. Decimal values compare by value, busy databases stay responsive, and the Elasticsearch-compatible API supports index aliases and aggregations over every matching document.
Our product is now called OriginChainDB, and its website and docs live at originchaindb.com. Links to the previous web address forward to the new one. Database connection addresses did not change with the rename, so nothing in your application needs updating.
A NUMERIC or DECIMAL column compared with an INTEGER column is now compared by value, in single tables, join keys and filters, on the SQL API and on PostgreSQL connections. A CASE condition over a decimal column compares by value too, as in PostgreSQL.
SELECT o.id FROM orders o JOIN credits c ON c.amount = o.total
A large table scan no longer holds up other clients of the same database, and bursts of prepared statements from many connections are paced. When heavy work is at its limit, a request waits briefly and then gets a clear “retry shortly” answer.
At that limit, PostgreSQL and MySQL clients can get SQLSTATE 53000 (MySQL error 1041) when preparing a statement. The statement did not run: retry it with back-off, and inside a transaction roll back and retry the whole transaction.
The Elasticsearch-compatible API supports index aliases, and aggregations now run over every matching document.