On Thursday 07 May 2009 08:10:00 pm Ed Leafe wrote:
> On May 7, 2009, at 9:57 PM, johnf wrote:
> > Because the following section of code in dBizobj.py takes ~40
> > seconds to
> > complete:
> >
> > for key, cursor in cursors.iteritems():
> > self._CurrentCursor = key
> > changedRows = self.getChangedRows(includeNewUnchanged)
>
> Can you print the number of changedRows here?
>
> > for row in sorted(changedRows, reverse=True):
> > self._moveToRowNum(row)
> > try:
> > func(*args, **kwargs)
> > except StandardError, e:
> > # Reset things and bail
> > dabo.errorLog.write(_("Error in
> > scanChangedRows: %s") % e)
> > self._CurrentCursor =
> > old_currentCursorKey
> > self._positionUsingPK(old_pk)
> > raise
>
> If you want to run this with profiling on, I'd be interested in
> knowing why a simple cancel is taking so long. Does this bizobj have
> lots of child bizobjs?
>
>
> -- Ed Leafe
print changedRows
[0]
[]
The table session has 1586 records, two joins, and two children.
--
John Fabiani
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-dev
Searchable Archives: http://leafe.com/archives/search/dabo-dev
This message:
http://leafe.com/archives/byMID/[email protected]
