Subject RE: [IBO] Optimize Locate() for an entirely fetched TIB_Query result set
Author Support List
Thomas,

> Hello Jason,
>
> >>>>> Even with the settings above, I still have a large number (pretty
> >>>>> much the number of Locate() calls) of
> >>>>>
> >>>>> SELECT * FROM IBLM$COLUMNLOGDEF
> >>>>> WHERE IBLM$COLUMNLOGDEF.TABLE_NAME=? /* BIND_0 */
> >>>>> AND IBLM$COLUMNLOGDEF.OPERATION=? /* BIND_1 */
> >>>>> AND IBLM$COLUMNLOGDEF.COLUMN_NAME=? /* BIND_2 */
> >>>>>
> >>>>> calls. In the Firebird 2.5 Trace API output.
> >>>>
> >>>> I have a simple sample application with a smallish Firebird 2.5
> >>>> database, which shows this problem. Care to have a look?
> >>>
> >>>
> >>> Sure, I'd be glad to.
> >>
> >> Have you had time to give it a try?
> >
> > I have worked on this some and I am yet baffled about what is going on.
> > I think there is an issue I should resolve in order to increase the
> > efficiency.
> >
> > I'll be getting back into it again soon now that I am home from being
> > out of town for over a week.
>
> Has anything changed in that area in the newest 4.9.14 Build 5 release?

I've been working on this more and all of those calls are efforts to see if
the record is on the server when it cannot find it in the buffer.

I remember that you had a reason why you didn't think IBO should be looking
on the server for a match but I don't clearly recall what it was.

Perhaps you can get on Skype and see if I'm on-line and we can work on this?

Thanks,
Jason LeRoy Wharton
www.ibobjects.com