Icon View Incident Report

Serious Serious
Reported By: Martin Hunter
Reported On: 9/17/2002
For: Version 3.17 Build 1
# 1229 Creating a Descending Index Via SQL Causes Descending Information to Be Set Incorrectly

The problem I have is when a DESCending index is created via SQL, selecting any data using this index results in a canned dataset. However, modifying some part of the index and then modifying it back again fixes the problem and we get a live dataset.

This is how to recreate the problem:

(STEP 1): Run the following SQL:

DROP TABLE IF EXISTS "TestForElevate";

CREATE TABLE IF NOT EXISTS "TestForElevate"
(
   "Date Raised" TIMESTAMP,
LANGUAGE "ANSI Standard" SORT "Default Order"
USER MAJOR VERSION 1
);

CREATE DESC INDEX IF NOT EXISTS "Date Raised Desc" ON 
"TestForElevate" 
("Date Raised");


(STEP 2):
Make sure "Want Live Result Set" is checked, and run the following
  select * from TestForElevate order by [Date Raised] desc
Result?  A CANNED result set

(STEP 3):
Use Database System Utility and Restructure the table.  On the 
secondary index 
set CASE-INS to "YES", and SAVE.

(STEP 4):
Go straight back into restructure and set CASE-INS back to "NO" again,
 and 
SAVE, thus apparently giving us exactly the table structure we 
originally set out 
with.

(STEP 5):
Rerun the SQL in STEP 2, and lo and behold, we do NOT get a Canned 
result set 
this time but but a LIVE result set.



Resolution Resolution
Fixed Problem on 9/18/2002 in version 3.18 build 1
Image