Subject | RE: [IBO] Optimize Locate() for an entirely fetched TIB_Query result set |
---|---|
Author | Support List |
Post date | 2011-06-14T20:52:17Z |
Thomas,
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.
Regards,
Jason Wharton
www.ibobjects.com
> >>> Even with the settings above, I still have a large number (pretty muchI have worked on this some and I am yet baffled about what is going on. I
> >>> 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?
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.
Regards,
Jason Wharton
www.ibobjects.com