On Thu, Dec 24, 2009 at 5:40 PM, Andrew Dunstan and...@dunslane.net wrote:
1) If I set my database and connection encoding to UTF-8, does pg (and
future versions of it) guarantee that unicode code points are stored
unmodified? or could it be that pg does some unicode
normalization/manipulation
Dear PG hackers,
I have two question regarding Unicode support in PG:
1) If I set my database and connection encoding to UTF-8, does pg (and
future versions of it) guarantee that unicode code points are stored
unmodified? or could it be that pg does some unicode
normalization/manipulation with
- - wrote:
Dear PG hackers,
I have two question regarding Unicode support in PG:
1) If I set my database and connection encoding to UTF-8, does pg (and
future versions of it) guarantee that unicode code points are stored
unmodified? or could it be that pg does some unicode
2) How far is normalization support in PG? When I checked a long time
ago, there was no such support. Now that the SQL standard mandates a
NORMALIZE function that may have changed. Any updates?
Creating such a function shouldn't be terribly hard AIUI, if someone
wants to submit a
On Dec 24, 2009, at 4:14 PM, Andrew Dunstan wrote:
2) How far is normalization support in PG? When I checked a long time
ago, there was no such support. Now that the SQL standard mandates a
NORMALIZE function that may have changed. Any updates?
Creating such a function shouldn't be
