Re: upper bug?

If you don't set NLS_LANG you get US7ASCII, depending on which O/S you are using. Unixes -> US7ASCII, NT -> WE8ISO8859P1.

That's the default, it is documented (but nobody reads docs) and it has been posted here *many* times.
There are no disadvantages of using 8-bit

Regards

--
Sybrand Bakker
Senior Oracle DBA

to reply remove '-verwijderdit' from my e-mail address


"Richard Kuhler" <noone_at_nowhere.com> wrote in message
news:NpwE8.1133$V71.752514_at_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

> > >

>