Open topic with navigation
Where changes relate to a Zendesk issue, the associated Zendesk reference number is displayed. For example, (9424).
This section provides an overview of the major changes included with NuoDB 3.4.1.
The NuoDB SQL (
nuosql) command line tool now supports inline comments ('–') when used in interactive mode.
For information on using
nuosql, see Using NuoDB SQL Command Line.
NuoDB Optimizer can now perform shallow table and index scans for queries using aggregate functions count and sum over constants. (9431)
This section provides an overview of the major changes included with NuoDB 3.4.
The introduction of Transactional DDL (see New Features) may impact behavior of existing DDL operations for current NuoDB customers. For example:
CREATE INDEXnow automatically locks a table from writes for the time it takes to create the index.
ALTER TABLE CHANGE DATATYPEnow converts all data values to the new data type.
For details of changes relating to transactional DDL, contact NuoDB Support.
The performance of memory management capabilities introduced in NuoDB 3.2 has been improved.
The internal object identifier data type has been changed from
BIGINT. As a result, the data type for the
OBJECTID column in the TABLES table, the ALLSYSTEMTABLES table, and the SEQUENCES table has been changed from
BIGINT. Also, the data type for the
SYSTEM_ID column in the SCHEMAS table has been changed from
BIGINT. For more information on these tables, see TABLES System Table Description, ALLSYSTEMTABLES System Table Description, SEQUENCES System Table Description, and SCHEMAS System Table Description.
Previously, to use the
UPDATE privileges were required for the target table. Now,
DELETE privileges are required.
Since enabling statement caching in the NuoDB DataSource can result in statement timeouts, statement caching capabilities have been removed from the NuoDB DataSource.
The changes required to resolve issues with the ordering of timestamp values, and to support trailing spaces in indexes, may require certain indexes to be rebuilt in NuoDB 3.4. If an index contains columns of date or time date types, or if the column contain strings with trailing spaces, it will be necessary to rebuild indexes.
Previously, log messages incorrectly implied that a transaction was not committed:
TE shutdown was requested before the transaction successfully committed
TE shutdown was requested before the transaction successfully prepared
In certain circumstances, it is possible that a transaction may have been committed after the TE shut down. As a result, error messages have been changed to display as follows:
TE shutdown while committing
TE shutdown while preparing
The state of the transaction needs to be validated by the application. For more information, see Behavior If Connection to a Database is Lost.
The JDBC and Hibernate drivers are now shipped independently from the NuoDB database. As a result, these drivers have been removed from the NuoDB database installation package and are now available from the Maven repository. For more information, see NuoDB Drivers Available at Other Public Sites.