On 9/18/07, paulh <[EMAIL PROTECTED]> wrote: > > ProgrammingError at /newso/6562/80/sisale/picked/ > ERROR: current transaction is aborted, commands ignored until end of > transaction block SET client_encoding to 'UNICODE' > > The last statement executed was an explicit call to ...save().
This is a somewhat misleading error message. Essentially, the Postgres backend is telling you that it couldn't run the 'SET client_encoding to UNICODE' SQL statement because the previous SQL statement caused an error. This generally means that the command prior to the command that raised the visible error is the _actual_ cause of the problem - usually because of some form of data integrity problem. Yours, Russ Magee %-) --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
