It seems that we have to mention both the calls (commit & rollback) for
every @transaction.commit_manually decorator. One single function call won't
be sufficient to perform the operation.
On Tue, Aug 18, 2009 at 11:08 PM, Lokesh wrote:
>
> Hi,
>
> Verified the flow of statements for the posted
Hi,
Verified the flow of statements for the posted code. Still the problem
exists.
Code works fine when I handled the transactions in general functions
but not with the views.
Could someone please clarify me on these
1. Can I use the transaction decorators(@transaction.commit_manually)
for the
On Tue, Aug 18, 2009 at 16:19, Lokesh wrote:
>
> Hi,
>
> Unable to perform rollback the transactions. Ended up with the
> following error
> "Transaction managed block ended with pending COMMIT/ROLLBACK"
>
> Can I rollback the db changes even if the code doesn't raise any
> excceptions?
>
> Here i
On Sat, 2008-11-29 at 21:22 -0800, I.A wrote:
> Hi Zeroth,
>
> I'm sorry for missing that information.
> Yes, I'm using MySQL 5.0.x and your question made me check. Turns out
> that mysql was creating MyISAM tables for me when I do syncdb with my
> models. I've added the following line to my set
Hi Zeroth,
I'm sorry for missing that information.
Yes, I'm using MySQL 5.0.x and your question made me check. Turns out
that mysql was creating MyISAM tables for me when I do syncdb with my
models. I've added the following line to my settings.py
DATABASE_OPTIONS = {"init_command": "SET storage_
Are you using a mysql database? That may be the source of the trouble.
IIRC, some versions of MySQL, depending on the inner database, don't
support transactions.
-Zeroth
On Nov 29, 6:56 pm, "I.A" <[EMAIL PROTECTED]> wrote:
> hi guys,
>
> i'm wondering how transaction really works with django mod
6 matches
Mail list logo
