Re: 1.8.4 bug DB Restriction field
От | Dave Page |
---|---|
Тема | Re: 1.8.4 bug DB Restriction field |
Дата | |
Msg-id | 937d27e10806060714x211d0cddoc2462f9a5828c138@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: 1.8.4 bug DB Restriction field (Guillaume Lelarge <guillaume@lelarge.info>) |
Ответы |
Re: 1.8.4 bug DB Restriction field
|
Список | pgadmin-support |
On Fri, Jun 6, 2008 at 3:12 PM, Guillaume Lelarge <guillaume@lelarge.info> wrote: > 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 ? Just remove the NOT? -- Dave Page EnterpriseDB UK: http://www.enterprisedb.com
В списке pgadmin-support по дате отправления: