On Feb 19, 2009, at 4:49 PM, Paul McNett wrote:
> But I don't understand how None could have gotten into the list of
> row numbers that
> are changed. scanChangedRows() has this code:
>
> 770 changedRows = self.getChangedRows(includeNewUnchanged)
> 771 for row in sorted(changedRows, reverse=True):
> 772 self._moveToRowNum(row)
>
> ... and it is the line 772 that eventually causes the traceback,
> because one of the
> rows in sorted(changedRows) is None, instead of a valid row number.
>
> I'm unable to reproduce this error.
I've seen that once or twice, due to some bug in the new record
creation that was not creating a PK for newly-added records.
I suppose that we could add a handler for None in this situation,
perhaps writing to the error log and continuing on.
-- Ed Leafe
_______________________________________________
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]