Two questions :
1. Which java type (byte[] ?) do you map to which jdbc type when CMPing a
BLOB for Oracle?
2. Did you made it work with CLOB ? (and if so, what was the type mapping ?)
Shahar.
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Jeffrey Wescott
Sent: Monday, January 29, 2001 4:27 AM
To: jBoss
Subject: Re: [jBoss-User] CMP (JAWS), Oracle and BLOBs
Yes, CMP BLOBs work fairly well for store / retrieve in JBossCMP (a.k.a.
JAWS). Doing ad-hoc queries across BLOBs (at least under Oracle 8i)
proves pretty difficult, however. Avoid them if you can.
++Jeff
Shahar Solomianik wrote:
> Hi.
> Let me understand...
> Did someone had CMP BLOB working somwhow ???
>
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Scot Bellamy
> Sent: Friday, January 26, 2001 10:01 PM
> To: jBoss
> Subject: Re: [jBoss-User] CMP (JAWS), Oracle and BLOBs
>
>
> I haven't used BLOBs so I can't comment on a work around, hopefully
> someone else has and can comment. As far as other Oracle drivers, I
> don't know of any other type 4 drivers. Merant has a type 3 driver that
> works well and may solve the problem you have. It is expensive though,
> about $4000.00/cpu the last I checked :-(.
>
> Scot.
>
> Jeffrey Wescott wrote:
>
>> Hi, all.
>>
>> I'm using JBoss-2.0-FINAL and have written several CMP Entity beans of
>> the sort where there are nested entity beans and nested collections of
>> entity beans, for example:
>>
>> Consider three entity beans: A, B and C. Entity Bean A has as a
>> CMP-managed field a Collection of Entity bean C objects. Entity Bean
>> B has as a CMP-managed field an Entity bean A object.
>>
>> As far as I can tell, JAWS handles this correctly. However, with the
>> Oracle 8i driver (classes12.zip), there is one issue. In the
>> ejbCreate() method for your beans, you have to make sure that any
>> fields on the bean that map to the Oracle type "BLOB" are non-null.
>> That means that in the example above, the ejbCreate() method for A
>> would have to create an empty ArrayList or Vector for its collection
>> field and the ejbCreate() method for B would have to create a non-null
>> "dummy" A object. The reason is that the Oracle "thin" driver doesn't
>> support passing null arguments for BLOB parameters in PreparedStatements.
>>
>> My questions are:
>>
>> 1- Has anyone come up with a good workaround for this aside from
>> creating the dummy objects and empty Collections as I described
>> above? If so, can I get some sample code?
>>
>> 2- Does anyone know of a type IV driver for Oracle that doesn't have
>> this limitation?
>>
>> Please don't tell me to use the OCI driver for Oracle, because it's
>> not an option for us.
>>
>> Thanks.
>>
>> ++Jeff
>>
>>
>>
>> --
>> --------------------------------------------------------------
>> To subscribe: [EMAIL PROTECTED]
>> To unsubscribe: [EMAIL PROTECTED]
>> List Help?: [EMAIL PROTECTED]
>>
>>
>
>
>
> --
> --------------------------------------------------------------
> To subscribe: [EMAIL PROTECTED]
> To unsubscribe: [EMAIL PROTECTED]
> List Help?: [EMAIL PROTECTED]
>
>
>
> --
> --------------------------------------------------------------
> To subscribe: [EMAIL PROTECTED]
> To unsubscribe: [EMAIL PROTECTED]
> List Help?: [EMAIL PROTECTED]
>
>
>
>
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
List Help?: [EMAIL PROTECTED]
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
List Help?: [EMAIL PROTECTED]
