From: | dmp <danap(at)ttc-cmc(dot)net> |
---|---|
To: | pgsql-jdbc(at)postgresql(dot)org |
Subject: | Bytea Hex Format |
Date: | 2009-08-10 15:05:05 |
Message-ID: | 4A803721.3070102@ttc-cmc.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
Hello,
Listed on commits for PostgreSQL this week was one from Tom Lane:
"Support hex-string input and output for type BYTEA. Both hex format
and the traditional "escape" format are automatically handled on
input. The output format is selected by the new GUC variable
bytea_output. As committed, bytea_output defaults to HEX, which is
an *incompatible change*. We will keep it this way for awhile for
testing purposes, but should consider whether to switch to the more
backwards-compatible default of ESCAPE before 8.5 is released.
Peter Eisentraut"
Is this going to effect the JDBC default behavior, currently the
the MySQLView program uses getBytes() to dump data for BYTEA and
that is in Octal format.
Dana Proctor
MyJSQLView Project Manager
From | Date | Subject | |
---|---|---|---|
Next Message | Kris Jurka | 2009-08-10 22:52:51 | Re: Bytea Hex Format |
Previous Message | Sylvain Leroux | 2009-08-06 13:49:07 | Re: Using BigInteger as argument to AbstractJdbc2Statement.setObject |