Re: [Re: JDBC compliance]

From: Abel Muiño <abel(dot)muinho(at)mundo-r(dot)com>
To: PostgreSQL JDBC List <pgsql-jdbc(at)postgresql(dot)org>
Subject: Re: [Re: JDBC compliance]
Date: 2003-01-08 16:31:25
Message-ID: 1042043485.7395.24.camel@calculin.casadeabel
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-jdbc

El mié, 08-01-2003 a las 17:08, Barry Lind escribió:

> In 7.1 and earlier only the LargeObject way of doing things was
> supported. In 7.2 the bytea way was added. But unfortunately this has
> left the driver in a bit of a confused state as you point out.
In my opinion, setBinaryStream should work on the same data type as
get/setBlob (even when the database doesn't properly support those),
because it is the only standard (i.e. without database specific code)
way of creating BLOBs. As far as I know, bytea columns can be read and
set with get/setBytes.

> If you haven't done so, I would strongly suggest reading the above
> mentioned documentation.
I've read that, but unfortunately, I need to work with old code (i.e.
use BLOBs/CLOBs) so I can't switch to setBytes/getBytes and I need to
create BLOBs/CLOBs in a standard-JDBC way (so can't use largeobjects
API).

By now, I'll stick to the 7.1 compatibility mode with database rules
for deleting the large objects when deleting the row.

Thanks for your help
--
Abel Muiño Vizcaino

In response to

Responses

Browse pgsql-jdbc by date

  From Date Subject
Next Message Abel Muiño 2003-01-08 17:26:22 Deletion of Large Objects (was Re: [Re: JDBC compliance])
Previous Message Barry Lind 2003-01-08 16:08:11 [Re: JDBC compliance]