This select just verifies that the row still exists in the database, but is shouldn't be called in commit option A. I was under the impression that in commit option A didn't call the actual find if the bean was still in the ready cache. If this is happening after the bean is initially created or loaded (assuming you are not loading a ton of entities) then it is a bug. If so, can you post a simple bug report to source forge.
Thanks, -dain Ignacio Coloma wrote: > Hi, I am not doing anything weird enough to have this on the DB log when I > call some CMP findByPrimaryKey with Commit Option A: > > SELECT ID FROM FORMA_PAGO WHERE ID=81 > SELECT ID FROM COMERCIAL WHERE ID=4 > SELECT ID FROM CLIENTE WHERE ID=521 > SELECT ID FROM ZONA WHERE ID=1 > SELECT ID FROM PEDIDO WHERE ID=2166 > SELECT ID FROM PEDIDO WHERE ID=2166 > SELECT ID FROM PEDIDO WHERE ID=2166 > SELECT ID FROM PEDIDO WHERE ID=2166 > SELECT ID FROM PEDIDO WHERE ID=2166 > > I don't know if this is a bug or a feature. What is the purpose of checking > the pk value? The record doesn't get read, though. My app performance would > boost if these DB access could be avoided. > > PS: No CMR here :) > > ============================================ > Ignacio Coloma Escribano > Verdino Sistemas de Información > 629 151 669 - http://www.iverdino.com > > > _______________________________________________ > Jboss-development mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-development > _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
