Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id E836C9FB326 for ; Sat, 28 Oct 2006 11:59:15 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 77658-06 for ; Sat, 28 Oct 2006 11:59:12 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey- Received: from web31810.mail.mud.yahoo.com (web31810.mail.mud.yahoo.com [68.142.207.73]) by postgresql.org (Postfix) with SMTP id 861B69FB280 for ; Sat, 28 Oct 2006 11:59:12 -0300 (ADT) Received: (qmail 88849 invoked by uid 60001); 28 Oct 2006 14:59:09 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:Date:From:Subject:To:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID; b=36TlF+N0q3dA34YkKRxgKr9HmAk1z6krK8HMEKPUat0h+/RrFvMnLEpkZytbAdwLGsSTws2UPFnPqxRkRt4TPpxVV5ngttwjgGbJ19b4h2qHu2zc9QrCNvHTq1XAbCQ0971oQuzaCUduWUS3umsUw5VrQyOeiMrgEms8OlfjAeQ= ; X-YMail-OSG: yDCONgUVM1lp4TdBqZqnijbIoC8KOSmt.VgZed.36VNDLor7Sbg_YOEOl3Hx51H23KpM9xLrtjGhgDFHq54JbNFlmZQnYU9qnxDGNNnE8Ststfu6Gmnx8H7EuC76jOrUu7Z4pbCrDVGHplo- Received: from [24.54.196.198] by web31810.mail.mud.yahoo.com via HTTP; Sat, 28 Oct 2006 07:59:09 PDT Date: Sat, 28 Oct 2006 07:59:09 -0700 (PDT) From: Richard Broersma Jr Subject: Re: Case Preservation disregarding case sensitivity? To: beau hargis , pgsql-sql@postgresql.org In-Reply-To: <200610271623.37525.beauh@bluefrogmobile.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Message-ID: <879704.84815.qm@web31810.mail.mud.yahoo.com> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=2.71 tagged_above=0 required=5 tests=AWL, DNS_FROM_RFC_ABUSE, DNS_FROM_RFC_POST, DNS_FROM_RFC_WHOIS X-Spam-Level: ** X-Archive-Number: 200610/230 X-Sequence-Number: 26619 > Again, I am looking for a way (magic, patches, whiskey, etc) that will give me > case-preservation with EITHER case-sensitivity OR case-insensitivity, but not > both as I am seeing. > > Thanks in advance. I am hoping to find a solution to this so I can actually > convert one of our databases to use Postgres. And I can say that little > issues like this are precisely why Postgres was never used in this > organization before, even though several of the other database developers > like the features, stability and performance of Postgres. Here is an explination from the postgresql manual: http://www.postgresql.org/docs/8.1/interactive/sql-syntax.html#SQL-SYNTAX-IDENTIFIERS ... Quoting an identifier also makes it case-sensitive, whereas unquoted names are always folded to lower case. For example, the identifiers FOO, foo, and "foo" are considered the same by PostgreSQL, but "Foo" and "FOO" are different from these three and each other. (The folding of unquoted names to lower case in PostgreSQL is incompatible with the SQL standard, which says that unquoted names should be folded to upper case. Thus, foo should be equivalent to "FOO" not "foo" according to the standard. If you want to write portable applications you are advised to always quote a particular name or never quote it.) ... Regards, Richard Broersma Jr.