pg.ddx.io  pgsql-docs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
non-string or non-string
4+ messages / 4 participants
[nested] [flat]

* non-string or non-string
@ 2020-05-17 21:11 PG Doc comments form <noreply@postgresql.org>
  2020-05-17 22:31 ` Re: non-string or non-string Alvaro Herrera <alvherre@2ndquadrant.com>
  2020-05-17 22:33 ` Re: non-string or non-string Tom Lane <tgl@sss.pgh.pa.us>
  0 siblings, 2 replies; 4+ messages in thread

From: PG Doc comments form @ 2020-05-17 21:11 UTC (permalink / raw)
  To: pgsql-docs@lists.postgresql.org; +Cc: b@janin.com

The following documentation comment has been logged on the website:

Page: https://www.postgresql.org/docs/11/functions-string.html
Description:

The second line in "Table 9.8. SQL String Functions and Operators" uses
"non-string or non-string" as part of the example. I assume one of these
should be "string".


^ permalink  raw  reply  [nested|flat] 4+ messages in thread

* Re: non-string or non-string
  2020-05-17 21:11 non-string or non-string PG Doc comments form <noreply@postgresql.org>
@ 2020-05-17 22:31 ` Alvaro Herrera <alvherre@2ndquadrant.com>
  2020-05-17 23:04   ` Re: non-string or non-string Bertrand Janin <b@janin.com>
  1 sibling, 1 reply; 4+ messages in thread

From: Alvaro Herrera @ 2020-05-17 22:31 UTC (permalink / raw)
  To: b@janin.com; pgsql-docs@lists.postgresql.org

On 2020-May-17, PG Doc comments form wrote:

> The following documentation comment has been logged on the website:
> 
> Page: https://www.postgresql.org/docs/11/functions-string.html
> Description:
> 
> The second line in "Table 9.8. SQL String Functions and Operators" uses
> "non-string or non-string" as part of the example. I assume one of these
> should be "string".

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

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

-- 
Álvaro Herrera                https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services





^ permalink  raw  reply  [nested|flat] 4+ messages in thread

* Re: non-string or non-string
  2020-05-17 21:11 non-string or non-string PG Doc comments form <noreply@postgresql.org>
  2020-05-17 22:31 ` Re: non-string or non-string Alvaro Herrera <alvherre@2ndquadrant.com>
@ 2020-05-17 23:04   ` Bertrand Janin <b@janin.com>
  0 siblings, 0 replies; 4+ messages in thread

From: Bertrand Janin @ 2020-05-17 23:04 UTC (permalink / raw)
  To: pgsql-docs@lists.postgresql.org; +Cc: Alvaro Herrera <alvherre@2ndquadrant.com>

> 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





^ permalink  raw  reply  [nested|flat] 4+ messages in thread

* Re: non-string or non-string
  2020-05-17 21:11 non-string or non-string PG Doc comments form <noreply@postgresql.org>
@ 2020-05-17 22:33 ` Tom Lane <tgl@sss.pgh.pa.us>
  1 sibling, 0 replies; 4+ messages in thread

From: Tom Lane @ 2020-05-17 22:33 UTC (permalink / raw)
  To: b@janin.com; +Cc: pgsql-docs@lists.postgresql.org

PG Doc comments form <noreply@postgresql.org> writes:
> The second line in "Table 9.8. SQL String Functions and Operators" uses
> "non-string or non-string" as part of the example. I assume one of these
> should be "string".

It might look that way depending on how wide your browser window is...
but the way it's supposed to be read is

	string || non-string
	        or
	non-string || string

The devel version of the docs forces the two cases to be on separate
lines, which hopefully will stem the confusion.

			regards, tom lane





^ permalink  raw  reply  [nested|flat] 4+ messages in thread


end of thread, other threads:[~2020-05-17 23:04 UTC | newest]

Thread overview: 4+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2020-05-17 21:11 non-string or non-string PG Doc comments form <noreply@postgresql.org>
2020-05-17 22:31 ` Alvaro Herrera <alvherre@2ndquadrant.com>
2020-05-17 23:04   ` Bertrand Janin <b@janin.com>
2020-05-17 22:33 ` Tom Lane <tgl@sss.pgh.pa.us>

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox