3 Replies Latest reply on May 6, 2005 11:40 AM by Joachim Van der Auwera

    jdbc2 pm and dirty flags

    Joachim Van der Auwera Expert

      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