This would cost an extra query for every query, but you could let the DB
manage it with:
select quote_ident('user');
Just pile on all of the identifiers into a list and use the results for
the real query. This way it'll work across all versions of Postgresql
as well as future ones without any changes required to the 'keylist'.
On Tue, 2002-08-13 at 07:57, Dave Page wrote:
>
>
> > -----Original Message-----
> > From: Johan Mjönes [mailto:johan.mjones@agent25.se]
> > Sent: 13 August 2002 13:02
> > To: pgadmin-support@postgresql.org
> > Subject: [pgadmin-support] Problems viewing a table called
> > "user" in pgAdmin 1.3.6
> >
> >
> > Hello,
> >
> > We're having problems with the new dev version av pgAdmin II,
> > since it can't properly display one of our tables called
> > "user" (pgAdmin II 1.2 had no problem neither creating nor
> > viewing it). When the properties are loading, the parser says
> > 'parse error at or near "user"' (did someone forget to quote? ;)
> >
>
> Hi,
>
> I would guess that 'user' is a keyword that the parser doesn't like. 1.2.0 used to blindly quote everything which
manypeople objected to. 1.3.60 only quotes identifiers with characters that aren't [0-9] [a-z] or _. I will need to
lookat checking a list of reserved words as well. In the meantime, you could manually type:
>
> select * from "user"
>
> In the SQL window.
>
> Regards, Dave.
>
> ---------------------------(end of broadcast)---------------------------
> TIP 3: if posting/reading through Usenet, please send an appropriate
> subscribe-nomail command to majordomo@postgresql.org so that your
> message can get through to the mailing list cleanly
>
