I think the optimization should to do the query and if the bean is not found remove it from the cache. Not really an optimization, but it keeps the cache clean.
-dain Scott M Stark wrote: > I would say the optimization is inconsistent with the commit option. > Why should a third party removing the bean from the store be any > different than an update to the record? > > xxxxxxxxxxxxxxxxxxxxxxxx > Scott Stark > Chief Technology Officer > JBoss Group, LLC > xxxxxxxxxxxxxxxxxxxxxxxx > ----- Original Message ----- > From: "Bill Burke" <[EMAIL PROTECTED]> > To: "Jboss-Dev" <[EMAIL PROTECTED]> > Sent: Thursday, March 14, 2002 9:46 AM > Subject: [JBoss-dev] is findByPrimaryKey optimization bad? > > > >>A BMP findByPrimaryKey is optimized to look in cache first for the active >>pk. If it is active in cache, then the pk is just returned, without >> > calling > >>ejbFindByPrimaryKey on the BMP. Should we do this for commit-options 'B' >>and 'C'? >> >>Here's the scenario somebody just submitted as a bug. They get a BMP (so >>it's active in cash). They manually delete the bean through straight JDBC >>(not calling bean.remove()). Then findByPrimaryKey(pk) returns a valid >>Entity when the entity is actually deleted in the DB. Maybe for commit >>option b and c we should not do this optimization? >> >>Same for CMP? >> >>What you all think? >> >> >>Bill >> > > > > _______________________________________________ > 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
