-Original Message-From: MacGregor, Ian
A. [mailto:[EMAIL PROTECTED]] Sent: Tuesday, February 11, 2003
4:04 PMTo: Multiple recipients of list ORACLE-LSubject:
RE: utf8
How
about
insert into () values
(CHR(2122));
Ian
MacGregor
Stanford Linear Acc
Title: Message
How
about
insert
into () values
(CHR(2122));
Ian
MacGregor
Stanford Linear Accelerator Center
[EMAIL PROTECTED]
-Original Message-From: Steve Main
[mailto:[EMAIL PROTECTED]] Sent: Tuesday, February 11, 2003 2:44
PMTo: Multiple recipients of list ORAC
Maybe I am wrong, but here is my thinking..
The problem is that the "DBA" on-site built a db using
US7ACII and then used the dbca to change the character
set to UTF8 and perform a partial re-install. My
thought was that some of the language specific .msb
files were not installed correctly during t
Obviously you need more details on the "lock-up" part. But I am curious as
to why you think UTF8 would be part of the "lock-up" issue??
TIA
Chris
-Original Message-
Sent: Monday, January 14, 2002 9:05 AM
To: Multiple recipients of list ORACLE-L
Folks,
I am starting a new project toda
Yes, I have it and no problem.
JP
On Wed 31. October 2001 17:15, you wrote:
> Hi,
>
> We are currently using NVARCHAR2 datatype to store our unicode data.
> We were told that if we use database character set as UTF8 then we can
> unicode data in varchar2 columns and can avoid NVARCHAR2 datatype a
It is true.
Igor Neyman, OCP DBA
[EMAIL PROTECTED]
- Original Message -
To: "Multiple recipients of list ORACLE-L" <[EMAIL PROTECTED]>
Sent: Wednesday, October 31, 2001 11:15 AM
> Hi,
>
> We are currently using NVARCHAR2 datatype to store our unicode data.
> We were told that if we us
