From: | Florian Weimer <fweimer(at)bfk(dot)de> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Hannes Frederic Sowa <hsowa(at)bfk(dot)de>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: [PATCH] Documentation: remove confusing paragraph about backslash escaping |
Date: | 2012-02-27 16:00:47 |
Message-ID: | 824nucnu4w.fsf@mid.bfk.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
* Tom Lane:
> Hannes Frederic Sowa <hsowa(at)bfk(dot)de> writes:
>> As with recent changes to `standard_conforming_strings' the paragraph
>> about backslash escaping in the description of `LIKE' is only confusing.
>> Thus I attached a patch to remove it.
>
> The para is still relevant if you don't have standard_conforming_strings
> on.
And if you aren't using parametrized queries. The old text is a bit
misleading even with standard_conforming_strings set to off. It is
technically correct because it refers to the SQL statement parser which
is run on parameters, but this seems a pretty fine distinction.
--
Florian Weimer <fweimer(at)bfk(dot)de>
BFK edv-consulting GmbH http://www.bfk.de/
Kriegsstraße 100 tel: +49-721-96201-1
D-76133 Karlsruhe fax: +49-721-96201-99
From | Date | Subject | |
---|---|---|---|
Next Message | Tatsuo Ishii | 2012-02-27 16:05:22 | Re: How to know a table has been modified? |
Previous Message | Pavel Stehule | 2012-02-27 15:54:25 | Re: WARNING: concurrent insert in progress within table "resource" |