Received: from localhost (IDENT:root@hectic-2.jpl.nasa.gov [128.149.68.204]) by hub.org (8.9.3/8.9.3) with ESMTP id LAA52508 for ; Thu, 10 Jun 1999 11:13:08 -0400 (EDT) (envelope-from lockhart@alumni.caltech.edu) Received: from alumni.caltech.edu (lockhart@localhost [127.0.0.1]) by localhost (8.8.7/8.8.7) with ESMTP id PAA15845; Thu, 10 Jun 1999 15:14:43 GMT Sender: lockhart@hub.org Message-ID: <375FD663.4645D0A@alumni.caltech.edu> Date: Thu, 10 Jun 1999 15:14:43 +0000 From: Thomas Lockhart X-Mailer: Mozilla 4.51 [en] (X11; I; Linux 2.0.36 i686) X-Accept-Language: en MIME-Version: 1.0 To: phd2@earthling.net CC: "'Oleg Bartunov'" , "'hackers@postgresql.org'" , Tatsuo Ishii Subject: Re: [HACKERS] Postgres 6.5 beta2 and beta3 problem References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit > What feedback do you want? I am pretty sure two Olegs on this list are > ready to continue the discussion. istm that the Russian and Japanese contingents could represent the needs of multibyte and locale concerns very well. So, we should ask ourselves some questions to see if we can make *progress* in evolving our text handling, rather than just staying the same forever. SQL92 suggests some specific text handling features to help with non-ascii applications. "national character" is, afaik, the feature which would hold an installation-wide local text type. "collations" would allow other text types in the same installation, but SQL92 is a bit fuzzier about how to make them work. Would these mechanisms work for people? Or are they so fundamentally flawed or non-standard (it is from a standard, but I'm not sure who implements it)? - Thomas -- Thomas Lockhart lockhart@alumni.caltech.edu South Pasadena, California