Glenn Holmer wrote:
> We can't upgrade the driver because we get this:
>
> 2005-03-17 10:10:22,961 WARN
> net.sf.hibernate.util.JDBCExceptionReporter - Meth
> od: logExceptions - Line: 38 Message: SQL Error: 0, SQLState: 42883
> 2005-03-17 10:10:22,962 ERROR
> net.sf.hibernate.util.JDBCExceptionReporter - Meth
> od: logExceptions - Line: 46 Message: ERROR: operator does not exist:
> smallint = boolean
Without more details I'd have to say this is a hibernate or schema
mapping bug -- it looks like it is using setBoolean() where you should
be using setShort() (or vice versa). This only shows up in newer drivers
because they more tightly bind types to parameters (due to using the V3
extended query protocol to pass parameters to the server)
This behaviour is unlikely to change, so you might want to look at
tracking down the cause. As a last resort, you might be able to create
implicit casts between smallint<->boolean.
> Here is more of the log with pg74.213.jdbc3.jar:
>
> 2005-03-16 14:30:43,239 WARN
> net.sf.hibernate.util.JDBCExceptionReporter - Meth
> od: logExceptions - Line: 38 Message: SQL Error: 0, SQLState: 08S01
> 2005-03-16 14:30:44,273 ERROR
> net.sf.hibernate.util.JDBCExceptionReporter - Meth
> od: logExceptions - Line: 46 Message: The backend has broken the
> connection. Possibly the action you have att
> empted has caused it to close.
What is in the server logs around this point? This might be a backend
crash, or might just be the protocol stream getting out of sync again.
> The other possible culprit is that one of our developers just started
> using the Windows version of pgAdmin III, is that known to cause any
> problems?
Not that I know of.
To diagnose this further against the old driver I am going to need
either a testcase, the query code, or a tcpdump of the offending connection.
-O
