You are viewing a plain text version of this content. The canonical link for it is here.

Posted to derby-dev@db.apache.org by "Bryan Pendleton (JIRA)" <ji...@apache.org> on 2007/08/18 20:57:31 UTC

[jira] Resolved: (DERBY-2887) NULLS FIRST / LAST for ORDER BY

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

Bryan Pendleton resolved DERBY-2887.
------------------------------------

       Resolution: Fixed
    Fix Version/s: 10.4.0.0
       Derby Info:   (was: [Patch Available])

Committed nullOrderingPatch.diff to the trunk as revision 567314.


> 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
>             Fix For: 10.4.0.0
>
>         Attachments: nullOrderingPatch.diff, prototypeCodeNoTests.diff, prototypeCodeNoTests_v2.diff, prototypeCodeNoTests_v3.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.