On Tue, 23 Nov 1999, Rafal Piotrowski (CSCS) wrote:
> Peter Mount wrote:
> > > One more thing, setBytes method, does work, but only if the array of
> > > bytes is not too big. (I don't know the exact size) :-(
> > You may need to look at the LargeObject api, which is additional to the
> > JDBC api.
> I don't want to use the LargeObject API, because I want to make my
> application easy to port to different DBMS. And since LargeObject API is
> not in for example in JDBC for mySQL, I don't want to use it.
Thats a good point.
> Anyway, I have used it before, and I have noticed the following thing:
> when I store an object, and then try to rewrite the object (the new
> object is bigger), nothing huppens. Well, the size of the object
> changes, but when I retreive the data from the object, it is unchanged
> :-? (i.e. I get the original object, the first one stored).
> I thing that is odd. Something simmilar huppens, when I reduce the size
> of the object and write it. Except that the size of the LargeObject does
> not change, it staies the same, as it was.
That sounds like a problem in the backend - unless a new lo is created,
but your code is refering to the old one.
Peter T Mount peter(at)retep(dot)org(dot)uk
Main Homepage: http://www.retep.org.uk
PostgreSQL JDBC Faq: http://www.retep.org.uk/postgres
Java PDF Generator: http://www.retep.org.uk/pdf
In response to
pgsql-interfaces by date
|Next:||From: Nigel Berkeley||Date: 1999-11-24 00:58:23|
|Subject: PgAccess 0.98 and libpq.so.2|
|Previous:||From: Hiroshi Inoue||Date: 1999-11-23 13:17:40|
|Subject: Re: [INTERFACES] table very big !!!!!|