Ian, thanks for the feedback, but what your concern is not related to
this proposal.
What you're talking about is issuing a BEGIN while already in a database
transaction, which is normally an error, with no standard meaning or
definition in SQL's transaction model. It's completely up to the
datab
2010/5/18 Ian Lewis :
> Am I missing something? Are we talking about doing some kind of
> transaction management at the application level?
Yes: we're talking about Django's transaction management layer (that is, the
code in django.db.transaction), which controls how Python-level transaction
blocks
2010/5/17 Ian Lewis :
>
> I suppose that it's worth mentioning that any support for nested
> transactions will not be portable to different databases (particularly
> MySQL) and probably would need to be documented accordingly.
How do you mean?
Django-level transaction block nesting is portable to
Hi Russel, thanks for the response!
On May 15, 12:47 pm, Russell Keith-Magee
wrote:
>
> By way of a brief explanation of why things are they way they are:
>
> Firstly, Django's history in journalism-based websites breeds a
> history of high-volume reads, and low-volume, relatively simple
> writes
Hi,
I'm working with a company that uses and maintains a commercial Django-based
commercial system, which requires reliable transactional integrity across
groups of database operations in a number of places (financial transfers,
and so on).
I've been investigating how Django's transaction managem
