Icon View Incident Report

Serious Serious
Reported By: Roy Lambert
Reported On: 4/16/2007
For: Version 1.02 Build 1
# 2326 Using an ORDER BY Clause in a Sensitive SELECT Result Set Can Cause Access Violation

I ran the following SQL statement and tried to close the result set got an av at 20747365.

select _subject, _msgno, _sent,_received from mandn
where _subject collate ansi_ci like '%addict%'
order by _subject



Comments Comments and Workarounds
The issue was that the _subject column also had a text index defined for it in addition to a normal index. ElevateDB was mistakenly trying to use the text index for the ORDER BY. Also, this issue only occurs with sensitive result sets. The workaround is to request an insensitive result set instead.


Resolution Resolution
Fixed Problem on 4/17/2007 in version 1.03 build 1


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

Image