Well I wondered that originally. That's why I did the test with the
groovy script. The page I use to run that is part of the same
application and I am using the same dataSource which I pass to
hibernate so I don't see how it can be a different driver.
In any case, I've looked into the metadata and found that I am using
an older version of the driver. My build scripts don't clean out the
old version and so it was just picing one at random. I'm now using the
latest PostgreSQL 9.1 JDBC4 (build 901).
This actually does seem to have resolved the issue, more or less. I am
seeing two invalid character symbols instead of an exception. This is
good enough for this client ;-)
Thanks for the help,
James
2011/10/29 Oliver Jowett <oliver@opencloud.com>:
> On 29 October 2011 18:21, James Pharaoh <james@phsys.co.uk> wrote:
>> The test case works for me, and also on the server. A little
>> investigation shows one big difference, the code I am using is somehow
>> using a JDBC2 statement class, whereas adding some output to the test
>> case when it runs successfully shows me using a JDBC4 one.
>>
>> Furthermore, the app in question has a page where I can enter queries
>> in groovy. Trying a similar testcase there also works, but I am
>> getting a JDBC3 statement class.
>
> Maybe you have two different copies of the driver floating around?
>
> Oliver
>
--
James Pharaoh
Pharaoh Systems Limited
http://phsys.co.uk/contact
