How the transactions are done in the saveChanges?

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi all.

I'm experimenting with ModelingFramework, and I've some questions.

I've tried the sample model in from the website, and I've analyzed the
database logs. I've noticed that the ec.saveChanges() in the model is
composed of 5 transactions: the first 4 transactions get the key numbers
from the sequence, the last one is the transaction actually doing the work.

Is this a correct behaviour? What are the reasons behind it?

Also, I've noticed that the ec.fetch() is a transaction which terminates
with an abort. Is this correct?

I've not yet experimented with Zope. I see I can connect the
ec.saveChanges() to the transactions machinery in Zope. Some questions:

1) how many db transaction are done for each saveChanges (i.e. same as
above?)

2) how are the db transaction executed/completed inside a Zope
transaction? In a non-zope application, I can see each fetch() produces
a transaction, as well as the ec.saveChanges(). Is this true also in
Zope applications?

Thanks for the support.

Regards
Marco
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFBGRKfXhfyAQQVoaIRApwhAJ4gN0VvFmGwjVMGbcWPNJX8//7UuwCfWz23
ms4DuwY4buaqGurMlFB2yYg=
=fnEH
-----END PGP SIGNATURE-----


-------------------------------------------------------
SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media
100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33
Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift.
http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285