Icon View Incident Report

Serious Serious
Reported By: Daniel Lundin
Reported On: 12/1/2005
For: Version 4.22 Build 1
# 2141 Restricted Transactions Not Acquiring Proper Write Locks During Commit

My server app has a separate thread that waits for changes in a number of tables (StrictChangeDetection is used) and when any changes has been detected, it goes through every records in these tables. First a filter is applied, and based on the filter it is determined if there is any records that needs to be changed or deleted. When this is done, the filter is removed. This is repeated continuously, but after a while RecordCount reports 0, even if there is records in the table that meets the conditions in the filter. The problems perists until the table is closed and then reopened.

After some more research it boils down to this: If a client adds records within a "restricted transaction" , filtering a table in the server seems to stop working until either the table is closed and then reopened or until a record is added or deleted and then "reapplying" the filter again.

Comments Comments and Workarounds
The workaround is to use a non-restricted transaction.

Resolution Resolution
Fixed Problem on 12/7/2005 in version 4.22 build 2

Products Affected Products Affected
DBISAM Additional Software and Utilities
DBISAM CLX Client-Server
DBISAM CLX Client-Server with Source
DBISAM CLX Standard with Source
DBISAM ODBC Client-Server
DBISAM ODBC Client-Server with Source
DBISAM ODBC Standard with Source
DBISAM VCL Client-Server
DBISAM VCL Client-Server with Source
DBISAM VCL Standard with Source