Mailing-List: contact ojb-dev-help@db.apache.org; run by ezmlm
References: <3EB7B0BF.10802@alma.nu> <3129.1052228035@www54.gmx.net>
 <3EB7BF2D.9030201@alma.nu> <3EBA3E4F.5060403@alma.nu> <3EBB420D.50501@web.de>
 <BAY2-DAV614VEm0Gcr800004a88@hotmail.com> <3EBF8429.8060109@alma.nu>
From: "Thomas Poeschmann" <t.poeschmann@exxcellent.de>
MIME-Version: 1.0
Subject: Re: Oracle 9i BLOB malfunction / 4k mystery
To: "OJB Developers List" <ojb-dev@db.apache.org>
Content-type: text/plain; charset= "iso-8859-1"
Date: Mon, 12 May 2003 16:05:08 +0200
Content-transfer-encoding: quoted-printable
Message-Id: <81b33ffe2fbf2fc26db4817de10540c53ebfa9bf@exxcellent.de>

Hi there,

> Michael Mogley wrote:
> Thomas Poeschmann says on the list that he almost has a solution,
> using the above method I presume.

Yes, of course using the SELECT FOR UPDATE. Sorry for promising posting code
but not doing it, but I will try to find it this evening. It is probably just 
for reference for you, since you already have it.

> Are there other dbmses and drivers that exhibit the same irregular 
> behavior regarding LOB=B4s.

Not that I know. Sometimes it is different to call one of the methods on a
statement to bring certain Java objects in. For example passing an array in as
a String. But I have never seen anything hard as Oracle XLOBs ;)

> Unfortunatly, our solution (apart from the the fix submitted) currently 
> consists of changing to the oci driver. Sad but true.

Which has other drawbacks, but well... Other ORM can not handle it either with
thin, by the way ;)

Kind regards,

Thomas