pgsql: Revert "Rename unicode_combining_table to unicode_width_table" - Mailing list pgsql-committers

From John Naylor
Subject pgsql: Revert "Rename unicode_combining_table to unicode_width_table"
Date
Msg-id E1mJG2h-0002BD-Tn@gemulon.postgresql.org
Whole thread Raw
List pgsql-committers
Revert "Rename unicode_combining_table to unicode_width_table"

This reverts commit eb0d0d2c7300c9c5c22b35975c11265aa4becc84.

After I had committed eb0d0d2c7 and 78ab944cd, I decided to add
a sanity check for a "can't happen" scenario just to be cautious.
It turned out that it already happened in the official Unicode source
data, namely that a character can be both wide and a combining
character. This fact renders the aforementioned commits unnecessary,
so revert both of them.

Discussion: https://www.postgresql.org/message-id/CAFBsxsH5ejH4-1xaTLpSK8vWoK1m6fA1JBtTM6jmBsLfmDki1g%40mail.gmail.com

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/1563ecbc1be8b8e5c57651cf5c87f90dea9aea8f

Modified Files
--------------
src/common/unicode/Makefile                                           | 4 ++--
...ate-unicode_width_table.pl => generate-unicode_combining_table.pl} | 2 +-
src/common/wchar.c                                                    | 2 +-
.../common/{unicode_width_table.h => unicode_combining_table.h}       | 2 +-
4 files changed, 5 insertions(+), 5 deletions(-)


pgsql-committers by date:

Previous
From: Peter Eisentraut
Date:
Subject: pgsql: Fix handling of partitioned index in RelationGetNumberOfBlocksIn
Next
From: John Naylor
Date:
Subject: pgsql: Update display widths as part of updating Unicode