Received: from sss.sss.pgh.pa.us (sss.pgh.pa.us [206.210.65.6]) by hub.org (8.9.2/8.9.1) with ESMTP id KAA15707; Thu, 11 Feb 1999 10:35:30 -0500 (EST) (envelope-from tgl@sss.pgh.pa.us) Received: from sss.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.sss.pgh.pa.us (8.9.1/8.9.1) with ESMTP id KAA14222; Thu, 11 Feb 1999 10:35:00 -0500 (EST) To: pgsql-hackers@postgreSQL.org cc: maillist@remo.demon.co.uk (Neil Burrows), pgsql-sql@postgreSQL.org Subject: Re: [HACKERS] Re: [SQL] RULE questions. In-reply-to: Your message of Thu, 11 Feb 1999 07:33:00 -0500 (EST) Date: Thu, 11 Feb 1999 10:35:00 -0500 Message-ID: <14220.918747300@sss.pgh.pa.us> From: Tom Lane "D'Arcy" "J.M." Cain writes: > Second, an option to CREATE INDEX to make the index case insensitive. That, at least, we can already do: build the index on lower(field) not just field. Or upper(field) if that seems more natural to you. > Also, in a primary key field (or > unique index) it would be nice if "A" was rejected if "a" already was > in the database. Making either of the above a UNIQUE index should accomplish that. regards, tom lane