recovering from interpreter db errors

[Luke Skibinski Holt]

Is there a way within the interpreter of recovering from these sorts of
errors:

psycopg.ProgrammingError: ERROR: current transaction is aborted,
commands ignored until end of transaction block

I get them when debugging queries and something goes awry wherein I
have to restart the interpreter and import everything again. Any help?
I have no experience with psycopg ...

Luke Skibinski Holt

[Kenneth Gonsalves]

On Monday 23 Jan 2006 5:50 pm, Luke Skibinski Holt wrote:
> psycopg.ProgrammingError: ERROR:  current transaction is aborted,
> commands ignored until end of transaction block

programming error means something wrong in the sql query

--
regards
kg

http://www.livejournal.com/users/lawgon
tally ho! http://avsap.org.in
ಇಂಡ್ಲಿನಕ್ಸ வாழ்க!

[Andreas Stuhlmüller]

On 1/23/06, Luke Skibinski Holt <AliceViaW...@gmail.com> wrote:
>
> Is there a way within the interpreter of recovering from these sorts of
> errors:
>
> psycopg.ProgrammingError: ERROR: current transaction is aborted,
> commands ignored until end of transaction block

Execute these commands after the error occured:

>>> from django.core import db
>>> db.db.rollback()

Andreas

[Luke Skibinski Holt]

excellent - exactly what I was looking for. Thanks heaps, Andreas.

Luke Skibinski Holt

[exoweb adrian]

I do this at this start of every django interpreter session:

>>> from django.core.db import db
>>> db.cursor().close()
>>> db.connection.autocommit()

Then you don't need to do a rollback and lose your cursor every time
you get a database error.