| Subject | RE: [IBO] IBOTable findkey functionis too slow and reason?? |
|---|---|
| Author | Jason Wharton |
| Post date | 2019-05-16T18:01:36Z |
For this to work quickly, meaning it submits an internal query
fetching records from the descending order first, you need to have an index that
has those same columns but in descending order. IBO should recognize that
index and automatically apply that optimization.
There may be some other things to configure as well. Are
you using TIBOTable? If not, this is actually recommended with IBO so that
you get these automatic features applied.
You can configure this with the TIBOQuery and TIB_Query as well, but it is a little more involved. You need to use the OrderingLinks property.
You can configure this with the TIBOQuery and TIB_Query as well, but it is a little more involved. You need to use the OrderingLinks property.
Let me know how it goes!
Regards,
Jason Wharton
From: IBObjects@yahoogroups.com [mailto:IBObjects@yahoogroups.com]
Sent: Thursday, May 16, 2019 1:27 AM
To: IBObjects@yahoogroups.com
Subject: [IBO] IBOTable findkey functionis too slow and reason??
I have a big table with a complex primary index; thus, the primary index is
combination of 3 fields.
If i try to go to the last record using Findkey it is taking a long
time.
why is that??? if this is a normal case why i need to have an
index??
more general question how does the indices work at IBO table
level?