Jason McKerr wrote:
Hey guys, a lot of people are running into the problem of two LONG RAW columns in Oracle. In the OJB_DMAP_ENTRIES two LONGVARBINARY are created.
In oracle, this translates to two LONG RAW columns which is illegal in oracle 9i or 8i.
So basically, I need to know if it's OK to use RAW columns for the various LONGVARBINARY columns in the OJB Core tables?
Yes, that should be fine.
We need those columns to store gzipped serialized Identity Objects. Unfortunately there is no fixed size to them (an Identity could have any number of primary key attributes).
But they should < 1024 bytes for nearly all possible applications.
so using raw(2000) should be perfect.
If so, can you guys change the db.props file in the torque/sql/base/oracle directory to RAW?
We have to tell the Torque team about this issue.
Maybe it's easier to simply change LONGVARBINARY to VARBINARY in our torque scripts...
cheers, Thomas
The real issue is that RAW only supports 2000 length, and LONG raw is 2 Gigs.
Jason
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
