|
1 | 1 | <!-- |
2 | | -$PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.353 2005/08/2403:47:11 momjian Exp $ |
| 2 | +$PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.354 2005/08/2414:35:26 momjian Exp $ |
3 | 3 | --> |
4 | 4 |
|
5 | 5 | <appendix id="release"> |
@@ -299,7 +299,13 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.353 2005/08/24 03:47:11 momjian |
299 | 299 | will be treated literally in non-E strings. To prepare for this |
300 | 300 | change, use E'' strings in places that need special backslash |
301 | 301 | processing, and turn on escape_string_warning to find additional |
302 | | - strings that need to be converted to use <literal>E''</>. |
| 302 | + strings that need to be converted to use <literal>E''</>. Also, |
| 303 | + use two single-quotes ('') to embed a literal single-quote |
| 304 | + in a string, rather than the PostgreSQL-supported syntax of |
| 305 | + backslash single-quote (\'). The former is standards-conforming |
| 306 | + and does not require the use of the E'' string syntax. You can |
| 307 | + also use the $$ string syntax, which does not treat backslashes |
| 308 | + specially. |
303 | 309 | </para> |
304 | 310 | </listitem> |
305 | 311 |
|
|