what characterset to use?
in [Oracle]
|
Prev: OID/LDAP problem - Any help with a fix would be appreciated
Next: Oracle11 & statistics calculations
From: sybrandb on 1 Sep 2007 17:26 On Sat, 01 Sep 2007 13:11:47 +0200, Frank van Bortel <frank.van.bortel(a)gmail.com> wrote: >So, you are an advocate of keeping the characterset of the client >the same as for the database?!? >Because you do: you say the Database should adhere the OS characterset. >As far as any utility, running on the server is concerned, those >utilities are *clients* to the server. >Utter nonsense to jump on Laurenz like that, Sybrand, when you claim >the very same. Reading seems to be quite difficult for several people nowadays. In my situation I *don't* have clients running on the server. They are all running on Winblows. So: set the characterset of the database to the characterset of the O/S: WE8ISO8859P15 on *Nix and MSWIN1252 on Winblows. Set the characterset of the client (a *different* system) to the characterset of the client O/S, usually MSWIN1252. Actually this is the situation when you use the installation defaults on *Nix and on Winblows. Why people set their charactersets to US7ASCII beats me. Why you jump on me and accuse me of something I never stated, beats me too. -- Sybrand Bakker Senior Oracle DBA
From: Frank van Bortel on 2 Sep 2007 07:38 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 sybrandb(a)hccnet.nl wrote: > In my situation I *don't* have clients running on the server. > They are all running on Winblows. Weren't discussing your situation. > > So: set the characterset of the database to the characterset of the > O/S: WE8ISO8859P15 on *Nix and MSWIN1252 on Winblows. No, no need at all - and, P15 is not Unix - P1 is. > Set the characterset of the client (a *different* system) to the > characterset of the client O/S, usually MSWIN1252. Agree - goes for the environment variables (registry on Windows) on the server machine as well > Actually this is the situation when you use the installation defaults > on *Nix and on Winblows. As I claimed > Why people set their charactersets to US7ASCII beats me. Dunno either. Remnants from times long gone? - -- Regards, Frank van Bortel Top-posting is one way to shut me up... -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (MingW32) iD4DBQFG2qCZLw8L4IAs830RAu8xAJ9LGZV0EUN2h49vTGJe/+Lqt2+aUQCYp/cg 42ry4m00fSp3ROuxHd9MYA== =uGo8 -----END PGP SIGNATURE-----
From: sybrandb on 2 Sep 2007 18:21
On Sun, 02 Sep 2007 13:38:01 +0200, Frank van Bortel <frank.van.bortel(a)gmail.com> wrote: >> So: set the characterset of the database to the characterset of the >> O/S: WE8ISO8859P15 on *Nix and MSWIN1252 on Winblows. > >No, no need at all - and, P15 is not Unix - P1 is. Actually most Unixes support P15, at least Solaris and AIX. P1 doesn't support the Euro sign. P15 does. P15 exists because the ISO committee couldn't agree on changing P1. -- Sybrand Bakker Senior Oracle DBA |