Re: Django 1.8 Transaction Begin

[Russell Keith-Magee]

Hi Katarzyna,

I'm not sure what gave you the impression that Django doesn't support transactions - there's a whole section in the documentation about this very topic:

https://docs.djangoproject.com/en/1.8/topics/db/transactions/

You don't explicitly execute a "BEGIN" statement, but you can definitely put code into a transaction.

Yours,

Russ Magee %-)

On Wed, Jun 17, 2015 at 5:41 PM, Katarzyna Łabędź <katarzy...@gmail.com> wrote:

Hi!

As far as i know Django 1.8 does not support BEGIN transaction for mysql. Is there a way to invoke this?
How to invoke BEGIN Transaction in a raw sql? I cannot find it in documentation...

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users...@googlegroups.com.
To post to this group, send email to django...@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/0f0adf0f-bfca-4aae-9bc5-64cb5ee1ee18%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[James Bennett]

As the documentation states, the default behavior in Django is "autocommit", relying on the database's autocommit behavior. This means Django does not need to issue explicit BEGIN and COMMIT statements, so by default Django does not issue them unless the ORM determines that a requested operation requires multiple queries (in which case Django does use an explicit transaction for those queries).

Django provides a number of options for other transaction behaviors, including running each HTTP request/response cycle inside a transaction, or manually beginning and committing transactions from your own code. Consult the transaction documentation for details.

[Carl Meyer]

Hi Kate,

On 06/18/2015 04:05 AM, Katarzyna Łabędź wrote:
> Maybe i didn't understand it correctly.
>
> I know Django support transactions, but isn't it do it on commit?
> I just tried to find the BEGIN statement inside them and i could not
> find it - searched through internet and what I found was a bunch of
> people asking the same question - where is the begin in the
> transactions? So i just figured i ask here.
> Why Django don't execute Begin statement ? Isn't it necessary to have a
> fully correct transaction?

You are right to be confused, because this is confusing territory.

The default behavior of all Python database adapters is "implicit
transactions", meaning the underlying database adapter library itself
(Python-MySQL, psycopg2, etc) sends a BEGIN automatically as soon as you
send your first query. (At least if the library is compliant with PEP
249 [1], the Python database adapter standard, which all adapters used
by built-in Django backends are.)

Django overrides this and places the underlying connection into
autocommit mode (no transactions) by default. But when you request a
transaction (by using an 'atomic' block), Django doesn't need to
explicitly send BEGIN, it just puts the connection back into the default
PEP 249 "implicit transactions" mode, which means the database adapter
will send BEGIN automatically as soon as you send a query. So Django
never sends a BEGIN itself, just COMMIT or ROLLBACK.

In practice, though, you can ignore this implementation detail, and just
assume that a BEGIN is sent at the start of any (outer) 'atomic' block
(and COMMIT or ROLLBACK) is sent at the end, and you'll be correct.

I wrote a blog post [2] which discusses this in more detail. It's about
PostgreSQL instead of MySQL, but the part near the beginning about PEP
249 and Django applies equally well to MySQL (I think; I'm not very
familiar with transactions on MySQL).

Carl

[1] https://www.python.org/dev/peps/pep-0249/
[2] http://oddbird.net/2014/06/14/sqlalchemy-postgres-autocommit/

[Erik Cederstrand]

> Den 18/06/2015 kl. 17.49 skrev Carl Meyer <ca...@oddbird.net>:
>
> I wrote a blog post [2] which discusses this in more detail. It's about
> PostgreSQL instead of MySQL, but the part near the beginning about PEP
> 249 and Django applies equally well to MySQL (I think; I'm not very
> familiar with transactions on MySQL).

Just remember that the only MySQL storage engine that actually supports transactions is InnoDB: https://dev.mysql.com/doc/refman/5.5/en/storage-engines.html

Erik