Hi! I see... I specially like this quote:
"The drawback of using locales other than C or POSIX in PostgreSQL is its performance impact. It slows character handling and prevents ordinary indexes from being used by LIKE. For this reason use locales only if you actually need them."
In this situation, I really prefer to drop the accentuation (it's an username).
<rant mode>How can we be in 2008 and accentuated characters are still a problem!? Must become farmer, must become farmer...
</rant mode> Yours Miguel Arroz On 2008/04/02, at 12:33, Ralf Schuchardt wrote:
Hi Miguel,I think you must initialize your database cluster with the correct locale, to get this working (see http://www.postgresql.org/docs/8.3/interactive/locale.html) .Ralf Schuchardt Am 02.04.2008 um 03:34 schrieb Miguel Arroz:I created an UNIQUE INDEX using the lower() function to create a case-insensitive UNIQUE constraint. I tested this and I noticed it's failing on accentuated characters. The problem is this:select lower('JoÃo'); lower ------- joÃo (1 row) lower() is not "lowering" the accentuated characters._______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/arroz%40guiamac.com This email sent to [EMAIL PROTECTED]
Miguel Arroz http://www.terminalapp.net http://www.ipragma.com
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to [EMAIL PROTECTED]
