Alternative to TOraTable.Locate?

[kurtbilde]

Hi,

TOraTable.Locate seems to be very "expensive" to use - even when .Locating on the primary key. Is there an alternative, that is less time consuming (in wait time), but still let's me use TOraTable as Dataprovidor for the DB-aware components?

-Kurt

[AlexP]

Hello,

Independently on the method of positioning in the DataSet you will use (Locate, LocateEx, FindFirst, FindKey, etc.), data must be loaded to the client for positioning, and if the data volume is large enough, all these methods will cause delay. To increase performance, you can explicitly set the sorting order (ORDER BY) by a needed field or set the FetchAll property to True, that will allow retrieving all records on opening DataSet and to be positioned locally

[kurtbilde]

Hi Alex,

The ORDER BY option doesn't speed up the process and when using FetchAll = true the penalty is paid when using the tOraTable.open (long wait time). Couldn't the unique rowid be used for a special tOraTable.FetchRow(RowId)?!?

-Kurt

[AlexP]

Hello,

There is no such functionality at the moment. We plan to implement the possibility to search for a record by a key field without fetching the whole table. We cannot tell the exact terms of this feature implementation yet.

[kurtbilde]

Hopefully very, very soon - this is a major (performance) killer :-O

-Kurt