immudb v1.2 is officially released and ships with some great new features!
Now, with full transactional support for everyday business applications, the open source immudb tamper-proof database can serve as the main transactional database for enterprises.
“There is no need to have immudb running next to a traditional database anymore, as immudb now has full ACID transactional integrity compliance,” said Jerónimo Irázabal, co-founder of immudb and lead architect.
immudb provides full integrity of data, as well as compatibility with SQL and key/value making it possible to move data to immudb without having to make changes to applications.
The first tamper-proof database, immudb 1.2 now has the ability to rollback changes and have data expire.
Through this immudb is now compliant with the EU’s General Data Protection Regulation (GDPR), including its “right to forget” requirements.
The GDPR went into effect in 2016 in Europe to protect privacy and govern the transfer of personal data. It is also used as a model in other countries in the world.
Unlike other databases, immudb is built on a zero-trust model: history is preserved and can’t be changed. Data in immudb comes with cryptographic verification at every transaction to ensure there is no tampering possible.
Many of the features included in this release were requested and discussed by community members, to whom we’re grateful for all the interaction and contributions!
- Full Transactions support: full ACID transactional integrity compliance both at Key-Value and SQL layer.
- Support for logical deletion and expiration of KV entries: forget about data entries by setting an expiration date or by using the delete statement.
- Support for logical deletion in SQL: it’s now possible to use the delete statement to logically delete records.
- Updates are now unconstrained: row updates can be performed for any data structure, overcoming the limit immudb had with secondary indexes.
- support for TIMESTAMP SQL type: full timestamp support when creating tables and when performing queries at microsecond precision.
- Fixes to JOIN with subquery
- INNER is now default join type
- Some improvements to error messages
- switch to standard SQL syntax for aliasing
- switch to standard SQL COUNT(*) syntax
- suport SQL for: SELECT DISTINCT, NOT LIKE, IN, IS NULL, IS NOT NULL, basic CAST (for timestamp)
- Secondary indexes with NULL values (breaking change for on-disk format in SQL layer)
- New session-based connection method in client SDK
- Initial support for golang sql stdlib