"Chris Campbell" <[EMAIL PROTECTED]> writes:
> For Oracle schema, toque is creating VARBINARY columns (The ObjectData
> columns in particular) as LONG RAW. My Oracle friends tell me that LONG
> RAW can be up to 2 gigs in size and that RAW would be a better choice
> for most of these columns for reasons of efficiency, not to mention you
> can only put one LONG RAW in an Oracle table. Now RAW can be up to 2k in
> size. Would I run into any problems with turbine if I make this change?
> Does anyone have an example of an object that may exceed 2k that gets
> put into these columns?
Hi Chris. RAW is more appropriate -- we have it set to RAW in the
HEAD. I've backported my HEAD fixes to the tip of the 2.1 branch.
Here it is as it stands now:
BIT = NUMBER (1, 0)
TINYINT = NUMBER (3, 0)
SMALLINT = NUMBER (5, 0)
INTEGER = INT
BIGINT = NUMBER (20, 0)
FLOAT = FLOAT
REAL = NUMBER
DOUBLE = FLOAT
NUMERIC = NUMBER
DECIMAL = NUMBER
CHAR = CHAR
VARCHAR = VARCHAR2
LONGVARCHAR = VARCHAR2 (2000)
DATE = DATE
TIME = DATE
TIMESTAMP = DATE
BINARY = RAW
VARBINARY = RAW
LONGVARBINARY = LONG RAW
NULL =
OTHER =
JAVA_OBJECT =
DISTINCT =
STRUCT =
ARRAY =
BLOB = BLOB
CLOB = CLOB
REF =
Stephanie also posted this great links
<http://technet.oracle.com/doc/oracle8i_816/java.816/a81354/basic3.htm>,
which is now in Oracle's db.props file.
Daniel Rall
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
