Parser breakage: "timestamp" has become a reserved word

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: pgsql-hackers(at)postgreSQL(dot)org
Subject: Parser breakage: "timestamp" has become a reserved word
Date: 1998-10-11 22:13:42
Message-ID: 28160.908144022@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

The current (as of 8 Oct) parser will not let me select a field named
"timestamp" from a table. It worked just fine a week or so ago.
I presume the problem is that timestamp is also a data type name.

Is this a bug, or can I expect that addition of data types may break
tables that used to work?

tree=> \d stringdataseriesclass

Table = stringdataseriesclass
+----------------------------------+----------------------------------+-------+
| Field | Type | Length|
+----------------------------------+----------------------------------+-------+
| label | text not null | var |
| timestamp | datetime not null | 8 |
| value | text not null | var |
+----------------------------------+----------------------------------+-------+

tree=> select timestamp from stringdataseriesclass;
ERROR: parser: parse error at or near "from"

tree=> select label from stringdataseriesclass;
label
-----
(0 rows)

tree=>

regards, tom lane

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 1998-10-11 22:13:52 Re: [HACKERS] Linux and -export-dynamic
Previous Message Bruce Momjian 1998-10-11 21:31:22 Linux and -export-dynamic