Prem K Mehrotra wrote:
> "Guyon Morée" <gumuz_at_NO_looze_SPAM.net> wrote in message news:<416a84f7$0$286$4d4ebb8e_at_news.nl.uu.net>...
>
>>Thanks for your quick reply.
>>
>>As I mentioned, this behaviour seems to be version specific. Do yo have any
>>details on that?
>>
>>thanx
>>
>>guyon
>>
>>"Frank van Bortel" <fvanbortel_at_netscape.net> wrote in message news:ckdm78
>>
>>>BYTE would be the default; the other possibility is CHAR.
>>>So, technically, there is no difference between the two (BYTE
>>>being default), the difference is in the CHAR option: a character
>>>can take more that one byte (up to 3 byte, iirc). Think multibyte
>>>character sets.
>>>This option tells a multibyte database (!) to use character semantics
>>>when storing data: a varchar2(10) would be able to store 10 characters,
>>>in stead of 10 byte worth of characters.
>>>
>>>BTW - you can tell TOAD to suppress this...
>
>
> I think this was introduced in Oracle9i. It defintely was not there in Oracle8i
> and earlier releases.
Ah - not the TOAD version, then....
Correct, there was no need when only NVARCHAR could be multibyte;
asof 9i, the standard characterset can be a multibyte one.
--
Regards,
Frank van Bortel
Received on Tue Oct 12 2004 - 03:22:16 CDT
