From: | David Goodenough <david(dot)goodenough(at)btconnect(dot)com> |
---|---|
To: | Karel Zak <zakkr(at)zf(dot)jcu(dot)cz> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: SELECT problem |
Date: | 2002-06-21 11:24:02 |
Message-ID: | 20020621112403.37D2D475461@postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Friday 21 June 2002 11:46, Karel Zak wrote:
> On Fri, Jun 21, 2002 at 11:38:39AM +0100, David Goodenough wrote:
> > landn=# select * from sites;
> > CUSTNAME | AREA | SITE | NAME | BUILDING | TOWN | COUNTY | POSTCODE |
> > GRIDREF | LATITUDE | LONGITUDE
> > ----------+------+------+------+----------+------+--------+----------+---
> >------+----------+----------- (0 rows)
> >
> > landn=# select area from sites;
> > ERROR: Attribute 'area' not found
> > landn=#
>
> select "AREA" from sites;
>
> Karel
Well yes that works, but why? In every book I have ever read on SQL
the column names are not in quotes, and the other DB I use regularly
(IBM DB/2) does not require the column names in quotes, and actually
does not recognise the column names if they are in quotes?
I thought SQL was supposed to be standardised these days? Or are we
in the "standards are a good thing, lets have lots" mode with conflicting
standards or incomplete standards?
David
From | Date | Subject | |
---|---|---|---|
Next Message | terry | 2002-06-21 11:46:27 | Re: [DOCS] crash problem |
Previous Message | John Gray | 2002-06-21 11:08:56 | Re: SELECT problem |