> Cayenne adapters for Oracle, Derby, FrontBase, Postgres and SQLServer
> use JDBC-level batching that sometimes speeds things up
> significantly. SQLTemplate doesn't use JDBC batching. There are other
> possible reasons too, such as pk caching.
Thanks for the hint. How can I make sure that
What I found was that in Insert operations, it is best to use
Cayenne data objects (as opposed to raw SQL queries)
Cayenne adapters for Oracle, Derby, FrontBase, Postgres and SQLServer
use JDBC-level batching that sometimes speeds things up
significantly. SQLTemplate doesn't use JDBC batchi
Sorry for the previous mail, I inadvertently sent it half-ready :-(
Hello,
I made a small performance test comparing different Cayenne solutions with JDBC
solutions. What I found was that in Insert operations, it is best to use
Cayenne data objects (as opposed to raw SQL queries), while for Updat
Hello,
I made a small performance test comparing different Cayenne solutions with JDBC
solutions. What I found was that in Insert operations, it is best to use
Cayenne data objects (as opposed to raw SQL queries), while for Update and
Delete the case is the opposite.
So for Insert, this worked b
