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-06 14:12:59
Message-ID: 484945EB.3010404@lelarge.info
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgadmin-support

Zach Conrad a écrit :
> 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?
>

OK, it seems my bugfix was wrong. And I suppose the one on schema
restriction is also wrong.

My patch is more user friendly (you don't have to know the name of
pg_database's columns), but it allows less stuff (you can just give
databases' names, you won't be able to filter on columns other than
datname). It seems a regression to me, sorry about this.

Dave, what do you think I should do ? remove the patch ?

Regards.

--
Guillaume.
http://www.postgresqlfr.org
http://dalibo.com

In response to

Responses

Browse pgadmin-support by date

  From Date Subject
Next Message Dave Page 2008-06-06 14:14:48 Re: 1.8.4 bug DB Restriction field
Previous Message Dave Page 2008-06-06 13:43:36 Re: HELP