Talk About Network

Google


Register and Login
Nick
Password
Register create new account Sign up is FREE and you can post replies, new topics, bookmark posts and more!
Recover lost password


Data Bases > Pgsql Interfaces Pgadmin Support > Re: 1.8.4 bug D...
Latest [ Topics | Posts ] Archive Post A New Topic Post a Reply
<< Topic < Post Post 12 of 12 Topic 2037 of 2158
Post > Topic >>

Re: 1.8.4 bug DB Restriction field

by mshapiro51@[EMAIL PROTECTED] ("Michael Shapiro") Jun 5, 2008 at 04:46 PM

------=_Part_6850_4264095.1212702402375
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

I think there is a problem with the syntax -- highlighted below

It seems that
 datname NOT in (datname=3D'blah')

should just be
 datname NOT in ('blah')


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=3Dta.OID WHERE datname NOT IN (*datname=3D'blah'*)

On Thu, Jun 5, 2008 at 3:43 PM, Zach Conrad <zach.conrad@[EMAIL PROTECTED]
>
wrote:

> Thank you for your quick response.
>
> There are a few things this brings up:
>
> 1. The pgAdmin help file states the use of datname IN ('blah') in the DB
> Restriction field
> 2. Most people know which databases they want to connect to. Wouldn't it
> make
>   more sense to use datename IN (...) rather than NOT IN?
>
> Thank you all for creating a great application!
>
> Sincerely,
>
> Zach Conrad
>
> ----- Original Message -----
> From: "Guillaume Lelarge" <guillaume@[EMAIL PROTECTED]
>
> To: "Zach Conrad" <zach.conrad@[EMAIL PROTECTED]
>
> Cc: pgadmin-sup****t@[EMAIL PROTECTED]
> Sent: Thursday, June 5, 2008 3:31:55 PM GMT -06:00 US/Canada Central
> Subject: Re: [pgadmin-sup****t] 1.8.4 bug DB Restriction field
>
> Zach Conrad a =E9crit :
> > DB Restriction field borks on datname IN ('blah') or datname=3D'blah'
w=
ith
> the error: "ERROR:  operator does not exist: name <> boolean LINE 5: 
WHE=
RE
> datname NOT IN (datname=3D'blah')
> >
> > Here's the full query from the logs being sent from pgAdmin:
> > 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_datab=
ase
> db LEFT OUTER JOIN pg_tablespace ta ON db.dattablespace=3Dta.OID WHERE
da=
tname
> NOT IN (datname=3D'blah')
> >
>
> The DB Restriction field should not contain : datname IN ('blah')
>
> It should contain : 'blah'
> or : 'foo','bar'
>
> Regards.
>
>
> --
> Guillaume.
>  http://www.postgresqlfr.org
>  http://dalibo.com
>
> --
> Sent via pgadmin-sup****t mailing list (pgadmin-sup****t@[EMAIL PROTECTED]
)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgadmin-sup****t
>

------=_Part_6850_4264095.1212702402375
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

