Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Usenet -> c.d.o.server -> Re: upper bug?

Re: upper bug?

From: Richard Kuhler <noone_at_nowhere.com>
Date: Wed, 15 May 2002 16:55:09 GMT
Message-ID: <NpwE8.1133$V71.752514@twister.socal.rr.com>


Indeed it's USASCII7. Why does Oracle use that as the default? What are the disadvantages of using 8-bit?

Richard

Roman Mirzaitov wrote:
>
> Hi,
>
> what character set are you using? Isn't it 7-bit charset?
> I've just checked it with my 8-bit charset - works quite fine. (Oracle 8.1.7
> on Solaris)
>
> Regards,
> --
> Roman Mirzaitov
> Brainbench MVP for Oracle Administration
> www.brainbench.com
>
> "Richard Kuhler" <noone_at_nowhere.com> wrote in message
> news:poiE8.1404$DF2.385508_at_twister.socal.rr.com...
> > Why does the Oracle UPPER function convert ascii 128-255 into ascii
> > 0-127?
> >
> > > select ascii(upper(chr(128))) from dual;
> >
> > ASCII(UPPER(CHR(128)))
> > ----------------------
> > 0
> >
> > > select ascii(upper(chr(180))) from dual;
> >
> > ASCII(UPPER(CHR(180)))
> > ----------------------
> > 52
> >
> > > select ascii(upper(chr(255))) from dual;
> >
> > ASCII(UPPER(CHR(255)))
> > ----------------------
> > 127
> >
> >
> > Is there a way to fix this? Note: NLS_UPPER does the same thing.
> >
> >
> > Thanks,
> > Richard
> >
Received on Wed May 15 2002 - 11:55:09 CDT

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US