BUG: Index on date field breaks "eqf @TD" selection

[Jay R. Ashworth]

Thanks to Jeff Harrison for having this solution at the top of his
head; it was in fact my problem...

===

I have a file with a date field (86) which is (10,MDYY/).

I have processing which runs using a selection 

:86:eqf:@TD

Before I did some on-site work on the system yesterday, the code
running that selection worked fine; today, it could not select the 8
records with today's date in field 86.

:86:eqf:@T4

likewise didn't work.


A *manual* selection:

:86:eq:03/13/2007

did work.


The problem Jeff pointed out to me was that I had built an index on
field 86, to make interactively finding some dirty data easier.  (He
didn't know I'd built an index, but he did suggest to me that an
index's existance could cause this.)

He speculates, and I concur, that this was triggering index scan, and
that for some reason, that was breaking the selection.

It failed with both short and extended selections; it *succeeded* when
I either a) ran dclerk with PFIXS=off or b) removed the index.

The dclerk is 4.8.3K2D4

===

Is this a known bug?  Has it been fixed in later releases?

Cheers,
-- jra
-- 
Jay R. Ashworth                                                jra at baylink.com
Designer                          Baylink                             RFC 2100
Ashworth & Associates        The Things I Think                        '87 e24
St Petersburg FL USA      http://baylink.pitas.com             +1 727 647 1274