| From: | Kris Jurka <books(at)ejurka(dot)com> |
|---|---|
| To: | dmp <danap(at)ttc-cmc(dot)net> |
| Cc: | pgsql-jdbc(at)postgresql(dot)org |
| Subject: | Re: Bytea Hex Format |
| Date: | 2009-08-10 22:52:51 |
| Message-ID: | alpine.BSO.2.00.0908101851360.16919@leary.csoft.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-jdbc |
On Mon, 10 Aug 2009, dmp wrote:
> "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*.
>
> 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.
>
It will require a change to the JDBC driver to correctly interpret hex
escaped bytea data (which hasn't happened yet), but JDBC users will not
need to change anything, getBytes will still be the call to use.
Kris Jurka
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kris Jurka | 2009-08-11 05:07:29 | Re: Using BigInteger as argument to AbstractJdbc2Statement.setObject |
| Previous Message | dmp | 2009-08-10 15:05:05 | Bytea Hex Format |