| From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Michael Artz <mlartz(at)gmail(dot)com>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: bytea hex input/output |
| Date: | 2006-05-17 03:30:09 |
| Message-ID: | 200605170330.k4H3U9D21057@candle.pha.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Tom Lane wrote:
> "Michael Artz" <mlartz(at)gmail(dot)com> writes:
> > What ig going on behind the scenes? Does it first get converted to text and
> > then on to bytea?
>
> No, the \nnn escape is built into the lexer's syntax for a string
> literal (see backend/parser/scan.l), and only after that does the string
> get fed to bytea's input routine (or any other datatype's either).
> In hindsight this was a horribly bad idea that we'll be paying through
> the nose for, for some time to come :-(. But we're stuck with it for
> the moment.
Should we rethink this for SQL standard strings?
--
Bruce Momjian http://candle.pha.pa.us
EnterpriseDB http://www.enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2006-05-17 03:34:18 | Re: bytea hex input/output |
| Previous Message | Tom Lane | 2006-05-17 03:24:29 | Re: Announce: GPL Framework centered on Postgres |