From: | Stephan Szabo <sszabo(at)megazone23(dot)bigpanda(dot)com> |
---|---|
To: | "DUDLEY,DONALD (HP-Boise,ex1)" <donald(dot)dudley(at)hp(dot)com> |
Cc: | "'pgsql-sql(at)postgresql(dot)org'" <pgsql-sql(at)postgresql(dot)org> |
Subject: | Re: SQL Reserved words |
Date: | 2003-04-23 18:11:25 |
Message-ID: | 20030423110949.V86759-100000@megazone23.bigpanda.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
On Tue, 22 Apr 2003, DUDLEY,DONALD (HP-Boise,ex1) wrote:
> I am importing a database from Informix (SE 7.25) on HP-UX 11i to postgres
> 7.3.2 on RH 8 Linux.
> In running the "CREATE TABLE" scripts while building the new database, pgSQL
> seems to be choking on several of the column names.
> When I looked in the appendix B1 of the Users Manual, I see that some of the
> column names are reserved words, either by pgSQL or by ANSI SQL.
> Some of the column names are: 'desc' (for 'description', collides with
> keyword for 'DESCENDING'), and 'group' (used in 'GROUP BY' clause).
> I'd like not to have to alter the many queries used in scripts and programs
> to change 'desc' to descr, and group to grp, for example.
> Is there a way to tell pgSQL that you're referencing a column name and not a
> reserved word? Informix handled them ok...
You can use double quotes around the names (in all cases where you refer
to it) to use it as an identifier, but that doesn't help if you don't want
to change the queries.
From | Date | Subject | |
---|---|---|---|
Next Message | Josh Berkus | 2003-04-23 18:20:56 | Re: Why is seq search preferred here by planner? |
Previous Message | Richard Huxton | 2003-04-23 17:55:36 | Re: OUTER JOIN |