Neil Conway wrote:
> On Wed, 10 Apr 2002 22:36:49 -0700 "Barry Lind" <[EMAIL PROTECTED]>
> wrote:
>
>> Neil,
>>
>> Will this allow you to pass bytea data as binary data in the
>> parameters section (ability to bind values to parameters) or will
>> this still require that the data be passed as a text string that
>> the parser needs to parse.
>
>
> The patch I'm working on would require that the parameters are still
> parsed, so it would likely suffer from the same performance
> problems.
>
> I'm unsure how to fix this without a change to the FE/BE protocol
> (and even then, it wouldn't be trivial). Suggestions?
>
The other day there was a discussion around the fact that X'ffff' will
get converted into an integer constant, e.g.
test=# select X'ffff';
?column?
----------
65535
(1 row)
, while SQL99 says that this syntax *should* be used to specify a
"binary string". It looks like the hex-to-integer magic actually occurs
in the lexer, and then the integer value of 65535 is passed to the
parser as an ICONST. I'm wondering if changing the lexer to make this a
conversion to a properly escaped bytea input string, and passing it to
the parser as a string constant would speed things up?
Joe
---------------------------(end of broadcast)---------------------------
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
