Hi

Delphi 2007 - 2.02 Build 2


I have found a new bug in EDBTable.FindNearest

i have a index for : INTFIELD1.

table :

INTFIELD1
1
1
1
2
2
3
3
3
3
5
5
5
5

note :
4 dont' exist.

code :
table.FindNearest([4])

result a not correct dataset ( like corrupt )
i see  all data, but  only one row of 3 ( range not cancelled ?? )  , or i
see duplicate the record

with refresh work all well ( but not always... not perfect dataset )


FindNearest with exist value, work well.


can i have a fast fix for it ?
i can't wait weeks/much days...  for next beta.


Best Regards.
Mauro Botta.

this code in DbIsam 4 , work all well.

Mauro,

<< result a not correct dataset ( like corrupt )
i see  all data, but  only one row of 3 ( range not cancelled ?? )  , or i
see duplicate the record

with refresh work all well ( but not always... not perfect dataset ) >>

Is this with a local or remote session ?

<< I can't wait weeks/much days...  for next beta. >>

EDB is not in beta, so please stop with the snark.

--
Tim Young
Elevate Software
www.elevatesoft.com

> Is this with a local or remote session ?

Local

> << I can't wait weeks/much days...  for next beta. >>

> EDB is not in beta, so please stop with the snark.

sorry ^^


What is "snark"  ?

Mauro,

<< sorry ^^

What is "snark"  ? >>

Sarcasm.  Some of your messages come across as really sarcastic.

--
Tim Young
Elevate Software
www.elevatesoft.com

Mauro,

I cannot reproduce this here at all using the table/code that you indicated.
Did you try repairing the table ?  It looks to me like your table's
index(es) may be corrupted.

--
Tim Young
Elevate Software
www.elevatesoft.com

> Sarcasm.  Some of your messages come across as really sarcastic.

Sorry, there is not sarcastic.


Only my bad english ^^

> I cannot reproduce this here at all using the table/code that you
> indicated. Did you try repairing the table ?  It looks to me like your
> table's index(es) may be corrupted.

hi

yes , i have already repair it, but notthing.

i see today , the bug is present when there is a filter.

i have this filter :
Filter = 'ANNOORDINE >= 2008 and ANNOORDINE <= 2008'

i have do a example for see you the bug
http://rapidshare.de/files/40801701/bug-findnearest.zip.html

Best Regards.
Mauro Botta.

Mauro


I've just tried your demo and I can confirm that something weird is going on.

Tim

The actual effect seems to vary depending on what filter is used, but just looking at what's appearing on the screen I'd say its the buffer for the grid isn't being filled properly. Using Mauro's filter if I scroll down the grid and back up the 7's are displayed ie not a full table refresh but at least forcing a redisplay of that portion of the table.

Roy Lambert [Team Elevate]

Mauro,

<< i see today , the bug is present when there is a filter.

i have this filter :
Filter = 'ANNOORDINE >= 2008 and ANNOORDINE <= 2008' >>

Okay, I've replicated this and a fix will be in 2.02 B3.

--
Tim Young
Elevate Software
www.elevatesoft.com