[hibernate-issues] [Hibernate-JIRA] Updated: (HSHARDS-3) setMaxResults method of Query is behaving wrong
Max Ross (JIRA)
noreply at atlassian.com
Tue Mar 27 04:50:04 EDT 2007
[ http://opensource.atlassian.com/projects/hibernate/browse/HSHARDS-3?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Max Ross updated HSHARDS-3:
---------------------------
Assignee: Maulik Shah (was: Max Ross)
Maulik,
This is the bug we were discussing earlier today. Please take a look.
Thanks,
Max
> setMaxResults method of Query is behaving wrong
> -----------------------------------------------
>
> Key: HSHARDS-3
> URL: http://opensource.atlassian.com/projects/hibernate/browse/HSHARDS-3
> Project: Hibernate Shards
> Issue Type: Bug
> Components: query
> Affects Versions: 3.0.0.Beta1
> Environment: Hibernate 3.2
> Oracle 10g
> Reporter: Stephan Klapproth
> Assignee: Maulik Shah
>
> A simple query like this
> List<Person> persons = HibernateUtil.getSession().createQuery("from Person").setMaxResults(1).list();
> is returning one person object from every shard instead of one object. So when you have 3 shards configured, objects will be returned.
--
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.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the hibernate-issues
mailing list