[
http://team.ops4j.org/browse/QI-370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17523#comment-17523
]
Arvid Huss commented on QI-370:
-------------------------------
Your right Niclas - I should have read up on that.
I just reacted to the GUI behavior when visualizing a larger list since in
larger result sets I could not see any sorting going on
due to null results returning first in list.
There is no conform SQL standard for how to treat null.
Different sql vendors handle the order different ( both last and first exist )
Some of the SQL vendors provide the NULLS FIRST or NULLS LAST functionality on
the ORDER BY clause.
I dont know if it is worth to attempt a implementation of that since
I can easily treat the returned list in any way I like to before presentation
to the user.
> OrderByComparator in IterableQuerySource does not honor null values in sort
> order
> ---------------------------------------------------------------------------------
>
> Key: QI-370
> URL: http://team.ops4j.org/browse/QI-370
> Project: Qi4j
> Issue Type: Improvement
> Components: Core Runtime
> Affects Versions: 1.3, 2.0 - Reductionism
> Reporter: Arvid Huss
> Priority: Minor
>
> IterableQuerySource and its predecessor IterableQuery( 1.3 )
> Regardless of sort order (ASC,DESC) order by null values are always returned
> first in the resulting list.
> I was expecting them either to be first or last depending on ASC, DESC.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
http://team.ops4j.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
qi4j-dev mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/qi4j-dev
