List Info

Thread: anyone see this problem in psycopg2 i m unable to debug this




anyone see this problem in psycopg2 i m unable to debug this
user name
2006-09-29 21:51:52
psycopg2.ProgrammingError : current transaction is aborted,
commands
ignored until end of transaction block


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the
Google Groups "Django users" group.
To post to this group, send email to django-usersgooglegroups.com
To unsubscribe from this group, send email to
django-users-unsubscribegooglegroups.com
For more options, visit this group at http://gr
oups.google.com/group/django-users
-~----------~----~----~----~------~----~------~--~---

anyone see this problem in psycopg2 i m unable to debug this
user name
2006-09-29 22:17:16
Hi anil, with this message we can't see what error is happen, you need say if you create some manual query, or if you edit something...What steps you follow?

On 9/29/06, anil < anilmrnyahoo.com">anilmrnyahoo.com> wrote:

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







--
SDM Underlinux
Garimpar.com
--
PEP-8
Só existem 3 tipos de pessoas no mundo, as que sabem contar, e as que não sabem.
CPFL - Compania Piratininga de FALTA de Luz (6 vezes em 5 dias!!)
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Django users"; group.
To post to this group, send email to django-usersgooglegroups.com
To unsubscribe from this group, send email to django-users-unsubscribegooglegroups.com
For more options, visit this group at http://groups.google.com/group/django-users
-~----------~----~----~----~------~----~------~--~---

anyone see this problem in psycopg2 i m unable to debug this
user name
2006-09-29 22:35:02
anil wrote:
> psycopg2.ProgrammingError : current transaction is
aborted, commands
> ignored until end of transaction block

Anil,

I get these errors when a call to psycopg fails and the
transaction in 
which it failed is not rolled back.  All further database
actions will 
fail until you roll back the transaction.

Wrap your psycopg call in a try/except block and rollback
the 
transaction if the call fails.

You'll find discussion about this in the list archives, I
think.

Best,

Eric.

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the
Google Groups "Django users" group.
To post to this group, send email to django-usersgooglegroups.com
To unsubscribe from this group, send email to
django-users-unsubscribegooglegroups.com
For more options, visit this group at http://gr
oups.google.com/group/django-users
-~----------~----~----~----~------~----~------~--~---

anyone see this problem in psycopg2 i m unable to debug this
user name
2006-09-30 02:31:04
this sounds serious how do we implement rollbacks
i use postgres 8.1
thanks
Anil
Eric Walstad wrote:
> anil wrote:
> > psycopg2.ProgrammingError : current transaction is
aborted, commands
> > ignored until end of transaction block
>
> Anil,
>
> I get these errors when a call to psycopg fails and the
transaction in
> which it failed is not rolled back.  All further
database actions will
> fail until you roll back the transaction.
>
> Wrap your psycopg call in a try/except block and
rollback the
> transaction if the call fails.
>
> You'll find discussion about this in the list archives,
I think.
> 
> Best,
> 
> Eric.


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the
Google Groups "Django users" group.
To post to this group, send email to django-usersgooglegroups.com
To unsubscribe from this group, send email to
django-users-unsubscribegooglegroups.com
For more options, visit this group at http://gr
oups.google.com/group/django-users
-~----------~----~----~----~------~----~------~--~---

anyone see this problem in psycopg2 i m unable to debug this
user name
2006-09-30 02:59:41
On 9/29/06, a <atempinbox.com> wrote:
> this sounds serious how do we implement rollbacks

from django.db import connection
connection._rollback()

This behavior, by the way, is a *good* thing; rather than
try to sort
things out and go on, PostgreSQL is saying, "An error
happened, and
I'm going to refuse to do anything else until you fix
it". This
provides extremely strong protection of your data.

-- 
"May the forces of evil become confused on the way to
your house."
  -- George Carlin

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the
Google Groups "Django users" group.
To post to this group, send email to django-usersgooglegroups.com
To unsubscribe from this group, send email to
django-users-unsubscribegooglegroups.com
For more options, visit this group at http://gr
oups.google.com/group/django-users
-~----------~----~----~----~------~----~------~--~---

anyone see this problem in psycopg2 i m unable to debug this
user name
2006-09-30 16:51:12
On Friday 29 September 2006 07:31 pm, a wrote:
> this sounds serious how do we implement rollbacks
> i use postgres 8.1
> thanks
> Anil

<http://www.google.com
/search?hl=en&lr=&q=psycopg+django+%22transaction+bl
ock%22>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the
Google Groups "Django users" group.
To post to this group, send email to django-usersgooglegroups.com
To unsubscribe from this group, send email to
django-users-unsubscribegooglegroups.com
For more options, visit this group at http://gr
oups.google.com/group/django-users
-~----------~----~----~----~------~----~------~--~---

[1-6]

about | contact  Other archives ( Real Estate discussion Medical topics )