| From: | Bruno Wolff III <bruno(at)wolff(dot)to> |
|---|---|
| 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-09 17:09:00 |
| Message-ID: | 20070109170900.GA19523@wolff.to |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-novice |
On Mon, Jan 08, 2007 at 16:38:57 -0600,
brian stapel <brians_224(at)hotmail(dot)com> 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. In postgres, unquoted column and table names are converted to lower case.
In general, the advice is to either never quote names or always quote them.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mathieu Peltier | 2007-01-09 19:36:39 | Are postgresql 8.2.1 RPMs signed? |
| Previous Message | Sean Davis | 2007-01-09 13:37:08 | Re: Keeping a Backup database in sync with the primary |