[
https://issues.apache.org/jira/browse/DERBY-2887?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bryan Pendleton reopened DERBY-2887:
------------------------------------
It occurs to me that maybe I should have updated the
DatabaseMetaData implementation, specifically the methods:
- nullsAreSortedAtEnd()
- nullsAreSortedAtStart()
- nullsAreSortedHigh()
- nullsAreSortedLow()
I'm not totally sure what those methods are supposed to return,
and it's quite possible that no changes are needed, but I
thought that to be safe, I would re-open this issue and go
examine the documentation for those methods to see if they
need to be changed.
> 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.
