On Mon, Mar 30, 2009 at 10:07 AM, Kieran McCusker
<kieran.mccusker@kwest.info> wrote:
> Hi
>
> This is not really a beta 2 issue as it has existed for a while but I
> thought I might as well raise it now.
>
> In Server properties -> DB restriction there appears to a conflict between
> the restriction in the UI and what the SQL actually wants. The sql wants
> anything that can go in an IN clause (I think?) that is then tested against
> datname - I'm not sure about the UI - I think there are two paths but at
> least one path wants datname IN (some list) which produces invalid SQL.
>
> To get around it you have to :-
>
> Server properties -> DB restriction put in the invalid datname IN (some
> list)
> let PgAdmin connect
> clear the invalid DB restriction (get the note about server settings...)
> Disconnect
> Server properties -> DB restriction put in correct restriction e.g.
> 'test_db'
Thanks - fix committed.
--
Dave Page
EnterpriseDB UK: http://www.enterprisedb.com
