Icon View Incident Report

Serious Serious
Reported By: Tom Haug
Reported On: 3/2/2011
For: Version 2.05 Build 3
# 3391 ERROR Triggers Consuming Exceptions Even When WHEN Clause Evaluates to False

We have ERROR ALL triggers with a condition of LOADINGUPDATES() on our tables to trap replication errors. However, with these in place, it appears that primary key constraint errors during normal program operation are not being thrown any more. Instead of generating an error, the active record is changed to the original row with the duplicate primary key. In the code, we are wrapping table posting in try/catch blocks and we are never notified that an error occurred.


Comments Comments
An errors that aren't handled by at least one ERROR trigger are now raised properly as exceptions, and any time an operation does not complete due to an error, the row pointer will not move. This will be true even if the error is consumed by an ERROR trigger.


Resolution Resolution
Fixed Problem on 3/3/2011 in version 2.05 build 4


Products Affected Products Affected
ElevateDB Additional Software and Utilities
ElevateDB DAC Client-Server
ElevateDB DAC Client-Server with Source
ElevateDB DAC Standard
ElevateDB DAC Standard with Source
ElevateDB DAC Trial
ElevateDB LCL Standard with Source
ElevateDB PHP Standard
ElevateDB PHP Standard with Source
ElevateDB PHP Trial
ElevateDB VCL Client-Server
ElevateDB VCL Client-Server with Source
ElevateDB VCL Standard
ElevateDB VCL Standard with Source
ElevateDB VCL Trial

Image