[
http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-338?pag...
]
Sanne Grinovero commented on HSEARCH-338:
-----------------------------------------
yes it's not a decision to be taken lightly.
Imho it's a bug, as it's not behaving as advertised and documented: we should have
the same API as a plain hibernate/JPA query;
still somebody could rely on this.
If somebody was skipping the initial next() they'll have some trouble. The other side,
people doing it the right way are missing a result
and probably didn't even notice (as nobody reported the issue).
I would have fixen this in 3.1.1 as it's just wrong, but probably postponing it to 3.2
is less dangerous.
ScrollableResults initial position not coherent to core Hibernate
-----------------------------------------------------------------
Key: HSEARCH-338
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-338
Project: Hibernate Search
Issue Type: Bug
Components: query
Affects Versions: 3.1.0.GA
Reporter: Sanne Grinovero
Assignee: Sanne Grinovero
Priority: Trivial
Fix For: 3.1.1
The javadoc for interface ScrollableResults reads:
"Go to a location just before first result (this is the initial location)"
but Search's initial position is at the first result instead.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira