Thread: Beta 2 issues

<font face="Helvetica, Arial, sans-serif">Hi<br /><br /> This is not really a beta 2 issue as it has existed for a
whilebut I thought I might as well raise it now.<br /><br /> In Server properties -> DB restriction there appears to
aconflict between the restriction in the UI and what the SQL actually wants. The sql wants anything that can go in an
INclause (I think?) that is then tested against datname</font><font face="Helvetica, Arial, sans-serif"> - I'm not sure
aboutthe UI - I think there are two paths but at least one path wants </font><font face="Helvetica, Arial, sans-serif">
</font><i>datnameIN (some list)</i> which produces invalid SQL.<br /><br /> To get around it you have to :- <br
/><ol><li>Serverproperties -> DB restriction put in the invalid <i>datname IN (some list)</i><li>let PgAdmin
connect<li>clearthe invalid DB restriction (get the note about server settings...)<li>Disconnect<li>Server properties
->DB restriction put in correct restriction e.g. 'test_db'</ol><br /> Cheers<br /><br /> Kieran<br /><br /> 

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