[
https://issues.apache.org/jira/browse/DERBY-2887?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12514992
]
Bryan Pendleton commented on DERBY-2887:
----------------------------------------
Thanks very much for the comments and suggestions, Dan and Christian! I believe
that I have the interpretation of NULLS FIRST/LAST wrong in the prototype code,
and that Derby's current behavior is actually:
NULLS LAST is the default for ascending order, and NULLS FIRST is the default
for descending order.
Section 10.10 of the SQL standard is the relevant section.
I'll update the wiki to incorporate this revised understanding, then I'll have
a fresh look at the code, and in the process I'll incorporate the other
suggestions. I'm particularly keen on trying to avoid having to touch so many
files; Dan your comments on the compare functions are very helpful.
> 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.
