Subject | Re: [IBO] IBOTable Last |
---|---|
Author | Jason Wharton |
Post date | 2001-10-29T17:56:26Z |
IBO makes it so that if they call Last and then Prior (which it assumes the
prior records will be needed) that this will be done efficiently.
I think if someone only wanted the last record they would simply provide
that query as the original one in the TIBOQuery component.
Hope this makes sense.
Jason Wharton
CPS - Mesa AZ
http://www.ibobjects.com
prior records will be needed) that this will be done efficiently.
I think if someone only wanted the last record they would simply provide
that query as the original one in the TIBOQuery component.
Hope this makes sense.
Jason Wharton
CPS - Mesa AZ
http://www.ibobjects.com
----- Original Message -----
From: "Sandeep" <sandeep@...>
To: <IBObjects@yahoogroups.com>
Sent: Sunday, October 28, 2001 1:59 PM
Subject: [IBO] IBOTable Last
> When procedure Last is called the IBOTable seems to be reading
> all the records on the server, but when I create an Descending
> index it works fine.
>
> The only advantage I found of Descending index is when doing last.
> There seems to be no speed improvement when scrolling up/down
> the table. What I think could be done (IMHO) is to make a sql
> statement like this
>
> select * from tableA
> where fieldA = (select max (fieldA) from tableA)
>
> when procedure Last is called. I don't know how difficult it will be
> because I don't know how the sql statements are made.
>
> Regards
>
> Sandeep
>
> Software Developer
> CFL
> sandeep@...
> http://www.cfl.co.nz