Thread: problems with setBytes getBytes
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?
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 > >
Read the 7.2 documentation for the jdbc driver. It describes how to revert back to the old behavior. --Barry 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 >