with setMaxResults broken?
As a workaround, it seems that something like:
setFirstResult(chunkNumber * chunkSize/2).setMaxResults(chunkNumber *
chunkSize/2 + chunkize)
works, though I have only slightly tested it. :)
___
SMA Solar Technology AG
ectProvider
4. org.apache.openjpa.lib.rop.MergedResultObjectProvider
Some brave code warrior needs to take a look.
-
Pinaki Poddar
Chair, Apache OpenJPA Project
--
View this message in context:
http://openjpa.208410.n2.nabble.com/Slice-setFirstResult-with-setMaxResults-broken-tp6695977p6712270.html
Sent from the OpenJPA Users mailing li
, 18. August 2011 02:11
An: users@openjpa.apache.org
Betreff: Re: Slice setFirstResult with setMaxResults broken?
> Slice setFirstResult with setMaxResults broken?
If the query has a order by clause, then yes. Just noticed.
Tricky/interesting problem to solve. Any brave code warrior?
-
Pin
Slice setFirstResult with setMaxResults broken?
> Slice setFirstResult with setMaxResults broken?
If the query has a order by clause, then yes. Just noticed.
Tricky/interesting problem to solve. Any brave code warrior?
-
Pinaki Poddar
Chair, Apache OpenJPA Project
--
View this message in contex
> Slice setFirstResult with setMaxResults broken?
If the query has a order by clause, then yes. Just noticed.
Tricky/interesting problem to solve. Any brave code warrior?
-
Pinaki Poddar
Chair, Apache OpenJPA Project
--
View this message in context:
http://openjpa.208410.n2.nabble.
Hi,
with Slice, when i do query.setFirstResult(5).setMaxResults(20), I get 15
results in the resultset, not 20 as one would expect (the table is much larger).
With a different similar setup but without slice, everything works fine, so I
suspect slice might be the cause here.
I'm using OpenJPA
