Received: from localhost (postgresql.org [64.49.215.8])
	by postgresql.org (Postfix) with ESMTP id A1CDB4769A7
	for <pgsql-sql@postgresql.org>; Mon, 16 Sep 2002 09:43:07 -0400 (EDT)
Received: from sss.pgh.pa.us (unknown [192.204.191.242])
	by postgresql.org (Postfix) with ESMTP id DB6FB476537
	for <pgsql-sql@postgresql.org>; Mon, 16 Sep 2002 09:38:45 -0400 (EDT)
Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1])
	by sss.pgh.pa.us (8.12.5/8.12.5) with ESMTP id g8GDck5D026276;
	Mon, 16 Sep 2002 09:38:47 -0400 (EDT)
To: "J rg" <mail2holly@gmx.de>
Cc: pgsql-sql@postgresql.org
Subject: Re: How can unique columns being case-insensitive be accomplished? 
In-reply-to: <alsac7$30gc$1@news.hub.org> 
References: <alsac7$30gc$1@news.hub.org>
Comments: In-reply-to "J rg" <mail2holly@gmx.de>
	message dated "Fri, 13 Sep 2002 11:07:57 +0200"
Date: Mon, 16 Sep 2002 09:38:46 -0400
Message-ID: <26275.1032183526@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
X-Virus-Scanned: by AMaViS new-20020517
X-Archive-Number: 200209/171
X-Sequence-Number: 9448

"Jörg" <mail2holly@gmx.de> writes:
> How can this problem be overcome? Any ideas?

Create a unique index on lower(name).

			regards, tom lane