Użytkownik Paul McNett napisał: > Failure to reset self.exitScan to False results in all future scans exiting > immediately, so for instance calling getChangedRows() on a biz with 3 > records and children would return all rows as having changes after the first > row with changes was found. I'll hand it to you that it made it fast!:)
Sorry, but I can't observe such behaviour in my code, I mean that the getChangedRows() always returns correct list of changed rows. Don't know how it can work in differ way for you. If you wish, I can send you coverage log for simple code. BTW, what is your testing environment, platform, interpreter, etc.? My code works on Windows XP/Vista/7 and Ubuntu 11.04. Remember that, (from docstring) "The changes may therefore not be in the record itself, but in a dependent child record." It looks like you need method to check if only current biz context in chain is changed, however I can't see application for it. And this is the point, how isAnyCHanged() is suitable for, return true if *any* row is changed, so if current one is, we don't need to check others. -- Regards Jacek Kałucki _______________________________________________ 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]
