We are very happy to release Kùzu 0.1.0 today! This is a major release with the following set of new features and improvements:
Kùzu 0.0.12 Release
We release Kùzu 0.0.12, another minor release. This release fixes a bug that prevents the database to be opened in read-only mode on a read-only file system. It also adds support for INT128 data type.
For more detailed information about the changes in this release, please see here.
KùzuExplorer: Visualizing Query Results and Schemas
Today, we are happy to release KùzuExplorer, which is Kùzu's browser-based frontend to visualize and explore database schemas and query results in the form of a graph, table, or in JSON. This is a very useful tool for exploring databases and debugging applications during prototyping phase. This post describes a brief overview of the main features of KùzuExplorer with pointers to KùzuExplorer documentation for details.
Kùzu 0.0.11 Release
We release Kùzu 0.0.11, another minor release. The main new feature of this release is read-only access mode for the database on Linux. The read-only mode enables the upcoming Kùzu UI to optionally open a database in read-only mode while allowing other applications to access the same database concurrently.
For more detailed information about the changes in this release, please see here.
Kùzu 0.0.10 Release
We're happy to introduce Kùzu 0.0.10, which is a minor release with a bunch of bug fixes and improvements:
- Added the frame of reference encoding for integers. PR 2140
- Fixed slicing of UTF-8 string. PR 2212
- Fixed copying of invalid UTF-8. PR 2208
- Added more checks and better error messages during the binding phase. PR 2206
- Fixed return list literal with null values. PR 2187
- Fixed bugs in scan multi label rel tables. PR 2149
- Deprecated all functions for getting the table names and properties from the client APIs and the CLI, instead,
CALL
is introduced for the same functionality. PR 2199, 2207 - Added missing data type support in client APIs. PR 2183, PR 2176, PR 2193, PR 2172
For more detailed information about the changes in this release, please see here.