INSERT, DELETE and UPDATE statements executed in a stored procedure called from a fired trigger were incorrectly transaction logged.

Certain BIT(96) to CHAR(24) CASTs could crash the server.

Incorrect optimization of a sub-select with outer column references could cause an infinite loop.

An INSERT privilege check related to a flat-file could crash the server.

"ORDER BY " could crash the server.

Extremely (>255 characters) long procedure names could crash the server.

Specifying a cache setting when creating a LookSee index would cause the server to deadlock.

The replication mechanism failed when a blob handle was referenced more than once in a transaction.

SELECT -(SELECT SUM(c0) FROM t0) FROM t0; caused the server to crash.

Implementation of ON UPDATE CASCADE clause in a FOREIGN KEY constraint was incorrect in certain nested cases.

Interval day-time literals was incorrectly transaction logged.

Occurrence of transaction conflict in the replication management was incorrectly handled.


The new sql92 command


can be used to protect as sequence of sql statements stating with the PROTECT statement and ending with and including a COMMIT or a ROLLBACK statement against transaction conflicts. If a transaction conflict is detected during the execution of the sequence of statements, the whole sequence is executed again after DELAY seconds. That process is repeated at most COUNT times. The default for DELAY is 10 and and the default for COUNT is 3.