1
0
mirror of https://github.com/postgres/postgres.git synced 2025-04-27 22:56:53 +03:00

Fix broken markup.

This commit is contained in:
Tom Lane 2005-08-24 15:35:01 +00:00
parent e4bffdad75
commit 2a733db0cc

View File

@ -1,5 +1,5 @@
<!-- <!--
$PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.354 2005/08/24 14:35:26 momjian Exp $ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.355 2005/08/24 15:35:01 tgl Exp $
--> -->
<appendix id="release"> <appendix id="release">
@ -284,8 +284,8 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.354 2005/08/24 14:35:26 momjian
<listitem> <listitem>
<para> <para>
<varname>standard_conforming_strings>/> - does this release <varname>standard_conforming_strings</> - does this release
treat backslashes literally in normal strings? treat backslashes literally in ordinary strings?
</para> </para>
</listitem> </listitem>
@ -625,13 +625,13 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.354 2005/08/24 14:35:26 momjian
<listitem> <listitem>
<para> <para>
Fix <command>HAVING</> without aggregate functions and no Fix <command>HAVING</> without any aggregate functions or
<command>GROUP BY</> to behave as if the main query returns a <command>GROUP BY</> so that the query returns a single group (Tom)
single group (Tom)
</para> </para>
<para> <para>
Previously, such a case would treat the <command>HAVING</> Previously, such a case would treat the <command>HAVING</>
clause as <command>WHERE</> clause. clause the same as a <command>WHERE</> clause. This was not per spec.
</para>
</listitem> </listitem>
<listitem> <listitem>