Re: bytea hex input/output - Mailing list pgsql-general

From Bruce Momjian
Subject Re: bytea hex input/output
Date
Msg-id 200605170330.k4H3U9D21057@candle.pha.pa.us
Whole thread Raw
In response to Re: bytea hex input/output  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: bytea hex input/output  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general
Tom Lane wrote:
> "Michael Artz" <mlartz@gmail.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. +

pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: Announce: GPL Framework centered on Postgres
Next
From: Tom Lane
Date:
Subject: Re: bytea hex input/output