On Tue, May 24, 2011 at 06:37, Yasuo Ohgaki yohg...@ohgaki.net wrote:
2011/5/20 Hannes Magnusson hannes.magnus...@gmail.com:
On Fri, May 20, 2011 at 03:24, Yasuo Ohgaki yohg...@ohgaki.net wrote:
Hi all
Current PostgreSQL has new escape functions for literals and identifiers.
Since there is
2011/5/20 Hannes Magnusson hannes.magnus...@gmail.com:
On Fri, May 20, 2011 at 03:24, Yasuo Ohgaki yohg...@ohgaki.net wrote:
Hi all
Current PostgreSQL has new escape functions for literals and identifiers.
Since there is no function for that, I made patch for that. Attached patch is
for
2011/5/24 Yasuo Ohgaki yohg...@ohgaki.net:
Should we really provide fallback if PQescape(Literal|Identifier)
isn't available? Did you copy the escaping from postgresql directly?
Wouldn't it nice to have the same escaping capability for 8.x?
It's not possible to copy the code, since it's
On Fri, May 20, 2011 at 03:24, Yasuo Ohgaki yohg...@ohgaki.net wrote:
Hi all
Current PostgreSQL has new escape functions for literals and identifiers.
Since there is no function for that, I made patch for that. Attached patch is
for trunk and tested with PostgreSQL 8.4 and 9.0.
This patch
Hi all
Current PostgreSQL has new escape functions for literals and identifiers.
Since there is no function for that, I made patch for that. Attached patch is
for trunk and tested with PostgreSQL 8.4 and 9.0.
This patch would also applied to 5.4 branch but how about 5.3?
It's pain not to have
