Carl Karsten wrote: > Paul McNett wrote: >> Carl Karsten wrote: >>> To me, .save and .delete operate at the same level: you can either save, or >>> you >>> can delete. once you have done either, you are done. so perfectly >>> consistent. >> To me, .save() and .cancel() operate at the same level: you can either >> save, or you can cancel. .new(), .delete(), and .setFieldVal() operate >> at the same level (just like in SQL insert, delete, and update. So not >> perfectly consistent. > > im confused. > > 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. >> Read those threads I posted: you changed your tune! :) > > I claim being still in the VFP haze. glad I was unsure about it, this could > have been extra embarrassing. I think I'm sufficiently out of the VFP haze myself. And we aren't talking about the VFP-style deleted flag here, not really. Once committed, the records will be deleted. But while in the local dataset, deleted records won't be a special case. Special cases violate the zen of python. ;) 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]
