Skip site navigation (1) Skip section navigation (2)

Re: [GENERAL] ascii() for utf8

From: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
To: Decibel! <decibel(at)decibel(dot)org>
Cc: Stuart <smcg2297(at)frii(dot)com>, PostgreSQL-development list <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [GENERAL] ascii() for utf8
Date: 2007-07-31 13:55:31
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-generalpgsql-hackers
Decibel! wrote:
> Moving to -hackers.
> On Jul 27, 2007, at 1:22 PM, Stuart wrote:
>> Does Postgresql have a function like ascii() that will
>> return the unicode codepoint value for a utf8 character?
>> (And symmetrically same for question chr() of course).

> I suspect that this is just a matter of no one scratching the itch. I 
> suspect a patch would be accepted, or you could possibly put something on 
> pgFoundry.

Nay; there were some discussions about this not long ago, and I think
one conclusion you could draw from them is that many people want these
functions in the backend.

> I'd set it up so that ascii() and chr() act according to the 
> appropriate locale setting (I'm not sure which one would be appropriate).

I don't see why any of them would react to the locale, but they surely
must honor client encoding.

Alvaro Herrera                     
"I dream about dreams about dreams", sang the nightingale
under the pale moon (Sandman)

In response to


pgsql-hackers by date

Next:From: Decibel!Date: 2007-07-31 15:09:59
Subject: Re: Quick idea for reducing VACUUM contention
Previous:From: Dawid KuroczkoDate: 2007-07-31 09:44:04
Subject: Re: Machine available for community use

pgsql-general by date

Next:From: Lee KeelDate: 2007-07-31 13:56:29
Subject: Re: tables not in list
Previous:From: Andrew EdsonDate: 2007-07-31 13:53:41
Subject: Error restarting postmaster

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group