|
1 | 1 | <!-- |
2 | | -$PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.354 2005/08/2414:35:26 momjian Exp $ |
| 2 | +$PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.355 2005/08/2415:35:01 tgl Exp $ |
3 | 3 | --> |
4 | 4 |
|
5 | 5 | <appendix id="release"> |
@@ -284,8 +284,8 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.354 2005/08/24 14:35:26 momjian |
284 | 284 |
|
285 | 285 | <listitem> |
286 | 286 | <para> |
287 | | - <varname>standard_conforming_strings>/> - does this release |
288 | | - treat backslashes literally innormal strings? |
| 287 | + <varname>standard_conforming_strings</> - does this release |
| 288 | + treat backslashes literally inordinary strings? |
289 | 289 | </para> |
290 | 290 | </listitem> |
291 | 291 |
|
@@ -625,13 +625,13 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.354 2005/08/24 14:35:26 momjian |
625 | 625 |
|
626 | 626 | <listitem> |
627 | 627 | <para> |
628 | | - Fix <command>HAVING</> without aggregate functions and no |
629 | | - <command>GROUP BY</> to behave as if the main query returns a |
630 | | - single group (Tom) |
| 628 | + Fix <command>HAVING</> without any aggregate functions or |
| 629 | + <command>GROUP BY</> so that the query returns a single group (Tom) |
631 | 630 | </para> |
632 | 631 | <para> |
633 | 632 | Previously, such a case would treat the <command>HAVING</> |
634 | | - clause as <command>WHERE</> clause. |
| 633 | + clause the same as a <command>WHERE</> clause. This was not per spec. |
| 634 | + </para> |
635 | 635 | </listitem> |
636 | 636 |
|
637 | 637 | <listitem> |
|