From: Jeff Davis <pgsql@j-davis.com>
To: Peter Eisentraut <peter@eisentraut.org>
To: florian.murat.koch@gmail.com
To: pgsql-docs@lists.postgresql.org
Subject: Re: Explanations not clear
Date: Mon, 13 May 2024 12:10:25 -0700
Message-ID: <20d80bfbbec3874d430691fec37465fb7c4cb277.camel@j-davis.com> (raw)
In-Reply-To: <dbdfcb5f-282c-4426-b67e-56f4d1588a36@eisentraut.org>
References: <171501838010.704.2474442958031349608@wrigleys.postgresql.org>
<dbdfcb5f-282c-4426-b67e-56f4d1588a36@eisentraut.org>
On Wed, 2024-05-08 at 08:52 +0200, Peter Eisentraut wrote:
> > I created a collation specifying the ks-level3 setting and with
> > deterministic set to false. But when I compare "a_b" to "a-b" with
> > this
> > collation I get false. According to the table 24.1 it should yield
> > true.
> > Only after adding ka-shifted this comparison becomes true. The
> > interactions
> > of the different options are not very clear.
>
> I think table 24.1 is somewhat incorrect in the sense that
> punctuation
> is only level 4 if you use ka-shifted, otherwise it's level 1. This
> should perhaps be clarified.
One option is to just include 3 levels (plus "identic") in the table,
and then later document that ka-shifted creates a fourth level and
moves punctuation character differences into that level. That explains
the mechanism but detracts from the examples.
Another option is to say that all the examples in the table are using
ka-shifted for illustration purposes. I like this option, but it's a
bit awkward because it refers to something that hasn't been explained
yet. It's also only relevant for the 'x-y' = 'x_y' example, which might
be slightly confusing.
Thoughts?
Regards,
Jeff Davis
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-docs@postgresql.org
Cc: pgsql@j-davis.com, peter@eisentraut.org, florian.murat.koch@gmail.com, pgsql-docs@lists.postgresql.org
Subject: Re: Explanations not clear
In-Reply-To: <20d80bfbbec3874d430691fec37465fb7c4cb277.camel@j-davis.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
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