Re: JDBC 9.2 DEV not working with Hex bytea output? - Mailing list pgsql-jdbc

Can you provide us with a test case?

I'll create a simple test case - but this happened inside a complex application using JEE stack (JSP/Servlets/WebServices/JPA/Jdbc), so would not be as fast as I could wish.

Just to clarify are you using the 9.2 1002 driver ?

Yes, 9.2 1002 driver. The only change in sources are the ones related to the warnings output, which I needed to debug my triggers.

Regards,

Edson

Dave Cramer

dave.cramer(at)credativ(dot)ca
http://www.credativ.ca

On Sun, Mar 31, 2013 at 10:32 AM, Edson Richter <edsonrichter@hotmail.com> wrote:

Hi!

I've downloaded source code for JDBC driver in order to output warnings during development phase of my application (so I can catch triggers messages at client side of the application).

This is the only change I've made (System.out... in addWarning methods - there is two: one for connection, one for statement).

Nevertheless, I has been obligated to change "alter database xxx set bytea_output='escaped'" in order to work.

In our production databases we have this option set to "hex", and works fine - is just with 9.2 DEV 1002 sources.

Is this a known issue?


Thanks,

Edson


--
Sent via pgsql-jdbc mailing list (pgsql-jdbc@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-jdbc