Message-Id: <5.2.1.1.0.20061027214608.04129070@pop6.sympatico.ca>
Date: Fri, 27 Oct 2006 21:50:22 -0400
To: pgsql-sql@postgresql.org
From: Frank Bax <fbax@sympatico.ca>
Subject: Re: Case Preservation disregarding case sensitivity?
In-Reply-To: <200610271623.37525.beauh@bluefrogmobile.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed

At 07:23 PM 10/27/06, beau hargis wrote:
>I am aware of the double-quote 'feature' which indicates that an element
>should be treated in a case-sensitive way. This as been the 'answer' to every
>question of this sort. This 'feature' does not solve the problem and
>introduces other problems.


If you use double-quotes when creating the table, you need to use 
double-quotes EVERY time you access those elements.  Neither of your two 
examples (that produced errors) have double quotes.


>ALTER TABLE user_profile ADD CONSTRAINT fk_uproftype  FOREIGN KEY
>(userProfileTypeId) REFERENCES user_profile_type (userProfileTypeId);
>
>ERROR:  column "userprofiletypeid" referenced in foreign key constraint does
>not exist


>insert into user_profile_type
>(userProfileTypeId,userProfileType) VALUES(1,'ABNORMAL');
>
>ERROR: column "userprofiletypeid" of relation "user_profile_type" does not
>exist


The second query should be:

insert into user_profile_type ("userProfileTypeId","userProfileType") 
VALUES(1,'ABNORMAL');