[
https://issues.apache.org/jira/browse/DERBY-2887?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bryan Pendleton resolved DERBY-2887.
------------------------------------
Resolution: Fixed
I read the DatabaseMetaData javadoc for a while, and I didn't see
any reason to believe that our current implementation should
change due to the NULLS FIRST/LAST support. The DatabaseMetaData
javadoc doesn't specifically mention the impact of NULLS FIRST/LAST,
but since the DatabaseMetaData methods are supposed to describe
the behavior of the database system as a whole, and the NULLS
FIRST/LAST is a query-specific behavior, it seems reasonable that
the DatabaseMetadata methods should not take NULLS FIRST/LAST
into account.
So I think it's safe to re-resolve this issue.
> 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.
