On Saturday 15 September 2007 06:36, Ed Leafe wrote: > On Sep 15, 2007, at 9:02 AM, johnf wrote: > > I believe I have traced this to the requery() of a bizobj. This > > makes sense > > and matches my first impression of the cause being the select > > statement. > > This is because what we do is: > > change the bizobj.UserSQL or the WhereClause() > > THEN > > bizobj.requery() - to retrieve the new data. > > > > So the question I have is - can I avoid the getfields() by using > > bizobj.execute()? Is this the correct way to avoid it? Or > > shouldn't the > > requery() be smart enough to determine that is no need to getfields()? > > First, I don't know why you want to "avoid" calling getFields(). > Have you done performance testing and determined that this is the > bottleneck process? Do you know that it even has a measurable impact > on execution time? > > Second, the results of the call to getFields() should be cached in > local cursor attributes; if it isn't, then there is some framework > code that should be updated. That's why I wanted you to run the loggit > () tracing so that I could see if there were any calls that should > not have been made. > > -- Ed Leafe
Larry has created a form that is very slow on my Linux box. We have been trying to fix the performance. During our testing I noticed that approximately 40 calls were made to getfields(). Even with the server cache - 40 calls take time. I was able to see the 40 calls by reviewing the Postgres server logs. Which means that the call was made to the Postgres server and not cached by Dabo - Right? The log is a little to long to include in the text. I'll send it to you. -- John Fabiani _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-users Searchable Archives: http://leafe.com/archives/search/dabo-users This message: http://leafe.com/archives/byMID/dabo-users/[EMAIL PROTECTED]
