If there is any interest, it would not be too difficult to port these tests to JPA.
Craig On May 27, 2008, at 6:09 PM, Patrick Linskey wrote:
Inconsistent in-memory entity model e.g. two-sides of relation set toinconsistent values or two fields mapping to same column set to differentvalues -- are corner cases and better be addressed by documenting.I believe that in general any inconsistencies in behavior with and without data caching enabled should be treated as bugs, not as mere documentation issues. As with all bugs, we must prioritize them appropriately, but they must have entries in the JIRA system, so that we don't just abandon the documented behavior as "correct".-Patrick On May 28, 2008, at 8:03 AM, Pinaki Poddar wrote:Inconsistent in-memory entity model e.g. two-sides of relation set toinconsistent values or two fields mapping to same column set to differentvalues -- are corner cases and better be addressed by documenting.refresh() behavior is significant and needs correction. Also, single, cleanentity refresh() is broken, I think, irrespective of Data Cache. -- View this message in context: http://www.nabble.com/datacache-tp17326391p17501098.html Sent from the OpenJPA Developers mailing list archive at Nabble.com.-- Patrick Linskey 202 669 5907
Craig Russell Architect, Sun Java Enterprise System http://java.sun.com/products/jdo 408 276-5638 mailto:[EMAIL PROTECTED] P.S. A good JDO? O, Gasp!
smime.p7s
Description: S/MIME cryptographic signature
