Received: from smtp9.xs4all.nl (smtp9.xs4all.nl [194.109.127.135]) by postgresql.org (8.11.3/8.11.4) with ESMTP id f89Eup706170 for ; Sun, 9 Sep 2001 10:56:51 -0400 (EDT) (envelope-from rene@lab.applinet.nl) Received: from TAL (a194-109-250-148.adsl.xs4all.nl [194.109.250.148]) by smtp9.xs4all.nl (8.9.3/8.9.3) with SMTP id QAA11004 for ; Sun, 9 Sep 2001 16:56:47 +0200 (CEST) From: Rene Pijlman To: pgsql-docs@postgresql.org Subject: NULLs and sort order Date: Sun, 09 Sep 2001 16:58:18 +0200 Organization: Applinet Message-ID: <7b0npts2v4csnqttdoviurtnsbvafape0v@4ax.com> X-Mailer: Forte Agent 1.7/32.534 MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by postgresql.org id f89Euq706171 X-Archive-Number: 200109/17 X-Sequence-Number: 949 I'm forwarding this information from Peter Eisentraut on pgsql-hackers about NULLs and sort order. I couldn't find this in the documentation. I guess it should be in "ORDER BY Clause" of "SELECT" in the Reference Manual, and in the 7.2 release notes. Can someone add this to the documentation? Or am I expected to submit a patch on the Docbook sources? On Sun, 9 Sep 2001 15:25:17 +0200 (CEST), Peter Eisentraut wrote: >Rene Pijlman writes: >> Currently the JDBC driver says: >> - Backend >= 7.2 sorts nulls higher than any other value in a >> domain. In other words: ascending means nulls at the end, >> descending means nulls at the start. >> - Backend < 7.2 puts nulls at the end regardless of sort order. > >That is correct. > >-- >Peter Eisentraut peter_e@gmx.net http://funkturm.homeip.net/~peter Regards, René Pijlman