On Jan 29, 2010, at 1:33 PM, Paul McNett wrote:
>> new() isn't the opposite of delete(); save() is.
>
> No, cancel() is the opposite of save()
>
> When you save(), you are committing your changes; when you cancel(), you are
> forfeiting your changes. Changes can include updating, inserting, or deleting.
>
> The way I see it, anyway. ;)
I look at it as the difference between local operations and backend
operations. new() is not much different than any other local editing function.
cancel() is also a local editing function.
There are three processes that update the backend: insert, update and
delete. We've combined the first two into save(), which is logically consistent
for a user: it writes their data, whether new or updated, to the database.
Delete doesn't write anything; it removes.
> (when you delete from an rdbms, you still need to commit the transaction
> first)
Which we do. Committing in the rdbms world is conceptually distinct
from the application layer.
-- 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]
