Skip site navigation (1) Skip section navigation (2)

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: (view raw, whole thread or download thread mbox)
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;
(0 rows)


			regards, tom lane


pgsql-hackers by date

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

Privacy Policy | About PostgreSQL
Copyright © 1996-2018 The PostgreSQL Global Development Group