Hello Adam,
This depends on what you are looking for. To force TopLink to submit the changes at the end of the transaction you can set the spec defined flush mode on the EntityManager to be 'commit' : em.setFlushMode(FlushModeType.COMMIT);
If you are looking for JDBC batch writing TopLink Essentials does not offer this functionality.
--Gordon
-----Original Message-----
From: Adam Bien [mailto:abien_at_adam-bien.com]
Sent: Wednesday, February 06, 2008 5:37 AM
To: persistence_at_glassfish.dev.java.net
Subject: Proprietary Optimization
Hi All,
is there a way in TopLink Essentials (of course beyond the JPA
Specification), to gather all updates and flush them bundled at the end
of transaction to the database (batch creates, updates etc.)? We are
using TopLink together with oracle...
I know such (proprietary) switches from other providers, like
"delay-updates-until-end-of-tx" by BEA. I didn't found any hints in
http://www.oracle.com/technology/products/ias/toplink/JPA/essentials/toplink-jpa-extensions.html
thank you in advance,
adam
--
Consultant, Author, Java Champion
Homepage: www.adam-bien.com
Weblog: blog.adam-bien.com
eMail: abien_at_adam-bien.com
Mobile: 0049(0)170 280 3144
Books: Enterprise Architekturen (ISBN: 393504299X),
Java EE 5 Architekturen (ISBN: 3939084247),
J2EE Patterns, J2EE Hotspots, Enterprise Frameworks and Struts