On Apr 16, 2008, at 7:33 PM, Paul McNett 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.
Well, you're both right. Carl is correct at the database level; Paul
is correct at the application level.
Using local data sets, we can buffer inserts and updates. We can't
buffer deletes without some hokey system of tracking deleted PKs that
would be a nightmare to maintain. What is really needed is a way to
mark a form as transactional: entering it begins a transaction, and
leaving either commits or rolls it back. We currently don't expose
begin/commit/rollback in the bizobj to the UI, so that would have to
be added.
-- 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]
