Community
Participate
Working Groups
Build Identifier: 2.3 nightly CursoredStreams (and thus probably also Scrollablecursors which were not tested) always seem to use the default connection pool ina partitioned DB environment, thus they don't adhere to the partitioning policies in effect. Those two features share a common use case, handling of large tables/datasets, where you probably want to have both cursors and partitioning. That's why i think fixing this would make eclipselink much better suited for this use case. Fixing this even for UnionPartition probably would require some more work but would be nice aswell. Reproducible: Always Steps to Reproduce: 1. Apply a partitioning policy to your model or supply a policy with a queryhint 2. load data from a partitioned table using cursors 3.
What i forgot to mention, i use PostgreSQL as database and thus i can only use cursors in a transaction context. i thus call em.getTransaction().begin() and jpaEm.getUnitOfWork().beginEarlyTransaction() before starting the query.
Setting target and priority. See the following page for the meanings of these fields: http://wiki.eclipse.org/EclipseLink/Development/Bugs/Guidelines Community: Please vote for this bug if it is important to you. Votes are one of the main criteria we use to determine which bugs to fix next.
The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink
