Hi Chris, Stephane. Stephane, I saw this in your original post (which
occurred while I was on vacation).
"Chris Campbell" <[EMAIL PROTECTED]> writes:
> This works fine for me. However I am noticing one problem. In Oracle you
> need to specify the size of a RAW, so the turbine-schema needs to have
> the size attribute put into the VARBINARY columns. This would cause
> problems for mysql users because mysql maps VARBINARY to MEDIUMBLOB
> which does not take a size. My "solution" was to set VARBINARY = RAW
> (2000) in the Oracle db.props file (I won't send a patch because this is
> not a general solution).
So I've been wondering which direction we should go on this. There
are two easy options: require a SIZE attribute for VARBINARY columns,
or don't. Personally, I don't see a clear path on this (experience
with more databases would be helpful). I would definitely need more
data with regard to common RDBMS implements of VARBINARY data types.
Does anyone have a good view of this information, or would be willing
to gather it?
> I am currently developing locally with mysql and deploying to oracle, so
> I need this flexibility. Just a heads up...
We definitely need to support this, one way or another.
Daniel Rall
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
