Hi there,
I am implementing a tool to handle userdata that is stored in a MySQL db.
The underlaying logic of the stored procedures used to maintain the db
content
dictate that I have to control the transactions myself.
I understand that there is a way to handle transaction controll in the
ZMySQL
robert rottermann schrieb:
Hi there,
I am implementing a tool to handle userdata that is stored in a MySQL db.
The underlaying logic of the stored procedures used to maintain the db
content
dictate that I have to control the transactions myself.
Can you elaborate on that? I dont see a reason
Are you sure it doesn't do it out of the box?
I know it does for ZPsycopgDA which is the Postgresq Zope database adapter.
With that one I don't have to come near handling the SQL transactions.
What Zope commits and rollsback is done for SQL too automatically.
robert rottermann wrote:
Hi
robert rottermann wrote at 2007-1-10 09:00 +0100:
...
I am implementing a tool to handle userdata that is stored in a MySQL db.
The underlaying logic of the stored procedures used to maintain the db
content
dictate that I have to control the transactions myself.
If you know what you do, then you
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi there,
I am implementing a tool to handle userdata that is stored in a MySQL
db. The underlaying logic of the stored procedures used to maintain the
db content dictate that I have to control the transactions myself.
I understand that there is a
Am 10.01.2007, 13:00 Uhr, schrieb robert rottermann [EMAIL PROTECTED]:
I understand that there is a way to handle transaction control in the
ZMySQL methods. However I find no documentation at all on how to use it.
This is incorrect. ZSQL methods are called within Zope transactions so you
thanks charlie,
so that means, that the _commit and _abort methods are only for zope's
transaction controll.
Yes, and with good reason.
But I think that if you know what your'e doing you may
use them althought it may be tricky. It is better to
try external method like Charlie suggested for
