db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bryan Pendleton (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-2887) NULLS FIRST / LAST for ORDER BY
Date Sat, 21 Jul 2007 15:32:06 GMT

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

Bryan Pendleton updated DERBY-2887:
-----------------------------------

    Attachment: prototypeCodeNoTests.diff

Attached is 'prototype_code_no_tests.diff', which is NOT for commit. I've started experimenting
with some changes, and I wanted to attach them so I wouldn't lose them, but I've still got
more work to do.

This first attempt modifies the compare(DVD) api so that the caller can pass in a boolean
indicating whether NULLS should sort FIRST or LAST, and modifies the sorter to use that new
api. The patch also has changes to the grammar and the compiler to parse the user's <null
ordering> specification and track it in the data structures.

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


Mime
View raw message