| From: | Craig Ringer <craig(at)2ndquadrant(dot)com> |
|---|---|
| To: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | TODO: Expose parser support for decoding unicode escape literals to user |
| Date: | 2014-05-15 08:31:48 |
| Message-ID: | 53747B74.4080801@2ndquadrant.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Hi all
I just noticed a Stack Overflow question
(http://stackoverflow.com/q/20124393/398670) where someone's asking how
to decode '\u0000` style escapes *stored in database text fields* into
properly encoded text strings.
The parser supports this for escape-strings, and you can write E'\u011B'
to get 'ě' because of
http://postgresql.1045698.n5.nabble.com/Unicode-escapes-in-literals-td1992313.html.
I don't see this exposed in a way that users can call directly, though.
'decode(bytea, text)' has the 'escape' input, but it expects octal.
It's possible to use PL/PgSQL's 'EXECUTE' to use the parser to do the
work, but that's downright awful.
Am I missing something obvious, or is this something that'd be a good
new-developer TODO?
--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Sim Zacks | 2014-05-15 08:42:15 | Re: Correct update statement |
| Previous Message | Khangelani Gama | 2014-05-15 06:19:27 | Correct update statement |