Tom Lane writes:
> Probably. Peter has a script that generates that table directly from
> gram.y, and I assume he'll run it sometime before 7.2 release...
After beta has started.
--
Peter Eisentraut [EMAIL PROTECTED] http://funkturm.homeip.net/~peter
---(end of b
Lee Kindness <[EMAIL PROTECTED]> writes:
> Tom Lane writes:
>>> There is an up-to-date list of keywords in the documentation:
>>>
>http://www.ca.postgresql.org/users-lounge/docs/7.1/postgres/sql-keywords-appendix.html
> Thanks for the info. Would I be right in saying that the status of
> time (u
Tom Lane writes:
> There is an up-to-date list of keywords in the documentation:
>
>http://www.ca.postgresql.org/users-lounge/docs/7.1/postgres/sql-keywords-appendix.html
Thanks for the info. Would I be right in saying that the status of
time (unreserved for PostgreSQL) for 7.2 needs to be ch
Lee Kindness <[EMAIL PROTECTED]> writes:
> Obviously a new column name will have to be used, however is there a
> definitive list of keywords to avoid so such an occurance wouldn't
> happen in a production system?
There is an up-to-date list of keywords in the documentation:
http://www.ca.postgre
In moving from 7.1.3 to 7.2devel (for bug fixes) we've encountered a
problem with a, previously valid, column name: time. In 7.1.3 the
following worked:
CREATE TABLE test(time INTEGER);
while in 7.2devel it results in a parse error:
ERROR: parser: parse error at or near "time"
Looking at
