Re: Poll: are people okay with function/operator table redesign?

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Isaac Morland <isaac(dot)morland(at)gmail(dot)com>, PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Poll: are people okay with function/operator table redesign?
Date: 2020-04-13 20:31:51
Message-ID: CAKFQuwYZLn3+-aBi3HBKywMmjtyiSUZqnwzkJ-aYsZ0ORyS8gA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Apr 13, 2020 at 11:27 AM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> Isaac Morland <isaac(dot)morland(at)gmail(dot)com> writes:
>
> > - I think there should be much more distinctive lines between the
> different
> > functions. As it is the fact that the table is groups of 3 lines doesn’t
> > jump out at the eye.
>
> I don't know any easy way to do that. We do already have the grouping
> visible in the first column...
>

Can we lightly background color every other rowgroup (i.e., "greenbar")?

I don't think having a separate Result column helps. The additional
horizontal whitespace distances all relevant context information (at least
on a wide monitor). Having the example rows mirror the Signature row seems
like an easier to consume choice.

e.g.,

enum_first(null::rainbow) → red

date '2001-09-28' + 7 → 2001-10-05

Its also removes the left alignment in a fixed width column which draws
unwanted visual attention.

David J.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2020-04-13 20:33:52 Re: Poll: are people okay with function/operator table redesign?
Previous Message Tom Lane 2020-04-13 20:29:07 Re: Poll: are people okay with function/operator table redesign?