Re: 1.8.4 bug DB Restriction field

I think there is a problem with the syntax -- highlighted below<br /><br />It seems that<br /><div style="margin-left:
40px;"> datnameNOT in (datname='blah')<br /><br /></div>should just be<br /><div style="margin-left: 40px;">  datname
NOTin ('blah')<br /><br /><br /></div><div style="margin-left: 40px;">SELECT db.oid, datname, db.dattablespace AS
spcoid,spcname, datallowconn, datconfig, datacl, pg_encoding_to_char(encoding) AS serverencoding,
pg_get_userbyid(datdba)AS datowner,has_database_privileg<div class="ArwC7c ckChnd" id="1exj">e(db.oid, 'CREATE') as
cancreate,current_setting('default_tablespace') AS default_tablespace FROM pg_database db LEFT OUTER JOIN pg_tablespace
taON db.dattablespace=ta.OID WHERE datname NOT IN (<b>datname='blah'</b>)</div></div><br /><div class="gmail_quote">On
Thu,Jun 5, 2008 at 3:43 PM, Zach Conrad <<a
href="mailto:zach.conrad@digitecinc.com">zach.conrad@digitecinc.com</a>>wrote:<br /><blockquote class="gmail_quote"
style="border-left:1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Thank you for your
quickresponse.<br /><br /> There are a few things this brings up:<br /><br /> 1. The pgAdmin help file states the use
ofdatname IN ('blah') in the DB Restriction field<br /> 2. Most people know which databases they want to connect to.
Wouldn'tit make<br />   more sense to use datename IN (...) rather than NOT IN?<br /><br /> Thank you all for creating
agreat application!<br /><br /> Sincerely,<br /><br /> Zach Conrad<br /><br /> ----- Original Message -----<br /> From:
"GuillaumeLelarge" <<a href="mailto:guillaume@lelarge.info">guillaume@lelarge.info</a>><br /> To: "Zach Conrad"
<<ahref="mailto:zach.conrad@digitecinc.com">zach.conrad@digitecinc.com</a>><br /> Cc: <a
href="mailto:pgadmin-support@postgresql.org">pgadmin-support@postgresql.org</a><br/> Sent: Thursday, June 5, 2008
3:31:55PM GMT -06:00 US/Canada Central<br /> Subject: Re: [pgadmin-support] 1.8.4 bug DB Restriction field<br /><br />
ZachConrad a écrit :<br /> > DB Restriction field borks on datname IN ('blah') or datname='blah' with the error:
"ERROR: operator does not exist: name <> boolean LINE 5:  WHERE datname NOT IN (datname='blah')<br /> ><br />
>Here's the full query from the logs being sent from pgAdmin:<br /> > SELECT db.oid, datname, db.dattablespace AS
spcoid,spcname, datallowconn, datconfig, datacl, pg_encoding_to_char(encoding) AS serverencoding,
pg_get_userbyid(datdba)AS datowner,has_database_privilege(db.oid, 'CREATE') as cancreate,
current_setting('default_tablespace')AS default_tablespace FROM pg_database db LEFT OUTER JOIN pg_tablespace ta ON
db.dattablespace=ta.OIDWHERE datname NOT IN (datname='blah')<br /> ><br /><br /> The DB Restriction field should not
contain: datname IN ('blah')<br /><br /> It should contain : 'blah'<br /> or : 'foo','bar'<br /><br /> Regards.<br
/><br/><br /> --<br /> Guillaume.<br />  <a href="http://www.postgresqlfr.org"
target="_blank">http://www.postgresqlfr.org</a><br/>  <a href="http://dalibo.com"
target="_blank">http://dalibo.com</a><br/><font color="#888888"><br /> --<br /> Sent via pgadmin-support mailing list
(<ahref="mailto:pgadmin-support@postgresql.org">pgadmin-support@postgresql.org</a>)<br /> To make changes to your
subscription:<br/><a href="http://www.postgresql.org/mailpref/pgadmin-support"
target="_blank">http://www.postgresql.org/mailpref/pgadmin-support</a><br/></font></blockquote></div><br />