From: | Harry Yau <harry(dot)yau(at)regaltronic(dot)com> |
---|---|
To: | PGG <pgsql-general(at)postgresql(dot)org>, PGA <pgsql-admin(at)postgresql(dot)org>, PGH <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Problem of Null Ordering |
Date: | 2002-12-03 09:13:09 |
Message-ID: | 3DEC75A5.D544E5D@regaltronic.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin pgsql-general |
Hi all,
I got some problem with the ordering.
I have a table which have a integer field , namely IF1, which is able to
have NULL value.
When I query this table and Order by IF1, the row that have the value of
NULL will come after the row that have a number value. I am wondering is
there anything I can do to make the row with Null value come before the
row with a number value. (Same as other RDBMS does - Sybase, MYSQL etc.)
Be more specified, I want to do something in the DBMS level instead of
doing some union queries. And apply this standard to all other query and
table in PGSQL.
Thank In Advance.
Harry Yau ( ^_^ )
From | Date | Subject | |
---|---|---|---|
Next Message | Jean-Christian Imbeault | 2002-12-03 09:31:52 | Re: Problem of Null Ordering |
Previous Message | Tom Lane | 2002-12-03 05:51:45 | Re: pg_restore error: function plpgsql_call_handler already exists with same argument types |
From | Date | Subject | |
---|---|---|---|
Next Message | Karel Zak | 2002-12-03 09:13:21 | Re: [GENERAL] One SQL to access two databases. |
Previous Message | Neil Conway | 2002-12-03 07:50:01 | Re: What could cause total crash of a postgres |