Log Message:
-----------
I've attached a patch that uses the SQLSTATE from the backend any time
the error condition after executing a query is
STMT_ERROR_TAKEN_FROM_BACKEND. Besides solving the problem I reported,
this seems to make much more sense than setting the SQLSTATE arbitrarily
to HY000 "General Error" in this situation. I look forward to your
feedback.
[Chris Ingram]
Modified Files:
--------------
psqlodbc:
connection.c (r1.117 -> r1.118)
(http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/psqlodbc/psqlodbc/connection.c.diff?r1=1.117&r2=1.118)
connection.h (r1.66 -> r1.67)
(http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/psqlodbc/psqlodbc/connection.h.diff?r1=1.66&r2=1.67)
environ.c (r1.53 -> r1.54)
(http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/psqlodbc/psqlodbc/environ.c.diff?r1=1.53&r2=1.54)
psqlodbc.h (r1.91 -> r1.92)
(http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/psqlodbc/psqlodbc/psqlodbc.h.diff?r1=1.91&r2=1.92)
statement.c (r1.100 -> r1.101)
(http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/psqlodbc/psqlodbc/statement.c.diff?r1=1.100&r2=1.101)
statement.h (r1.61 -> r1.62)
(http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/psqlodbc/psqlodbc/statement.h.diff?r1=1.61&r2=1.62)
---------------------------(end of broadcast)---------------------------
TIP 2: Don't 'kill -9' the postmaster
