Re: Problems viewing a table called "user" inpgAdmin 1.3.6

From: "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk>
To: "Rod Taylor" <rbt(at)zort(dot)ca>
Cc: Johan Mjönes <johan(dot)mjones(at)agent25(dot)se>, <pgadmin-support(at)postgresql(dot)org>
Subject: Re: Problems viewing a table called "user" inpgAdmin 1.3.6
Date: 2002-08-13 12:07:33
Message-ID: D85C66DA59BA044EB96AB9683819CF61138072@dogbert.vale-housing.co.uk
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgadmin-support

> -----Original Message-----
> From: Rod Taylor [mailto:rbt(at)zort(dot)ca]
> Sent: 13 August 2002 13:03
> To: Dave Page
> Cc: Johan Mjönes; pgadmin-support(at)postgresql(dot)org
> Subject: Re: [pgadmin-support] Problems viewing a table
> called "user" inpgAdmin 1.3.6
>
>
> 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'.

Yeah, the problem is though that pgAdmin's own internal quote_ident (fmtID) is called in lterally hundreds of places. What would be handier would be a function that returns an array of keywords - that could be queried at logon and used to populate a dictionary.

Regards, Dave.

Browse pgadmin-support by date

  From Date Subject
Next Message Armbrust, Daniel C. 2002-08-13 21:21:52 download broken
Previous Message Rod Taylor 2002-08-13 12:02:55 Re: Problems viewing a table called "user" in