From: | Sean Davis <sdavis2(at)mail(dot)nih(dot)gov> |
---|---|
To: | brian stapel <brians_224(at)hotmail(dot)com> |
Cc: | pgsql-novice(at)postgresql(dot)org |
Subject: | Re: Column Name = column does not exist |
Date: | 2007-01-08 22:46:57 |
Message-ID: | 45A2C9E1.6010804@mail.nih.gov |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-novice |
brian stapel wrote:
> Thanks for your time.
>
> I'm in the process of trying to incorporate three Human Resource
> systems into one. Each of the three systems had a different author
> and no standards were followed - consequently the table design leaves
> a bit to be desired. One of the most critical tables has a field
> named:Last_Name (case specific). When I execute 'Select Last_Name
> from employee' the statement fails with the following message: column
> "last_name" does not exist. If I wrap the field name in quotes
> "Last_Name" for example, the query works as expected.
>
> Is this typical behavior?
>
Yes. Postgresql case-collapses unless things are quoted. The rule of
thumb is, if you quote anywhere, you probably should quote EVERYWHERE.
Sean
From | Date | Subject | |
---|---|---|---|
Next Message | Carlson, James (Jim) | 2007-01-09 12:32:16 | Keeping a Backup database in sync with the primary |
Previous Message | brian stapel | 2007-01-08 22:38:57 | Column Name = column does not exist |