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
Re=
striction field
2. Most people know which databases they want to connect to. Wouldn't it
ma=
ke
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]
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 =C3=A9crit :
> DB Restriction field borks on datname IN ('blah') or datname=3D'blah'
wit=
h the error: "ERROR: operator does not exist: name <> boolean LINE 5:
WHE=
RE datname NOT IN (datname=3D'blah')
>=20
> 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_ge=
t_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.O=
ID WHERE datname NOT IN (datname=3D'blah')
>=20
The DB Restriction field should not contain : datname IN ('blah')
It should contain : 'blah'
or : 'foo','bar'
Regards.
--=20
Guillaume.
http://www.postgresqlfr.org
http://dalibo.com
--=20
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
|