I think there is a problem with the syntax -- highlighted below<br><br>It
s=
eems that<br><div style=3D"margin-left: 40px;">&nbsp;datname NOT in
(datnam=
e=3D&#39;blah&#39;)<br><br></div>should just be<br><div
style=3D"margin-lef=
t: 40px;">
&nbsp;datname NOT in (&#39;blah&#39;)<br><br><br></div><div
style=3D"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 id=3D"1exj" class=3D"ArwC7c
ckChnd">e(db=
..oid, &#39;CREATE&#39;) as cancreate,
current_setting(&#39;default_tablespa=
ce&#39;)
AS default_tablespace FROM pg_database db LEFT OUTER JOIN pg_tablespace
ta ON db.dattablespace=3Dta.OID WHERE datname NOT IN
(<b>datname=3D&#39;bla=
h&#39;</b>)</div></div><br><div class=3D"gmail_quote">On Thu, Jun 5, 2008
a=
t 3:43 PM, Zach Conrad &lt;<a
href=3D"mailto:zach.conrad@[EMAIL PROTECTED]
">za=
ch.conrad@[EMAIL PROTECTED]
>&gt; wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"border-left: 1px solid rgb(204,
=
204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Thank you for
you=
r quick response.<br>
<br>
There are a few things this brings up:<br>
<br>
1. The pgAdmin help file states the use of datname IN (&#39;blah&#39;) in
t=
he DB Restriction field<br>
2. Most people know which databases they want to connect to. Wouldn&#39;t
i=
t make<br>
 &nbsp; more sense to use datename IN (...) rather than NOT IN?<br>
<br>
Thank you all for creating a great application!<br>
<br>
Sincerely,<br>
<br>
Zach Conrad<br>
<br>
----- Original Message -----<br>
From: &quot;Guillaume Lelarge&quot; &lt;<a
href=3D"mailto:guillaume@[EMAIL PROTECTED]
">guillaume@[EMAIL PROTECTED]
>&gt;<br>
To: &quot;Zach Conrad&quot; &lt;<a
href=3D"mailto:zach.conrad@[EMAIL PROTECTED]
">zach.conrad@[EMAIL PROTECTED]
>&gt;<br>
Cc: <a
href=3D"mailto:pgadmin-sup****t@[EMAIL PROTECTED]
">pgadmin-sup****t@[EMAIL PROTECTED]
><br>
Sent: Thursday, June 5, 2008 3:31:55 PM GMT -06:00 US/Canada Central<br>
Subject: Re: [pgadmin-sup****t] 1.8.4 bug DB Restriction field<br>
<br>
Zach Conrad a =E9crit :<br>
&gt; DB Restriction field borks on datname IN (&#39;blah&#39;) or datname=
=3D&#39;blah&#39; with the error: &quot;ERROR: &nbsp;operator does not
exis=
t: name &lt;&gt; boolean LINE 5: &nbsp;WHERE datname NOT IN
(datname=3D&#39=
;blah&#39;)<br>

&gt;<br>
&gt; Here&#39;s the full query from the logs being sent from pgAdmin:<br>
&gt; SELECT db.oid, datname, db.dattablespace AS spcoid, spcname,
datallowc=
onn, datconfig, datacl, pg_encoding_to_char(encoding) AS serverencoding,
pg=
_get_userbyid(datdba) AS datowner,has_database_privilege(db.oid,
&#39;CREAT=
E&#39;) as cancreate, current_setting(&#39;default_tablespace&#39;) AS
defa=
ult_tablespace FROM pg_database db LEFT OUTER JOIN pg_tablespace ta ON
db.d=
attablespace=3Dta.OID WHERE datname NOT IN (datname=3D&#39;blah&#39;)<br>

&gt;<br>
<br>
The DB Restriction field should not contain : datname IN
(&#39;blah&#39;)<b=
r>
<br>
It should contain : &#39;blah&#39;<br>
or : &#39;foo&#39;,&#39;bar&#39;<br>
<br>
Regards.<br>
<br>
<br>
--<br>
Guillaume.<br>
 &nbsp;<a href=3D"http://www.postgresqlfr.org"
target=3D"_blank">http://www=
..postgresqlfr.org</a><br>
 &nbsp;<a href=3D"http://dalibo.com"
target=3D"_blank">http://dalibo.com</a=
><br>
<font color=3D"#888888"><br>
--<br>
Sent via pgadmin-sup****t mailing list (<a
href=3D"mailto:pgadmin-sup****t@[EMAIL PROTECTED]
">pgadmin-sup****t@[EMAIL PROTECTED]
>)<br>
To make changes to your subscription:<br>
<a href=3D"http://www.postgresql.org/mailpref/pgadmin-sup****t"
target=3D"_b=
lank">http://www.postgresql.org/mailpref/pgadmin-sup****t</a><br>
</font></blockquote></div><br>

------=_Part_6850_4264095.1212702402375--
 




 12 Posts in Topic:
1.8.4 bug DB Restriction field
zach.conrad@[EMAIL PROTEC  2008-06-05 14:43:44 
Re: 1.8.4 bug DB Restriction field
guillaume@[EMAIL PROTECTE  2008-06-05 22:31:55 
Re: 1.8.4 bug DB Restriction field
zach.conrad@[EMAIL PROTEC  2008-06-05 15:43:18 
Re: 1.8.4 bug DB Restriction field
guillaume@[EMAIL PROTECTE  2008-06-06 16:12:59 
Re: 1.8.4 bug DB Restriction field
dpage@[EMAIL PROTECTED]   2008-06-06 15:14:48 
Re: 1.8.4 bug DB Restriction field
guillaume@[EMAIL PROTECTE  2008-06-06 16:22:12 
Re: 1.8.4 bug DB Restriction field
dpage@[EMAIL PROTECTED]   2008-06-06 15:26:57 
Re: 1.8.4 bug DB Restriction field
zach.conrad@[EMAIL PROTEC  2008-06-06 09:47:44 
Re: 1.8.4 bug DB Restriction field
guillaume@[EMAIL PROTECTE  2008-06-11 10:06:44 
Re: 1.8.4 bug DB Restriction field
dpage@[EMAIL PROTECTED]   2008-06-11 09:10:13 
Re: 1.8.4 bug DB Restriction field
guillaume@[EMAIL PROTECTE  2008-06-12 21:02:05 
Re: 1.8.4 bug DB Restriction field
mshapiro51@[EMAIL PROTECT  2008-06-05 16:46:42 

Post A Reply:
  Go here to Signup

AddThis Feed Button


About - Advertising - Contact - Frequently Asked Questions - Privacy Policy - Terms of Use - Signup

Contact
tan12V112 Mon Dec 1 8:28:22 CST 2008.