Path: text.usenetserver.com!out01a.usenetserver.com!news.usenetserver.com!in02.usenetserver.com!news.usenetserver.com!postnews.google.com!y42g2000hsy.googlegroups.com!not-for-mail From: Ben Newsgroups: comp.databases.oracle.server Subject: Re: what characterset to use? Date: Mon, 27 Aug 2007 05:18:22 -0700 Organization: http://groups.google.com Lines: 59 Message-ID: <1188217102.287058.162900@y42g2000hsy.googlegroups.com> References: <1187787354.180425.72550@d55g2000hsg.googlegroups.com> <1187788114.490146.19240@57g2000hsv.googlegroups.com> <1187797142.181722.138450@l22g2000prc.googlegroups.com> <3j1pc3t2dc0k6rk6q1m4vf5v43tvlrfkip@4ax.com> <1187871755.715063.275670@m37g2000prh.googlegroups.com> <1187877195.908940@proxy.dienste.wien.at> <1187877730.087181.271380@i13g2000prf.googlegroups.com> <1187896740.215825.27680@z24g2000prh.googlegroups.com> <46ceb6b5$0$1346$834e42db@reader.greatnowhere.com> NNTP-Posting-Host: 208.62.121.66 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-Trace: posting.google.com 1188217102 15805 127.0.0.1 (27 Aug 2007 12:18:22 GMT) X-Complaints-To: groups-abuse@google.com NNTP-Posting-Date: Mon, 27 Aug 2007 12:18:22 +0000 (UTC) In-Reply-To: <46ceb6b5$0$1346$834e42db@reader.greatnowhere.com> User-Agent: G2/1.0 X-HTTP-UserAgent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; InfoPath.1),gzip(gfe),gzip(gfe) X-HTTP-Via: 1.0 POISA01 Complaints-To: groups-abuse@google.com Injection-Info: y42g2000hsy.googlegroups.com; posting-host=208.62.121.66; posting-account=ps2QrAMAAAA6_jCuRt2JEIpn5Otqf_w0 Xref: usenetserver.com comp.databases.oracle.server:433920 X-Received-Date: Mon, 27 Aug 2007 08:18:22 EDT (text.usenetserver.com) On Aug 24, 6:40 am, "Martin T." <0xCDCDC...@gmx.at> wrote: > Ben wrote: > > On Aug 23, 2:48 pm, sybra...@hccnet.nl wrote: > >> On Thu, 23 Aug 2007 07:02:10 -0700, Ben wrote: > >>> I'm not saying it is feasible to have a database set to use US7ASCII > >>> as its character set. I'm simply saying that in the scenario that > >>> Sybrand listed, 1 database and 1 client both being set to us7ascii, I > >>> don't see the issue. UNLESS you introduce a client using a different > >>> character set. > >> Ok, again > > >> Client set to US7ASCII > >> Database set to US7ASCII > >> You send an eight bit character. > >> Oracle sees 7 bit client character set, 7 bit server character set > >> ---> > >> HEY, I DON'T HAVE TO CONVERT ANY CHARACTER. > >> What will happen if all of a sudden someone decides to export using 7 > >> bit NLS_LANG and import into 8 bit database. > > >> Please don't imply I'm making up fairy tales, I'm talking stories for > >> grown ups!!!! > >> REAL WORLD HORROR STORIES with customers getting GROSS!!! > > >> And yes: this explanation is on Metalink!!! > > >> -- > > > I'm not implying anything. I'm trying to understand. > > > How do you insert an 8 bit character with a 7 bit client into a db > > with a 7 bit character set? Wouldn't that be a square peg round hole > > kind of thing? You of course wouldn't get the 8 bit character back out > > of the 7 bit db. > > > (...) > > What you really need to understand is that the character sets (NLS_LANG) > you tell Oracle about are ONLY there for conversion. > Oracle doesn't give a damn if you have a database which is told it's > UTF8 and the values residing in the VARCHAR2 columns are actually > WE8ISO8859P2. Oracle doesn't care. Only if you try to retrieve this data > with e.g. a JDBC driver, you will get a Java Exception telling you it > could not convert the UTF8 data. > > So the character sets of the clients and the DB are only there to tell > oracle if it has to convert or not. And if they are the same, no > conversion will take place. (And if the client "lies" you end up with > crap in your DB.) > > br, > Martin- Hide quoted text - > > - Show quoted text - Thank you Martin, I wasn't really understanding that Oracle would actually allow the insertion of the data. Good explanation. Thank you again.