| Subject | RE: [IBO] Updating with TIBOTable only modified fields with old value <> new value |
|---|---|
| Author | IBO Support List |
| Post date | 2015-05-17T15:17:33Z |
TIBOTable has the ability to do this for you automatically. As
long as it is configured correctly, IBO will do the work of keeping the fetching
of records to a minimum. You can do a Locate() into the middle of the dataset
somewhere and IBO will find the record on the server and then bring that record
to the dataset by having two internal cursors that fetch the ascending and
descending records from that point. Thus, you can still navigate the entire
table from that point. If you call First it will fetch from the ascending cursor
and if you call Last it will fetch from the descending cursor,
etc.
Hope this helps,
Jason Wharton
From: IBObjects@yahoogroups.com [mailto:IBObjects@yahoogroups.com]
Sent: Sunday, May 17, 2015 2:02 AM
To: IBObjects@yahoogroups.com
Subject: RE: [IBO] Updating with TIBOTable only modified fields with old value <> new value
I use filters on lookup TIBOTable and generally the result in less than one hundred rows.
For these tables I use locate to spécifically find a record
For the other TIBOTable (on which I insert or update) I use a gotokey to find the record
Would it be better (in terms of performance) to use IndexFieldName to sort on the fields involved in and use a SQLWhere string to limit the result ? (either to the range or to the record)
With large tables, every things limiting the network bandwidth will be useful
Thanks