db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christian d'Heureuse (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-2887) NULLS FIRST / LAST for ORDER BY
Date Tue, 24 Jul 2007 15:33:31 GMT

    [ https://issues.apache.org/jira/browse/DERBY-2887?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12515005
] 

Christian d'Heureuse commented on DERBY-2887:
---------------------------------------------

I have tested with H2 (http://www.h2database.com):

 create table temp1 (i int);
 insert into temp1 values (1);
 insert into temp1 values (2);
 insert into temp1 values (null);
 select * from temp1 order by i desc nulls first;

Result:
 NULL
 2
 1

> NULLS FIRST / LAST for ORDER BY
> -------------------------------
>
>                 Key: DERBY-2887
>                 URL: https://issues.apache.org/jira/browse/DERBY-2887
>             Project: Derby
>          Issue Type: Improvement
>          Components: SQL
>            Reporter: Christian d'Heureuse
>            Assignee: Bryan Pendleton
>            Priority: Minor
>         Attachments: prototypeCodeNoTests.diff, prototypeCodeNoTests_v2.diff
>
>
> I suggest to implement the "null ordering" option for the "ORDER BY" clause:
> According to the SQL standard, 10.10 <sort specification list>:
>  <null ordering> ::=
>     NULLS FIRST
>     | NULLS LAST

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message