On 4/15/07, Grupo Django <[EMAIL PROTECTED]> wrote: > > Hello! > I was building a gallery image, and everithing went fine with mysql, > but lately, I changed my mind and I changed the database to postgres, > it's the django recommendation. > Well, sudenly I got this message: > ProgrammingError?: ERROR: current transaction is aborted, commands > ignored until end of transaction block
This error means that the previous command that was executed caused an error with the database, so Postgres is preventing you from doing anything else until the transaction is reverted. If you are moving from a MySQL to Postgres backend, and MySQL wasn't reporting the problem, I'd guess the most likely cause is a referential integrity problem. The data you are inserting contains foreign keys - Postgres is much more rigorous on checking foreign key validity than the default MySQL setup. If you are inserting data into the tables that contains an invalid value for a primary key, Postgres will complain; if you try to execute another command, Postgres will raise the error you are seeing. 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 [EMAIL PROTECTED] 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 -~----------~----~----~----~------~----~------~--~---
