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

Re: byteain() doesn't parse correctly

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Jered Floyd <jered(at)permabit(dot)com>
Cc: pgsql-bugs(at)postgresql(dot)org, dev-server(at)permabit(dot)com
Subject: Re: byteain() doesn't parse correctly
Date: 2001-02-07 14:59:35
Message-ID: 28091.981557975@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-bugs
Jered Floyd <jered(at)permabit(dot)com> writes:
> More curious is that it can't handle '\134' either, implying that 
> multiple levels of parsing are going on.

You're right, there are multiple levels of parsing going on.  The
string-literal parser gets first crack before the type-specific
input converter does.  If you don't allow for that when counting
backslashes etc, you'll get confused for sure.

			regards, tom lane

In response to

Responses

pgsql-bugs by date

Next:From: Tom LaneDate: 2001-02-07 15:41:48
Subject: Re: Re: round - timestamp bug
Previous:From: Tom LaneDate: 2001-02-07 14:55:57
Subject: Re: BUG or feature?

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