> 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.com/Slice
http://openjpa.apache.org/builds/apache-openjpa-2.1.1/docs/manual/manual.htmlgives
me a 404. This is the link off the main Documentation page. Thought
someone should know.
Best,
Laird
--
http://about.me/lairdnelson
Try something similar with Slice, where the database is same, but two slices
use different schema.
where you store the new objects are determined by slice.DistributionPolicy.
Hence, it is possible to store related objects in separate slices.
-
Pinaki Poddar
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
Hi,
I now opened a JIRA for the issue (
https://issues.apache.org/jira/browse/OPENJPA-2040 ).
Regarding your questions: Qualifier means Schema, so in the tablename
"test.Person" "test" would be the qualifier.
The two records are in different schemas but on the same database
(otherwise my Met
