On Saturday, December 14, 2002, at 03:24  PM, Bruce Momjian wrote:

I can't think of an ultimate solution.  If we added a length to the
passed query string, so you could embed nulls, we would still have the
problem of handling the null once we split the query up into data
elements.  The only solution there would be to add a length to all
passed data values, so we could handle nulls in them, but I doubt it is
worth the effort and added code complexity.
No, but it might be worth it if PostgreSQL's PREPAREd statements created real functions. Then each value could be passed to the back-end individually, rather than in one big string. so instead of

"execute stmt('val1', 'val2')"

we could do:

stmt(val1, val2);

where "val1" and "val2" are actually variables that hold the values being passed.

David

--
David Wheeler AIM: dwTheory
[EMAIL PROTECTED] ICQ: 15726394
http://david.wheeler.net/ Yahoo!: dew7e
Jabber: [EMAIL PROTECTED]



Reply via email to