Much better in fact. The migration from 2 to 3 will be fairly painless since
there isn't that much API change. And you'll find (like I did) that the
improvements in ROP are well worth it. Nested contexts in ROP are now
available, client/server communications are optimised, pagination is great f
ROP's became better, e.g. it now supports nesting of contexts same way as
DataContexts do
2009/12/24 Emanuele Maiarelli
> I'll give a try once the project will me stable on the 2.0.4. This
> project uses ROP with a swing rich application, plus some webservices for
> batchjobs, are ROP still wo
I'll give a try once the project will me stable on the 2.0.4. This
project uses ROP with a swing rich application, plus some webservices
for batchjobs, are ROP still working good on 3.0
as they works on 2.0.4?
Andrus Adamchik ha scritto:
Sure. Hopefully within a couple of weeks 3.0 becomes R
Sure. Hopefully within a couple of weeks 3.0 becomes Release Candidate
and final after that, so you may give it another look.
For now I guess the only way is to write a custom query extending
SQLTemplate and overriding 'createSQLAction' to call 'setFetchSize' on
the JDBC statement. Implemen
I'm trying to figureout a solution using 2.0.4.
I don't feel confortable in switching to 3.0 at this stage of the
project.
Thank you,
Emanuele
Andrus Adamchik ha scritto:
This is likely an issue with MySQL driver caching returned data. The
solution was implemented in Cayenne 3
This is likely an issue with MySQL driver caching returned data. The
solution was implemented in Cayenne 3.0 (which is now in beta):
query.setStatementFetchSize(1000);
This propagates the fetch size setting to the JDBC statement, reducing
the driver memory footprint.
Andrus
On Dec 24,
