Re: BUG #13440: unaccent does not remove all diacritics

From: Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Michael Gradek <mike(at)busbud(dot)com>, PostgreSQL Bugs <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: BUG #13440: unaccent does not remove all diacritics
Date: 2015-09-02 22:02:19
Message-ID: CAEepm=3=2RM_6Nz8ss=QpuimRTF_2R-U5iBHqQ8r-rGSj9LsAQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Thu, Sep 3, 2015 at 4:55 AM, Andres Freund <andres(at)anarazel(dot)de> wrote:

> Hi,
>
> On 2015-06-23 13:00:43 +1200, Thomas Munro wrote:
> > I looked at this again and noticed a few problems. I've attached a
> > new version.
>
> My re-reading of the discussion is to commit this to master? I'll do
> that unless somebody protests.
>

What about 9.5? I thought the idea was not to change preexisting rules in
back branches because of compatibility problems with existing data that
users may have indexed/stored, but 9.5 obviously can't have that problem
yet.

> To me it seems like a good idea to include the generation script
> somewhere? Unicode isn't all that static.
>

+1

--
Thomas Munro
http://www.enterprisedb.com

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message robert.kruus 2015-09-02 22:03:16 BUG #13608: 3 argument range constructor functions
Previous Message Tom Lane 2015-09-02 21:33:51 Re: BUG #13607: Creating "Readonly" User for public Shema.