I'm working with the 1355 patched, trunk codebase (as of 4/16) and althought 
the 1355 patch no longer requires all independent, lazy-loaded objects to be 
loaded in a relationship tree, read-only queries are now resulting in updates 
to the objects at the time db.commit() is called.  This is particularly bad 
considering the value of the course's city independent object is getting nulled 
out.  Should 1355 be reopened or a new bug opened?
 
The original test case 
(LazyLoadRelationshipTest.testLoadLazyCollectionWithoutLazyOneToOne) can be 
updated with to demonstrate the issue:
 
public void testLoadLazyCollectionWithoutLazyOneToOne() throws Exception {
... original test case...
 
//Make sures there aren't any side effects (i.e. independent objects getting 
updated)
        database = jdoMgr.getDatabase();
        database.begin();
        query = database.getOQLQuery(oql);
        query.bind(1);
        queryResults = query.execute(AccessMode.ReadOnly);
        course = null;
        while (queryResults.hasMore()) {
            course = (GolfCourse) queryResults.next();
            City city = course.getCity();
            assertNotNull("Golf Course no longer has a relationship to 
independent object not loaded above", city);
            assertEquals("GolfCourse's associated independant city has 
changed!", new Long(1), city.getId());
        }
        database.commit();
        database.close();
 }
 
Thanks,
Jon

-------------------------------------------------
If you wish to unsubscribe from this list, please 
send an empty message to the following address:

[EMAIL PROTECTED]
-------------------------------------------------

Reply via email to