From owner-freebsd-stable@FreeBSD.ORG Mon Mar 20 17:16:26 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D1A1416A401 for ; Mon, 20 Mar 2006 17:16:26 +0000 (UTC) (envelope-from LoN_Kamikaze@gmx.de) Received: from mail.gmx.net (mail.gmx.de [213.165.64.20]) by mx1.FreeBSD.org (Postfix) with SMTP id 9F42243D48 for ; Mon, 20 Mar 2006 17:16:25 +0000 (GMT) (envelope-from LoN_Kamikaze@gmx.de) Received: (qmail invoked by alias); 20 Mar 2006 17:16:24 -0000 Received: from cable194106210-011.astral.lodz.pl (EHLO [192.168.0.207]) [194.106.210.11] by mail.gmx.net (mp020) with SMTP; 20 Mar 2006 18:16:24 +0100 X-Authenticated: #5465401 Message-ID: <441EE362.8060008@gmx.de> Date: Mon, 20 Mar 2006 18:16:18 +0100 From: "[LoN]Kamikaze" Organization: Lords of Nightmare User-Agent: Thunderbird 1.5 (X11/20060128) MIME-Version: 1.0 To: Vivek Khera , freebsd-stable@freebsd.org References: <1CC90809-B601-425F-AA6C-9927F7EA97AA@khera.org> In-Reply-To: <1CC90809-B601-425F-AA6C-9927F7EA97AA@khera.org> X-Enigmail-Version: 0.94.0.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 Cc: Subject: Re: utf-8 support in libc? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Mar 2006 17:16:26 -0000 If you make sure that your data goes into the database in a binary safe form (look for escape methods supplied by your favourite programming language) it doesn't matter how the database is encoded, because you will always get the data back the way you put it in. Vivek Khera wrote: > Reading thru one of the postgres mailing lists regarding which character > encoding to use for a database, someone chimed in and claimed this: > > Umm, you should choose an encoding supported by your platform and the > locales you use. For example, UTF-8 is a bad choice on *BSD because > there is no collation support for UTF-8 on those platforms. On > Linux/Glibc UTF-8 is well supported but you need to make sure the > locale you initdb with is a UTF-8 locale. By and large postgres > correctly autodetects the encoding from the locale. > > Is this an accurate claim for FreeBSD? I need to have a UTF-8 encoded > database in an upcoming project, and performance is always a concern. > > Thanks. > > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > >