[jira] Updated: (DERBY-2887) NULLS FIRST / LAST for ORDER BY
[ https://issues.apache.org/jira/browse/DERBY-2887?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bryan Pendleton updated DERBY-2887: --- Derby Info: [Patch Available] > 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: 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 : > ::= > 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.
[jira] Updated: (DERBY-2887) NULLS FIRST / LAST for ORDER BY
[ https://issues.apache.org/jira/browse/DERBY-2887?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bryan Pendleton updated DERBY-2887: --- Attachment: nullOrderingPatch.diff Attached is nullOrderingPatch.diff, a patch proposal. This patch builds on the prototype_v3 patch by: - adding code to OrderByList to ensure that ORDER BY triggers a sort when necessary - adding tests to orderby.sql and orderbyElimination.sql to demonstrate the behavior of NULLS FIRST/LAST - adding a few more comments to the code changes. I'd be most grateful if you could have a look at this patch proposal and tell me what you think. > 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: 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 : > ::= > 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.
[jira] Updated: (DERBY-2887) NULLS FIRST / LAST for ORDER BY
[ https://issues.apache.org/jira/browse/DERBY-2887?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bryan Pendleton updated DERBY-2887: --- Attachment: prototypeCodeNoTests_v3.diff Attached is prototypeCodeNoTests_v3.diff, updated in response to the various suggestions. This version 3 patch is much simpler than the previous two; Dan's ideas about sharing common code into DataType.java were a big win. My next steps will be to: add some new tests, investigate the sort avoidance issue, and track down a diff in the Wisconsin tests involving outer joins. All the other existing tests pass. > 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, > prototypeCodeNoTests_v3.diff > > > I suggest to implement the "null ordering" option for the "ORDER BY" clause: > According to the SQL standard, 10.10 : > ::= > 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.
[jira] Updated: (DERBY-2887) NULLS FIRST / LAST for ORDER BY
[ https://issues.apache.org/jira/browse/DERBY-2887?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bryan Pendleton updated DERBY-2887: --- Attachment: prototypeCodeNoTests_v2.diff The first patch did not handle collation sequences properly. The prototypeCodeNoTests_v2.diff addresses that problem. Still just a work in progress. > 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 : > ::= > 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.
[jira] Updated: (DERBY-2887) NULLS FIRST / LAST for ORDER BY
[ 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 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 : > ::= > 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.
