Re: 1.8.4 bug DB Restriction field

From: Guillaume Lelarge <guillaume(at)lelarge(dot)info>
To: Zach Conrad <zach(dot)conrad(at)digitecinc(dot)com>
Cc: pgadmin-support(at)postgresql(dot)org
Subject: Re: 1.8.4 bug DB Restriction field
Date: 2008-06-05 20:31:55
Message-ID: 48484D3B.7040400@lelarge.info
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgadmin-support

Zach Conrad a écrit :
> 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')
>
> 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_database db LEFT OUTER JOIN pg_tablespace ta ON db.dattablespace=ta.OID WHERE datname NOT IN (datname='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

In response to

Responses

Browse pgadmin-support by date

  From Date Subject
Next Message Zach Conrad 2008-06-05 20:43:18 Re: 1.8.4 bug DB Restriction field
Previous Message Zach Conrad 2008-06-05 19:43:44 1.8.4 bug DB Restriction field