One more thing...Maybe we shouldn't be worrying about straight JDBC calls corrupting the cache? If somebody wants to do this, then fuck em. They do so at there own risk.
Opinions? Thanks, Bill > -----Original Message----- > From: Bill Burke [mailto:[EMAIL PROTECTED]] > Sent: Thursday, March 14, 2002 12:46 PM > To: Jboss-Dev > Subject: 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
