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 8 of 12 Topic 2037 of 2158
Post > Topic >>

Re: 1.8.4 bug DB Restriction field

by zach.conrad@[EMAIL PROTECTED] (Zach Conrad) Jun 6, 2008 at 09:47 AM

Dave, Guillaume,

What I have grown accustomed to has been the ability to limit the
connection to a particular db or db's instead of seeing all the databases
I don't need to work with on that connection. I would be in favor of
dropping the NOT. 

Perhaps this is an UI issue where the DB Restriction field is trying to do
too much. Maybe there could be two fields:
1. Listed Databases (comma separated list of database names)
2. Filters (uses namespaces for filtering)

I could see Filters as a separate tab (Properties | Filters | SQL) for the
connection properties, similar to how a table properties tabs work,
specifically the Column tab where you could have the Add button add a new
filter. If someone really wants that much control over the connection,
they can have it. Generally speaking, the Listed Databases field is a
Filter, but less confusing to general users.

Sincerely,

Zach Conrad

----- Original Message -----
From: "Dave Page" <dpage@[EMAIL PROTECTED]
>
To: "Guillaume Lelarge" <guillaume@[EMAIL PROTECTED]
>
Cc: "Zach Conrad" <zach.conrad@[EMAIL PROTECTED]
>,
pgadmin-sup****t@[EMAIL PROTECTED]
 Friday, June 6, 2008 9:26:57 AM GMT -06:00 US/Canada Central
Subject: Re: [pgadmin-sup****t] 1.8.4 bug DB Restriction field

On Fri, Jun 6, 2008 at 3:22 PM, Guillaume Lelarge
<guillaume@[EMAIL PROTECTED]
> wrote:

>>> Dave, what do you think I should do ? remove the patch ?
>>
>> Just remove the NOT?
>>
>
> I can do this. But, for example, if someone was using this filter field
to
> get out template databases, removing the NOT won't fix this.

Hmm, good point. The original intent behind the feature was for
teaching environments in which there may be one database for each
student, so the students could limit their list to just their own
database without seeing all their schoolmates as well. I think that's
probably the most im****tant case to fix (which removing the NOT should
do), as those people will likely have *lot's* of clutter otherwise.

Alternatively, you could make the NOT optional with a checkbox.

-- 
Dave Page
EnterpriseDB UK: http://www.enterprisedb.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
 




 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 17:55:04 CST 2008.