Icon View Incident Report

Serious Serious
Reported By: Alan Craker
Reported On: 11/4/2010
For: Version 2.04 Build 4
# 3345 ElevateDB Server Not Sending Modified Flags for Default Column Values Back to Remote Sessions

We are having an issue regarding publishing tables and default field values. The development environment is C++ Builder 2007 and EDB 2.03b19. The table has a GUID primary key which is getting set by a default value of CURRENT_GUID and is defined as:

"GUID" GUID DEFAULT CURRENT_GUID NOT NULL

The program is using a TEDBTable component to access the table. When a record is inserted, the GUID field is not set through code and is correctly given a new value when posted to the table. However, when this table is published and an insert is performed, the GUID value is not getting saved in the .EDBPbl file. When the updates are saved and then loaded at a remote location, the record is inserted, but is given a different primary key value. This then of course creates all sorts of problems…

I get the same results using both remote and local sessions and have been able to reproduce this on several PCs here, but for some reason cannot get this behavior on my development machine. In further testing, I get the same results for other non-primary key fields with different data types and default values.


Comments Comments
The problem was caused by the fact that default column values were setting the modified flag for the column in the row buffer on the ElevateDB Server, but this modified flag was not being transferred back to the remote session on the client. Therefore, when the client sent back the row for insert, the default value would not be considered as modified, and would not be logged as a published update, nor would any dependent indexes be updated.

This fix is what required the switch to the 2.05 release number, due to the fact that the ElevateDB Server call-level API needed to change in order to make sure that the modified flags for the row buffers were transferred back to the remote session during the initialization of a row.


Resolution Resolution
Fixed Problem on 11/11/2010 in version 2.05 build 1


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