I am running a site using Django 1.2.5 and postgres. I just upgraded Django and Django CMS to their latest versions using South. And now I get a MOD_PYTHON error. Here is an excerpt:
MOD_PYTHON ERROR (...) File "/home/wsc2/lib/Django-1.2.5/django/db/backends/__init__.py", line 56, in _savepoint self.cursor().execute(self.ops.savepoint_create_sql(sid)) File "/home/wsc2/lib/Django-1.2.5/django/db/backends/util.py", line 15, in execute return self.cursor.execute(sql, params) File "/home/wsc2/lib/Django-1.2.5/django/db/backends/postgresql_psycopg2/base.py", line 44, in execute return self.cursor.execute(query, args) DatabaseError: current transaction is aborted, commands ignored until end of transaction block >From what I have read about this on the internet, it is caused by one query failing, and then trying to make another query without doing a rollback of the transaction. 1) Even if my database schema is inconsistent with the model, shouldn't Django handle this situation better? I.e. actually informing me of the error in the first query, and not attempting to execute any more queries? 2) I don't know much about the flow behind the Django scenes. But I need to find out which query is initially failing, to see what the db problem is. How can I find the query initially failing? Please tell me if I misunderstood something, or if I am off track. Thomas -- 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 django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.