Re: New "function tables" in V13 documentation

From: Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>
To: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, 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 20:48:20
Message-ID: 34aff021-acbc-c2f6-d572-0d3af6fa9169@aklaver.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 11/13/20 11:30 AM, David G. Johnston wrote:
> On Fri, Nov 13, 2020 at 12:20 PM Kevin Brannen <KBrannen(at)efji(dot)com
> <mailto: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.

Which is an indication that for changes of this scope it would be
prudent to create a mock up and have end users see and comment on before
rolling them out.

>
> 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.
>

--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Maksim Fomin 2020-11-13 20:56:38 Restoring database from false update
Previous Message Edson Richter 2020-11-13 20:46:43 RE: Range partitioning and overlap