Paul McNett wrote: > 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.
How about integrating sqlalchemy into Dabo? ;-) From sqlalchemy feature list: The Unit Of Work system, a central part of SQLAlchemy's Object Relational Mapper (ORM), organizes pending create/insert/update/delete operations into queues and flushes them all in one batch. To accomplish this it performs a topological "dependency sort" of all modified items in the queue so as to honor foreign key constraints, and groups redundant statements together where they can sometimes be batched even further. This produces the maxiumum efficiency and transaction safety, and minimizes chances of deadlocks. Modeled after Fowler's "Unit of Work" pattern as well as Hibernate, Java's leading object-relational mapper. Uwe _______________________________________________ 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]
