heh well thats the TG thing.I've never used it before or studied it, but I
the impression I usually get when others talk about it is that their model of
"autocommit" is a bit off.
On May 27, 2010, at 6:50 PM, Kent Bower wrote:
> Thank you, as always.
>
> I failed to recognize I'm using th
Thank you, as always.
I failed to recognize I'm using the TurboGears foundation, which uses
zope & transaction:
Is there a way to still accomplish this?
>>> DBSession.begin_nested()
>>>
>>> DBSession.commit()
Traceback (most recent call last):
File "", line 1, in
File
"/home/rarch/tg2e
On May 27, 2010, at 5:12 PM, Kent wrote:
> The docs state "For each begin_nested() call, a corresponding
> rollback() or commit() must be issued."
>
> In PostgreSql, according to my understanding, if there is ever a
> database exception, a rollback must be issued.
> This means a main reason to i
The docs state "For each begin_nested() call, a corresponding
rollback() or commit() must be issued."
In PostgreSql, according to my understanding, if there is ever a
database exception, a rollback must be issued.
This means a main reason to issue a SAVEPOINT is as a hedge against an
error.
As da
