Tom Lane wrote:
> Bruce Momjian <br...@momjian.us> writes:
> > Here is a doc patch that at least explains the example.  Applied.
> 
> I think s/or/otherwise/ (both places) would make that read better.

Done with the attached patch.

-- 
  Bruce Momjian  <br...@momjian.us>        http://momjian.us
  EnterpriseDB                             http://enterprisedb.com

  + It's impossible for everything to be true. +
diff --git a/doc/src/sgml/func.sgml b/doc/src/sgml/func.sgml
new file mode 100644
index 2f307c2..bedd8ba
*** a/doc/src/sgml/func.sgml
--- b/doc/src/sgml/func.sgml
*************** SELECT ... WHERE CASE WHEN x &lt;&gt; 0 
*** 10015,10022 ****
  <programlisting>
  SELECT COALESCE(description, short_description, '(none)') ...
  </programlisting>
!    This returns <varname>description</> if it is not null, or
!    <varname>short_description</> if it is not null, or <literal>(none)</>.
    </para>
  
     <para>
--- 10015,10022 ----
  <programlisting>
  SELECT COALESCE(description, short_description, '(none)') ...
  </programlisting>
!    This returns <varname>description</> if it is not null, otherwise
!    <varname>short_description</> if it is not null, otherwise <literal>(none)</>.
    </para>
  
     <para>
-- 
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs

Reply via email to