Icon View Incident Report

Serious Serious
Reported By: Terry Swiers
Reported On: 12/25/2018
For: Version 2.29 Build 1
# 4712 Switching RequestSensitive Property Between Query Executions Can Cause Filter Not Found Error

Cached statements that are initially cached with sensitive results throw the following error if they are executed a second time with insensitive results: ElevateDB Error #1001 A filter error occurred (Filter not found)

Steps to reproduce in EDB Manager:

1. Create a database, (a memory database will work), in a remote session that has the statement caching set to anything greater than zero.

2. Create a table with a single column such as:

CREATE TABLE "TestTable" ("aColumn" SMALLINT)

3. Run the following query with the "Request Sensitive Result Set" option checked:

select * from testtable where acolumn = 1

4. Uncheck the "Request Sensitive Result Set" option and click Execute again.


Resolution Resolution
Fixed Problem on 12/28/2018 in version 2.30 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