Re: [BUGS] byteain() doesn't parse correctly

2001-02-12 Thread Jered Floyd
Tom Lane <[EMAIL PROTECTED]> writes: > 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. Argh. This

Re: [BUGS] byteain() doesn't parse correctly

2001-02-07 Thread Tom Lane
Jered Floyd <[EMAIL PROTECTED]> writes: > Tom Lane <[EMAIL PROTECTED]> writes: >> 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

Re: [BUGS] byteain() doesn't parse correctly

2001-02-07 Thread Tom Lane
Jered Floyd <[EMAIL PROTECTED]> 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

[BUGS] byteain() doesn't parse correctly

2001-02-07 Thread Jered Floyd
POSTGRESQL BUG REPORT TEMPLATE Your name : Jered Floyd Your email address : [EMAIL PROT