Re: New "function tables" in V13 documentation

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: Kevin Brannen <KBrannen(at)efji(dot)com>
Cc: "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org>
Subject: Re: New "function tables" in V13 documentation
Date: 2020-11-13 19:30:50
Message-ID: CAKFQuwb7GE+0dcVkJF1iP7qqRuU2CwhpAPj6mo9H4OtbNs6Kmw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Fri, Nov 13, 2020 at 12:20 PM Kevin Brannen <KBrannen(at)efji(dot)com> wrote:

> Go to the string funcs/ops page in v13, and try to quickly find the ones
> that return an "int" (because your goal is to find the position of
> something in a string so you know the return value will have to be an
> "int").
>

That is not something I considered...I figured people would look for a name
that seems to reflect "position" or "in_string". I've never felt the need
to search based upon return type.

> Designing pages to the smallest media just frustrates those users on
> larger media (cue the many examples on the web where the left/right margins
> are so wide half of your screen is wasted instead of letting the text flow
> and resize).]
>

It is just as bad it is so wide that one has to move their head instead of
just moving their eyes. If anything our tables could probably be improved
by enforcing a maximum width to the content area.

David J.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Edson Richter 2020-11-13 20:29:22 Range partitioning and overlap
Previous Message Kevin Brannen 2020-11-13 19:20:29 RE: New "function tables" in V13 documentation