On Friday 14 September 2007 14:48, johnf wrote:
> On Friday 14 September 2007 11:14, Ed Leafe wrote:
> >     The only place where I can see it being called without caching is
> > when the cursor is trying to determine field types. Do this: modify
> > your dCursorMixin.py file to include this line at the top:
> >
> > from dabo.dBug import loggit
> >
> > ...and then around line 1666, add the decorator to the method:
> >
> >     @loggit
> >     def getFields(self, tableName=None):
> >             """ Get field information about the backend table.
> >
> >     Run the app as you normally would, and after exiting there should be
> > a file named 'functionCall.log'. If it isn't too big, paste the
> > contents into your reply; otherwise, email it to me off-list.
> >
> > -- Ed Leafe
> > -- http://leafe.com
> > -- http://dabodev.com
>
> thanks Ed.  This is a handy tool.  I have not determined what's going on at
> this point we Larry's form but it gives me info to investigate.

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()?



 
-- 
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]

Reply via email to