Re: endash not a graphic character?

From: Bruno Wolff III <bruno(at)wolff(dot)to>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: endash not a graphic character?
Date: 2016-08-21 18:55:19
Message-ID: 20160821185519.GA32162@wolff.to
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Sun, Aug 21, 2016 at 14:24:16 -0400,
Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
>Unfortunately, these particular characters are U+2013 and U+2014 so you
>lose.

Thanks for saving me some time, as it would have taken me quite a while
to figure that out.

I'll adjust the constraint so that good strings aren't rejected. Which
was my immediate problem. I'm not that worried about bad strings getting
added, since the data also gets checked before trying to add it to
the database.

>Obviously there's room for improvement here, but so far nobody's been
>motivated to work on it. Last discussion about it (AFAIR) was this
>thread:

One thing I would suggest is documenting this limitation under:
https://www.postgresql.org/docs/9.6/static/functions-matching.html#FUNCTIONS-POSIX-REGEXP

I might have missed it, but I did try reading that section to see if I was
doing something wrong before asking on the list. In particular I would
expect this limitation to be noted under:
9.7.3.6. Limits and Compatibility

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Tatsuki Kadomoto 2016-08-22 03:27:32 incorrect checksum detected on "global/pg_filenode.map" when VACUUM FULL is executed
Previous Message Tom Lane 2016-08-21 18:24:16 Re: endash not a graphic character?