From: | "Thomas Sondag" <thomas(dot)sondag(at)gmail(dot)com> |
---|---|
To: | "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk> |
Cc: | pgadmin-support(at)postgresql(dot)org |
Subject: | Re: Proposed Patchs |
Date: | 2006-05-30 13:14:45 |
Message-ID: | 2354aa530605300614q310a4e84q12fa22b740b2750@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-support |
2006/5/30, Dave Page <dpage(at)vale-housing(dot)co(dot)uk>:
>
>
> > -----Original Message-----
> > From: Thomas Sondag [mailto:thomas(dot)sondag(at)gmail(dot)com]
> > Sent: 30 May 2006 13:42
> > To: Dave Page
> > Cc: pgadmin-support(at)postgresql(dot)org
> > Subject: Re: [pgadmin-support] Proposed Patchs
> >
> > I'm not sure this is the better way, because most of the time objects
> > are owned by the current user, so showing only group by default can be
> > a bit confusing.
>
> There's no reason we cannot use groups + current user. I do think it
> would be more confusing to have the behaviour work in precisely the
> opposite way to the privileges.
>
I'm agree, I wasn't see things that way, but that's different to the
current behaviour.
> > If you want to see the result with the "Show group ..." option try
> > the folowing patch . the main idea for AddRoles function was to remove
> > one sql query.
> >
> > I test this patch only with postgresql 8.1 and it stop
> > segfaulting now :)
>
> Think you forgot the patch :-(
>
I hope you'll get it this time.
Thomas
Attachment | Content-Type | Size |
---|---|---|
diff.txt | text/plain | 16.0 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Eric E | 2006-05-30 21:40:10 | Linking issues building pgAdmin3 v1.4.2 on Suse 10.0 |
Previous Message | Dave Page | 2006-05-30 12:57:57 | Re: Proposed Patchs |