Craig Russell wrote: > Hi Erik, > > On Jul 21, 2005, at 2:10 AM, [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> > wrote: >
>> CHAR(1) will not allow Unicode storage, you need either to use NCHAR(1), >> CHAR(4) or another type that allows you to store 2 bytes. > > > Correct. The point is what should be the default. Well, implementation defined really. Derby defines CHAR(1) as storage for one *character*, not one byte, character is really the intent of the SQL spec. Derby always uses Unicode as the character set, so CHAR(1) can store any Unicode character from Java. Dan.
