Can you file a JIRA report for the time being? Nothing immediately
suspicious jumps out at me in the stack trace, but I am still fairly
confident that this has something to do with our special blob
handling in Oracle.
On Jan 3, 2007, at 10:14 AM, Kevin Sutter wrote:
Marc,
Kevin-
Also, this exception is supposedly only being produced with Oracle,
not
DB2. (I have not been able to verify that yet.) This would seem to
indicate that it's dictionary-specific, but I'm not seeing anything
there
yet...
Does Oracle even support blob primary keys? My recollection
Can you have java field of type byte[] that maps to a NUMERIC (or
heck a varchar) in he db? I'm guessing that Kevin's guid is a fixed
128 bit number. If it is and he can map it to a non-blob type, it
should be possible to join with any database system.
-dain
On Jan 2, 2007, at 3:09 PM,
You can use use RAW(16) to store GUIDs in Oracle. This datatype is
allowed in primary keys.
--
Regards,
Igor
Dain Sundstrom wrote:
Can you have java field of type byte[] that maps to a NUMERIC (or heck a
varchar) in he db? I'm guessing that Kevin's guid is a fixed 128 bit
number. If it is
Interesting ... sounds like a legit bug, then (although it bears
noting that byte[] primary keys aren't actually allowed by the JPA
spec, as per section 2.1.4 ... support for them is an OpenJPA
extension).
My guess is that this only affects Oracle, due to our special
handling of blobs.
: @IdClass annotation for id field of type byte[]
Can you have java field of type byte[] that maps to a NUMERIC (or
heck a varchar) in he db? I'm guessing that Kevin's guid is a fixed
128 bit number. If it is and he can map it to a non-blob type, it
should be possible to join with any