Changes between Version 20 and Version 21 of BetterErrorMessages

Timestamp:

Feb 28, 2008, 5:12:39 PM (17 years ago)

Author:

Kenneth Arnold

Comment:

Describe a confusing PostgreSQL error that I hit reasonably often

BetterErrorMessages

@@ -65 +65 @@
 }}}
 
+This pyscopg2 (PostgreSQL) error usually signifies that some ''previous'' database query was incorrect (e.g., you tried to {{{order_by()}}} a field that doesn't exist, or put a string in an integer column, etc.). That previous error aborted the transaction, causing all subsequent database access to fail with this message.
+
+If you get this while at a shell, you can fix your database connection by executing a rollback:
+{{{
+from django.db import connection
+connection.cursor().execute('rollback')
+}}}
+
+If you get this from a view, it probably means the immediately previous query had a problem (but was caught by an over-eager exception handler).
+
 In certain situations with PostgreSQL, a bogus error message about SET TIME ZONE may be returned. See #3179 (which is closed, but has a description of the problem).  The real error message can probably be found in the postgres log file.