| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, Alvaro Herrera <alvherre(at)commandprompt(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: quoting psql varible as identifier |
| Date: | 2010-01-18 20:26:53 |
| Message-ID: | 13148.1263846413@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> ... Also, I prefer an
> API where the escaping function does include the quotes, so I've done
> it that way in the attached patch.
IMO this function should act as much like PQescapeStringConn as possible.
Random differences like including or not including outer quotes don't
make the user's life better. Random differences like a slightly
different rule for the amount of space required are outright dangerous.
Also, why is this patch changing the documentation of PQescapeStringConn?
It might be only whitespace changes, but I don't particularly wish to
have to determine that.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2010-01-18 21:01:44 | Re: quoting psql varible as identifier |
| Previous Message | Robert Haas | 2010-01-18 20:19:06 | Re: quoting psql varible as identifier |