Open topic with navigation
Where resolution is associated with a reported issue, a Zendesk reference number is displayed, for example (9441).
This section provides a summary of the issues resolved in the release of NuoDB 3.4.
REPLACEcommand can locate and replace only existing fields containing a
NULLvalue if the new value is specified as literal null. If the new value is a complex SQL expression that evaluates to a
REPLACEstatement creates a duplicate row instead.
CASEexpressions result in unexpected errors.
CASEexpressions now return a syntax error.
UNIONclauses does not differentiate between
nuoarchive) incorrectly reports warning messages when schema objects are created using inconsistent case for the schema name.
nuoarchivecommand no longer reports warning messages for the scenario described.
START TRANSACTIONstatement does not start a new transaction if an implicitly started transaction is active and has not made any modifications.
It may not be possible to drop a table if the table is later renamed using a schema with a case different to that used when the table was created. (9441)
SQL> create schema [testschema]; SQL> create table [testschema].test(a int generated always as identity); SQL> rename table [TestSchema].test to [TestSchema].test_save; SQL> drop table test_save; SQL> sequence "testschema.test_save$IDENTITY_SEQUENCE" is referenced by table TestSchema.test_save and cannot be dropped
This issue has been resolved, allowing tables to always be dropped after they have been renamed.
STORE INclause, and the table is altered to add a partition without specifying the
STORE INclause, an error is returned indicating that no default storage group is specified. (8875)
CREATE TABLEcommand included the
STORE INclause, and a partition is added without including the
STORE INclause, the default storage group is used. In addition, a new
DEFAULTSTORAGEGROUPcolumn has been added to PARTITITIONEDTABLES which displays the default storage group for partitioned tables.
getreleaseversion()function collects the release version from every database process before also returning the common release version that all database processes are using. As a result, this function is time consuming. (9428)
getreleaseversion()is executed, is running at the most recent database version, only that release version is returned. In this case,
getreleaseversion()no longer attempts to connect to other database processes.
value) may cause duplicate values to be generated.
GENERATED ALWAYSmay result in the column having duplicate keys after subsequent inserts into the table.
CREATE TABLE, may not always be executed in the same order.
NOT NULLcolumn constraint to an existing table with data succeeds even when the column contains
READ COMMITTEDtransaction isolation and is not rolled back if the user transaction is.
CREATE INDEXstatement with concurrent
DELETEoperations on the same table may lead to duplicate or missing index keys. Or, issuing an
ALTER TABLEstatement with concurrent
DELETEoperations on the same table may lead to values violating check constraints.
ENUMtypes, with different definitions, return invalid results where an index is used for the comparison.
0x01characters returns extra