Ed Leafe wrote: > On Apr 16, 2008, at 11:13 PM, Paul McNett wrote: > >>> doesn't .save() cause the SQL INSERT or UPDATE commands? >> Yes. So to me it seems that .save() should cause the SQL INSERT, >> UPDATE, >> and/or DELETE commands. > > > I have made changes that expose beginTransaction(), > commitTransaction() and rollbackTransaction() in the bizobj so that > they respect the transaction token system. IOW, you can add code to > your form to trigger these things in the bizobj. I need a little bit > of time to clean up some other stuff I was working on from the bizobj > code, and will then post the changes for you to test.
Awesome. I'm kind of stuck because I need the behavior for the delivery that needs to happen within a week, but I was unclear on how to get it cleanly given the current design. I was about to hack some sort of flag system into my bizobj subclasses as a temporary stopgap but now I'll hold off on that. Since nobody is using my app (yet) in a multiuser context (database is a sqlite db stored locally) I don't have a problem holding the transaction open forever. Thanks! 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]
