Re: BUG #15548: Unaccent does not remove combining diacritical characters
| От | Hugh Ranalli |
|---|---|
| Тема | Re: BUG #15548: Unaccent does not remove combining diacritical characters |
| Дата | |
| Msg-id | CAAhbUMMrNL9uXXpwS+BPTGjKQv5Sxvr+OY2C73Ag7oFyjSOiEQ@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: BUG #15548: Unaccent does not remove combining diacritical characters (Tom Lane <tgl@sss.pgh.pa.us>) |
| Ответы |
Re: BUG #15548: Unaccent does not remove combining diacriticalcharacters
|
| Список | pgsql-bugs |
On Thu, 3 Jan 2019 at 13:22, Tom Lane <tgl@sss.pgh.pa.us> wrote:
Alvaro Herrera <alvherre@2ndquadrant.com> writes:
> I think the point is that if the committee updates with a further
> version of the file, how do you find the new version? We need a URL
> that's one step removed from the final file, so that we can see if we
> need to update it. Maybe we can provide both URLs for convenience.
+1. Could be phrased along the lines of "documents are at URL1,
currently synced with URL2" so that it's clear that URL2 should
be updated when we re-sync with a newer release.
Yes, this is what I was thinking. I was integrating this into my installer, used the "new" URL provided to download the file, and spent several minutes wondering why the script was failing (and what I had broken in it), before realising what had happened.
В списке pgsql-bugs по дате отправления: