what characterset to use?
in [Oracle]
|
Prev: OID/LDAP problem - Any help with a fix would be appreciated
Next: Oracle11 & statistics calculations
From: Laurenz Albe on 29 Aug 2007 06:28 sybrandb(a)hccnet.nl wrote: > Sucker. *plonk* Laurenz Albe
From: Ben on 29 Aug 2007 09:20 On Aug 29, 4:53 am, sybra...(a)hccnet.nl wrote: > On Tue, 28 Aug 2007 10:54:57 -0700, Ben <bal...(a)comcast.net> wrote: > >After reading this it sounds like Oracle is saying that conversion is > >a bad thing and that the database character set should be set the same > >as the client. > > That is EXACTLY what Oracle is NOT (I REPEAT: NOT) saying. > > Oracle SAYS: > THE DATABASE CHARACTERSET SHOULD BE THE SAME AS THE CHARACTERSET OF > THE O/S. > > WHAT IS SO DIFFICULT TO UNDERSTAND ABOUT THAT? > > -- > Sybrand Bakker > Senior Oracle DBA All caps.?.?. Yeah, that's it. It is definitely harder to understand something typed in all caps.
From: Shakespeare on 29 Aug 2007 10:47 "Ben" <balvey(a)comcast.net> schreef in bericht news:1188393646.062818.12200(a)k79g2000hse.googlegroups.com... > All caps.?.?. Yeah, that's it. It is definitely harder to understand > something typed in all caps. > It WOULD save some space in character sets though if everything was in UPPERCASE........... Shakespeare (What's in a case?)
From: joel garry on 29 Aug 2007 18:21 On Aug 29, 2:36 am, sybra...(a)hccnet.nl wrote: > On 29 Aug 2007 09:26:09 GMT, Laurenz Albe <inv...(a)spam.to.invalid> > wrote: > > >You are not only rude, but also clueless. > > Sucker. > > How often do you post anything useful? Ah jeez, Sybrand, Laurenz is one of the good guys. You seemed to have missed the "sounds like" qualifier in a couple of posts. Also, you may have misinterpreted what he meant by garbage in the db when there is no character conversion, or perhaps he should have said "potential garbage," as the characters wouldn't be changed until later. We can all agree that automatic conversion when it isn't wanted is a problem, can't we? jg -- @home.com is bogus. http://www.google.com/search?hl=en&q=%E2%80%9CPlaying+Russian+Roulette+with+Silver+Bullets%E2%80%9D&btnG=Google+Search
From: sybrandb on 29 Aug 2007 18:27
On Fri, 24 Aug 2007 14:05:46 +0200, "Martin T." <0xCDCDCDCD(a)gmx.at> wrote: >Laurenz Albe wrote: >> sybrandb(a)hccnet.nl wrote: >>>> (...) >> >> You got me wrong. >> >> Of course it is not Oracle's bug if I set my NLS_LANG wrong. >> >> But it is Oracle's bug (in my opinion) if I have set the client >> character set to US7ASCII, insert a byte > 127 in a text field, and >> neither get an error nor (as Oracle seems to prefer) have the byte >> clandestinely converted to a question mark. >> >> I claim that the missing check for incorrect characters is a bug. >> > >Amen. But still Oracle will probably tell you that it's a Feature, not a >Bug. It is not a bug. Laurenz Albe is, as usual, having everything wrong, clueless as he is on characterset issues. In this situation you will never notice anything when your database characterset is US7ASCII and your client characterset is US7ASCII. If the client O/S displays the character correctly everything will work. I am speaking from experience, been there, done that. Laurenz Albe just doesn't know what he is talking about (refer to his recent advise to set the database characterset to the characterset of the client, which is utterly stupid). -- Sybrand Bakker Senior Oracle DBA |