{"push_id":685559721,"size":1,"distinct_size":1,"ref":"refs/heads/master","head":"919ff8478abafdf5ee47a3a27b6f718c6c18af82","before":"00bce1639666aa4ba8dc360f351f4253aee59728","commits":[{"sha":"919ff8478abafdf5ee47a3a27b6f718c6c18af82","author":{"email":"678f57847e0f3276897b583a27f63d19955c45bf@oracle.com","name":"David Minsky"},"message":"Fix for bug 464088\n- History policy: relationship query can be initialized incorrectly with history SQL when relationship is eager\n- Change to ForeignReferenceMapping valueFromRowInternal() to not allow a historical query to be permanently set as a ForeignReferenceMapping's selection query -- instead, the historical query is cloned for execution.\n- Added specialized entities: Oyster (non-historized) & Pearl (historized), with support class: AdvancedHistoryCustomizer\n- Testing: testHistoryRelationshipQueryInitialization added to AdvancedJPAJunitTest, tested against Oracle & MySQL\n\nSigned-off-by: Petros Splinakis <petros.splinakis@oracle.com>","distinct":true,"url":"https://api.github.com/repos/eclipse/eclipselink.runtime/commits/919ff8478abafdf5ee47a3a27b6f718c6c18af82"}]}