Date: Sun, 17 May 2020 19:04:04 -0400
From: Bertrand Janin <b@janin.com>
To: pgsql-docs@lists.postgresql.org
Cc: Alvaro Herrera <alvherre@2ndquadrant.com>
Subject: Re: non-string or non-string
Message-ID: <20200517230404.GG44458@janin.com>
References: <158974990906.7031.8787889795019651207@wrigleys.postgresql.org>
 <20200517223128.GA8607@alvherre.pgsql>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <20200517223128.GA8607@alvherre.pgsql>
User-Agent: Mutt/1.11.4 (2019-03-13)
Precedence: bulk

> No, it's not the example but the operator description, and what it says
> is
> "string || non-string or non-string || string"
> 
> so it's trying to illustrate that there are two options:
> 
> string || non-string
> non-string || string

I see, that makes a lot more sense.

> but maybe it's not super-clear about that.  This is much clearer in the
> docs for Postgres 13, which has been heavily reformatted:
> https://www.postgresql.org/docs/devel/functions-string.html

Oh wow, that's quite the change.  I'm going to use the updated docs moving
forward, it confused me at first, after years of visually parsing the previous
format, but it's clearer once you understand the structure.

Thanks,
Bertrand