2009/11/2 Alvaro Herrera :
> Peter Eisentraut wrote:
>> As a compromise, we could keep the combined "Attributes" column but
>> replace the line breaks by commas. This would at least get rid of the
>> confusing and ugly line breaks in the common cases.
>
> That works for me.
Mmm, perhaps we were a
Peter Eisentraut wrote:
> As a compromise, we could keep the combined "Attributes" column but
> replace the line breaks by commas. This would at least get rid of the
> confusing and ugly line breaks in the common cases.
That works for me.
--
Alvaro Herrerahttp:/
On ons, 2009-10-21 at 10:28 -0300, Alvaro Herrera wrote:
> Peter Eisentraut wrote:
> > Could someone clarify why this (from PG 8.4)
> >
> > # \du
> > List of roles
> >Role name | Attributes | Member of
> > ---+-+
> > admin | Create
Alvaro Herrera writes:
> The reason it's an improvement of sorts is that there are now more
> possible attributes, and if we had kept adding columns it would have
> become wider than 80 columns.
Yeah, 8.4 has two more possible entries, and adding them as separate
columns would have guaranteed tha
Peter Eisentraut wrote:
> Could someone clarify why this (from PG 8.4)
>
> # \du
> List of roles
>Role name | Attributes | Member of
> ---+-+
> admin | Create role | {}
>: Create DB
> postgres | Superuser | {
2009/10/21 Peter Eisentraut :
> Could someone clarify why this (from PG 8.4)
>
> # \du
> List of roles
> Role name | Attributes | Member of
> ---+-+
> admin | Create role | {}
> : Create DB
> postgres | Superuser |
Could someone clarify why this (from PG 8.4)
# \du
List of roles
Role name | Attributes | Member of
---+-+
admin | Create role | {}
: Create DB
postgres | Superuser | {}
: Create role