I am using Jboss 4.0.1RC2 and was comparing sql statements generated when using "instance-per-transaction" compared with "cmp2.x jdbc2 pm" container configurations.
I see that the jdbc2 configuration incurs less select sql queries (cache works, great), but is also causes more update statements. I use the following configuration : | <container-configuration extends="cmp2.x jdbc2 pm"> | <container-name>IC-trace Entity Bean</container-name> | <call-logging>false</call-logging> | | <sync-on-commit-only>true</sync-on-commit-only> | <insert-after-ejb-post-create>true</insert-after-ejb-post-create> | <call-ejb-store-on-clean>false</call-ejb-store-on-clean> | </container-configuration> | It now generates an update statement after each insert, even though nothing has changed in the entity. Also, the update statement always seem to update all fields, not just the changed fields. Is the dirty field handling different for these containers? Is there a way (configuration) to make sure the update behaviour is the same as for the other persistence managers? Thanks, Joachim View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3876076#3876076 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3876076 ------------------------------------------------------- This SF.Net email is sponsored by: NEC IT Guy Games. Get your fingers limbered up and give it your best shot. 4 great events, 4 opportunities to win big! Highest score wins.NEC IT Guy Games. Play to win an NEC 61 plasma display. Visit http://www.necitguy.com/?r=20 _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
