Hi, I would like to ask a question concerning recursive transactions.
By recursive transaction I mean :
@django.db.transaction.commit_on_success
def a() :
# do some stuff
@django.db.transaction.commit_on_success
def b() :
# do some stuff
a()
# do some stuff
a()
# do some stuff
I would like when calling b(), the real commit will only be done when b
returns (and not each time a() returns + when b() returns
I'm testing on a sqlite backend and there is a real commit after each call to
a() : after raising an exception in the middle of b(), the stuff done by
previous calls to a() is in the database.
So, is it only the sqlite backend wich doesn't support recursive transactions,
or is django missing that point ?
If it's only a sqlite problem, is there a workaround?
Thanks.
Panard
--
HomePage: http://dev.inzenet.org/~panard/
Yzis : http://www.yzis.org
Qomics : http://dev.inzenet.org/~panard/qomics
Smileys : http://smileys.inzenet.org
--
HomePage: http://dev.inzenet.org/~panard/
Yzis : http://www.yzis.org
Qomics : http://dev.inzenet.org/~panard/qomics
Smileys : http://smileys.inzenet.org
pgpu8yB3yHaqe.pgp
Description: PGP signature
