Re: [INTERFACES] problem with getBytes - Mailing list pgsql-interfaces

From Rafal Piotrowski (CSCS)
Subject Re: [INTERFACES] problem with getBytes
Date
Msg-id 383A548E.3A0364F@CSCS.CH
Whole thread Raw
In response to Re: [INTERFACES] problem with getBytes  (Peter Mount <peter@retep.org.uk>)
Responses Re: [INTERFACES] problem with getBytes
List pgsql-interfaces
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. 

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.

Do you have any idea, what is going on?

thanks,

RP
-- 
..............................................................................
:           Rafal Piotrowski             :
mailto:Rafal.Piotrowski@CSCS.CH   :
:          Research Scientist            :
http://www.cscs.ch/~rpiotrow      :
: Centro Svizzero di Calcolo Scientifico : Tel.: +41 (0)91 610
8211          :
:       Via Cantonale, Galleria 2        :       +41 (0)91 610 8315
(direct) :
:       CH-6928 Manno, Switzerland       : Fax:  +41 (0)91 610
8383          :
..............................................................................


pgsql-interfaces by date:

Previous
From: Peter Mount
Date:
Subject: Re: [INTERFACES] table very big !!!!!
Next
From: Michael Meskes
Date:
Subject: header problem