db-derby-dev mailing list archives

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

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

Daniel John Debrunner commented on DERBY-2887:

I see from the wiki that the 'Interaction of NULLS FIRST/LAST and ASC/DESC' is still not resolved.
I think this needs to be resolved before any code is committed.

If 'NULLS FIRST' really means first regardless of ASC/DESC then:

   -  The wiki says that NULLS LAST is the default for Derby, but actually it will be  NULLS
FIRST if DESC and NULLS LAST if ASC (or is it the other way around :-)

  - the code would need to be clear so that in the data type the variables & concept are
described as nulls low or nulls high. Continuing the nulls first/last naming into DVD where
it would actually have a different meaning would lead to confusion in the code. The SQL language
layer would continue to have naming indicating first/last concept.

> -------------------------------
>                 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 LAST

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

View raw message