Thanks for the speedy reply and your diagnosis was absolutely spot on. Purely as an aside and because there may be others in my situation, the cause of the error was a confusion between thinking in django terms (where a foreign key is actually a python object) and in sql terms where a foreign key is a number (often). Often, because old habits die hard, when django wants a python object I go to great and pointless lengths to get hold of the corresponding number and then get an error.
On Sep 18, 2:27 pm, "Russell Keith-Magee" <[EMAIL PROTECTED]> wrote: > 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 -~----------~----~----~----~------~----~------~--~---
