[
http://issues.ops4j.org/browse/QI-233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13278#action_13278
]
Niclas Hedhman commented on QI-233:
-----------------------------------
The code in question is essentially also trying to 'compensate' for an
out-of-sync index. Is that actually necessary?
I am now making it simpler, and Rickard can tell me why it must do such
compensation.
> Query.iterator().next() returns null if no hasNext() has been executed.
> -----------------------------------------------------------------------
>
> Key: QI-233
> URL: http://issues.ops4j.org/browse/QI-233
> Project: Qi4j
> Issue Type: Bug
> Reporter: Niclas Hedhman
> Assignee: Niclas Hedhman
>
> The Iterator returned by EntityQueryImpl doesn't initialize the first
> instance of member reference "next", so that if one skips the call to
> hasNext(), one get a null value returned.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.ops4j.org/secure/Administrators.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
