Re: problems with setBytes getBytes

From: Dave Cramer <Dave(at)micro-automation(dot)net>
To: Robert Dyas <rdyas(at)covont(dot)com>
Cc: "pgsql-jdbc(at)postgresql(dot)org" <pgsql-jdbc(at)postgresql(dot)org>
Subject: Re: problems with setBytes getBytes
Date: 2002-04-15 14:53:59
Message-ID: 1018882440.3983.4.camel@inspiron.cramers
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-jdbc

Robert,

Below is a copy of an email describing the solution to your problem

Dave

David,

The behavior you are describing is correct for the 7.2 driver. In 7.2
the driver now uses the bytea datatype to store binary data (not
largeobjects as it did in 7.1 and earlier). This is documented in the
7.2 documentation. Also in the doc is a description on how to revert
back to the old behavior.

Thanks,
--Barry
On Tue, 2002-04-09 at 20:05, Robert Dyas wrote:
>
> I am using Postgresql 7.1.3 on Linux (Redhat 7.2).
>
> Using a JDBC driver for that version, setBytes and getBytes works great.
> When I tried the new driver (latest on your web site April 9, 2002)
> everything works except setBytes getBytes don't work at all with oid
> columns. Since this used to work, this seriously breaks backward
> compatiability.
>
> Any ideas?
>
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 6: Have you searched our list archives?
>
> http://archives.postgresql.org
>
>

In response to

Browse pgsql-jdbc by date

  From Date Subject
Next Message Dave Cramer 2002-04-15 15:01:23 Re: Timestamp Problem (index out of range)
Previous Message Thomas O'Dowd 2002-04-15 14:34:00 Re: Timestamp Problem (index out of range)