| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Lee Kindness <lkindness(at)csl(dot)co(dot)uk> |
| Cc: | pgsql-hackers(at)postgresql(dot)org, Thomas Lockhart <lockhart(at)fourpalms(dot)org>, Mark Aves <maves(at)csl(dot)co(dot)uk> |
| Subject: | Re: Column names - time |
| Date: | 2001-10-16 21:19:18 |
| Message-ID: | 22625.1003267158@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Lee Kindness <lkindness(at)csl(dot)co(dot)uk> 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.postgresql.org/users-lounge/docs/7.1/postgres/sql-keywords-appendix.html
As for predicting what keywords might become reserved in future PG
releases, my crystal ball is down at the moment ... but words that are
reserved in SQL99 would be good things to avoid.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bill Studenmund | 2001-10-16 22:09:52 | Re: schema support, was Package support for Postgres |
| Previous Message | Marc G. Fournier | 2001-10-16 21:10:58 | Re: delayed mail? |