New Features

New Features in NuoDB 3.3

NuoDB 3.3 includes the following new features:

Container Native Support for Red Hat OpenShift

You can now deploy, run, and manage a NuoDB database natively inside the Red Hat OpenShift container management platform to service SQL-based applications also running in Red Hat OpenShift. For more information see Deploying NuoDB in OpenShift Environments.

Introducing NuoDB Archive

A new utility for validating and cleaning the NuoDB archive as well as restoring backups is now available. For more information, see NuoDB Archive.

Improved Performance

Performance has been improved and memory utilization has been reduced for queries where the index only partially satisfies the ordering requirements.

Performance has been improved and memory utilization has been reduced for queries with a WHERE condition similar to the following:

table1.field1 = table2.field2 AND table2.field2 = table3.field3 ...

The performance of queries with joining views containing outer joins has been improved.

New SQL Support

An optional OR REPLACE clause has been added to the CREATE command. This supports the ability to replace an existing function, procedure, trigger, or view. For more information, see CREATE FUNCTION, CREATE PROCEDURE, CREATE TRIGGER, and CREATE VIEW.

New EXPLAIN Option

A new OPT_FULL_COST option for SQL EXPLAIN statements is available. In addition to the cost and selectivity estimates shown for the index accesses this new option shows the total cost associated with accessing a given table. For more information, see EXPLAIN.

Enhancements for GRANT and REVOKE Statements

The following new functionality has been developed for the GRANT and REVOKE SQL statements:

GRANT

For more information, see GRANT.

REVOKE

For more information, see REVOKE.

New Transaction Deadlock Diagnostics

A new PRIORBLOCKEDBY column has been added to the system.transactions and system.localtransactions tables. When a transaction deadlock takes place, and one transaction is chosen to be aborted to resolve the deadlock, the PRIORBLOCKEDBY column will contain the ID of the transaction that was blocking the aborted transaction before it was aborted. For more information on the PRIORBLOCKEDBY column, see TRANSACTIONS System Table Description and LOCALTRANSACTIONS System Table Description.