> -----Original Message-----
> From: Daniel Rall [mailto:[EMAIL PROTECTED]]
> Use the SIZE attribute for that column instead. BINARY/VARBINARY are
> analogous to CHAR/VARCHAR, which requires the SIZE attribute.
Right, we should change the definition instead....but in the schema then, it
has to be specified so that it works correctly on all DB. There are a couple
of definition that specify a VARBINARY type without size in the turbine
schema if I'm not wrong.
> > I changed the definition of CHAR, VARCHAR and LONGVARCHAR as well.
>
> What is the benefit of the Oracle CHAR data type over its VARCHAR2
> type? (I'm not very familiar with Oracle.) Though the JDBC VARCHAR
This one seems to be a religious war, I can't really say but see the link
below for JDBC mapping.
> definition is marked changed by your CVS diff, I don't actually see
> any change (whitespace difference?). LONGVARCHAR should definitely
> remain a sized value (as the LONG prefix indicates).
I used the mapping as specified here:
http://technet.oracle.com/doc/oracle8i_816/java.816/a81354/basic3.htm#102352
9
About the VARCHAR, it is maybe a whitespace. Sorry about the noise.
> > Question: Should a CHAR handle Unicode (ie CHAR(2)) or not
> (CHAR / CHAR(1))
>
> The JDBC CHAR type should map to an Oracle type which handles
> Unicode. What Oracle type should we be using for this?
According to the doc, a JDBC.CHAR is a CHAR..so let's go for this one. :)
--
Stephane Bailliez
Software Engineer, Paris - France
iMediation - http://www.imediation.com
Disclaimer: All the opinions expressed above are mine and not those from my
company.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
