On Tue, 2009-08-11 at 10:21 -0700, Richard Davies wrote:
> > I don't agree the current savepoint use within Django is inconsistent. As
> > far as I can tell, savepoints are used internally in the one case where
> > Django itself catches and suppresses an IntegrityError.
> ...
> > Right now it is
> I don't agree the current savepoint use within Django is inconsistent. As
> far as I can tell, savepoints are used internally in the one case where
> Django itself catches and suppresses an IntegrityError.
...
> Right now it is pretty simple: if your app code catches a database error it
> must
On Tue, Aug 11, 2009 at 11:24 AM, Richard Davies <
richard.dav...@elastichosts.com> wrote:
>
> Hi all,
>
> I've got two open tickets against database savepoints (#11156 and
> #9205) and think this is an area which we should take a look at for
> 1.2 - it is currently inconsistent, IMHO.
>
>
I've no
Hi all,
I've got two open tickets against database savepoints (#11156 and
#9205) and think this is an area which we should take a look at for
1.2 - it is currently inconsistent, IMHO.
Savepoints are described here:
http://docs.djangoproject.com/en/dev/topics/db/transactions/#savepoints
There a
