[eclipselink-dev] Fix for bug 361860 checked in

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]

[eclipselink-dev] Fix for bug 361860 checked in

From: David Minsky <david.minsky@xxxxxxxxxx>
Date: Mon, 07 Nov 2011 16:16:16 -0500
Delivered-to: eclipselink-dev@xxxxxxxxxxx
List-archive: <https://dev.eclipse.org/mailman/private/eclipselink-dev>
List-help: <mailto:eclipselink-dev-request@eclipse.org?subject=help>
List-subscribe: <https://dev.eclipse.org/mailman/listinfo/eclipselink-dev>, <mailto:eclipselink-dev-request@eclipse.org?subject=subscribe>
List-unsubscribe: <https://dev.eclipse.org/mailman/options/eclipselink-dev>, <mailto:eclipselink-dev-request@eclipse.org?subject=unsubscribe>
User-agent: Mozilla/5.0 (Windows NT 5.1; rv:7.0.1) Gecko/20110929 Thunderbird/7.0.1

Bug 361860 - Using ScrollableCursor with 1:M joining produces incorrect results
https://bugs.eclipse.org/bugs/show_bug.cgi?id=361860

- Multiple fixes to ScrollableCursor to resolve data consistency issues when performing joined queries
- Fix to ScrollableCursor retrievePreviousObject() to prevent a NPE when executing a query with joining
- Added ScrollableCursorJoiningVerificationTest to QueryFrameworkTestSuite

Checked into trunk (2.4) at revision: 10341

Reviewed: Andrei
Core LRG & JPA LRG on MySQL & Oracle

Prev by Date: [eclipselink-dev] 2.4.0 M5 complete...
Next by Date: [eclipselink-dev] BUILD STATUS:: trunk nightly build has test failures!
Previous by thread: [eclipselink-dev] 2.4.0 M5 complete...
Next by thread: [eclipselink-dev] Fix for bug 362804 checked in
Index(es):
- Date
- Thread

Breadcrumbs