[Replying to the original thread; there was discussion of this commit back in May and further commits made based on the discussion; I'm reporting a new issue that I've regression-tested to this commit, and the follow-up commits didn't change the behavior.]
On 5/25/11 2:57 AM, Jacek Kałucki wrote: > dabo Commit > Revision 6595 > Date: 2011-05-25 02:57:43 -0700 (Wed, 25 May 2011) > Author: Jacekk > Trac: http://trac.dabodev.com/changeset/6595 > > Changed: > U trunk/dabo/biz/dBizobj.py > > Log: > This fairly huge commit is the first attempt to fix Dabo issue > with detecting modified children bizobjs. > It should fix #1390 ticket. > Quick list of changes: > - the saveAll no longer uses scanChangedRows > - the validate method isn't called if only the child bizobj is changed > - data changes detection is moved from the validate to the save method > - the scan method now return value from the last called function (useful for > detecting changed rows) > - redundant exception logging in nested scans are avoided. > Although I'm testing this code since last december, there still can be > unexpected issues. > Please, report them immediately. With r6595, the time it takes to close my application goes from instantaneous to 3-5 seconds. There's probably unneeded scanning for changes in the biz.cancelAll() cycle? I'll try to dig into this in a bit, but wanted to document the problem first. Paul _______________________________________________ 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]
