Re: Possible bug with BYTEA and JDBC - Mailing list pgsql-bugs

From Gregory Kotsaftis
Subject Re: Possible bug with BYTEA and JDBC
Date
Msg-id 120534.58062.qm@web35307.mail.mud.yahoo.com
Whole thread Raw
In response to Re: Possible bug with BYTEA and JDBC  (Kris Jurka <books@ejurka.com>)
List pgsql-bugs
Kris you are without a doubt a life saver!
Being new to blobs altogether, this issue gave me a really hard time for mo=
re than a week! Thanks for the possible solutions (I will probably go with =
2 or 1).
Thank you very much (and I REALLY mean it!)
Greg :)

--- On Sun, 2/14/10, Kris Jurka <books@ejurka.com> wrote:

> From: Kris Jurka <books@ejurka.com>
> Subject: Re: [BUGS] Possible bug with BYTEA and JDBC
> To: "Gregory Kotsaftis" <gregkotsaftis@yahoo.com>
> Cc: pgsql-bugs@postgresql.org
> Date: Sunday, February 14, 2010, 4:42 PM
>=20
>=20
> On Sat, 13 Feb 2010, Gregory Kotsaftis wrote:
>=20
> > postgresql-8.4-701.jdbc4.jar
> > postgresql-8.5alpha3
> >=20
> > I followed the steps in the blob tutorial and tried to
> test the BYTEA example:
>=20
> The 8.5/9.0 release has changed the default bytea output
> format and the 8.4 JDBC driver does not support it.=A0
> You've got a couple of options:
>=20
> 1) Change the bytea format back to the 8.4 supported
> format.=A0 Set bytea_output =3D escape in your
> postgresql.conf.
>=20
> 2) Build the JDBC driver from CVS which does support the
> new format.
>=20
> 3) Use an 8.4 server.
>=20
> Kris Jurka
>=20

pgsql-bugs by date:

Previous
From: "IP"
Date:
Subject: Re: BUG #5318: Inconsistent PHP pg_result_error_field PGSQL_DIAG_SOURCE_FUNCTION across instalations
Next
From: "Sadao Hiratsuka"
Date:
Subject: BUG #5326: The 2nd update of a table which has foreign keys is blocked.