From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Oliver Jowett <oliver(at)opencloud(dot)com> |
Cc: | Michael Bell <mikebell90(at)yahoo(dot)com>, pgsql-jdbc(at)postgresql(dot)org |
Subject: | Re: Hibernate and Postgres 8.3/8.4 |
Date: | 2009-08-22 13:48:27 |
Message-ID: | 8388.1250948907@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
Oliver Jowett <oliver(at)opencloud(dot)com> writes:
> Michael Bell wrote:
>> Caused by: org.postgresql.util.PSQLException: ERROR: operator does not exist: smallint = character varying
>> Hint: No operator matches the given name and argument type(s). You might need to add explicit type casts.
>> Position: 628
>> The queries in question are all "correct" in that they use query.setXXX, where XXX is a "reasonable" thing like String, Integer, Long.....nothing fancy...
> Well, from the exception, either Hibernate is doing setString() on a
> parameter that is compared to a smallint, or it's doing setShort() on a
> parameter that is compared to a varchar type.. so one of the two sides
> is wrong.
Yeah. This looks to me like Hibernate contains instances of the exact
sort of bug --- not trivial issue, real bug --- that we removed the
implicit casts to help people catch. You should definitely file a bug
report with them.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | J. W. Ulbts | 2009-08-23 16:31:12 | Re: Display SQL from Java Prepared Statement |
Previous Message | Campbell, Lance | 2009-08-22 12:53:53 | Display SQL from Java Prepared Statement |