Bill Burke wrote: > 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?
As I said in a comment on the bug, that optimization breaks many scenarios that force people to use B and C. If the same tables are being used by a legacy application which does deletes, you wind up lying to your users. Bad Thing. -danch _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
