using the interpreter to learn Django (-r6474 from Subversion)
with postgresql_psycopg2 (pg82). I've found this thread in the
django-users archive:
recovering from interpreter db errors (jan-06)
http://tinyurl.com/2bazqe
But the information seems out-of-date with regards to the current
branc
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.
excellent - exactly what I was looking for. Thanks heaps, Andreas.
Luke Skibinski Holt
On 1/23/06, Luke Skibinski Holt <[EMAIL PROTECTED]> 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
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 h
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 an
6 matches
Mail list logo
