You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When running a Jakarta Data test against Oracle there is an issue with sorting not always being honored. To recreate, remove the @SkipIfSysProp(DB_Oracle) in JakartaDataRecreateServlet.java (open-liberty/dev/com.ibm.ws.jpa.tests.jpa_32_fat/test-applications/jakartadata/src/io/openliberty/jpa/data/tests/web/JakartaDataRecreateServlet.java)
@Test
@SkipIfSysProp({ DB_Oracle })
// Reference issue: https://github.com/OpenLiberty/open-liberty/issues/28289
// DB2 issue resolved (https://github.com/eclipse-ee4j/eclipselink/issues/2282), Oracle now has issues too
public void testOLGH28289() throws Exception {
Note: A similar issue was found in the DB2 database, which was resolved by this PR: #30076. The root cause was a problem with inserting values into DB2.
The text was updated successfully, but these errors were encountered:
When running a Jakarta Data test against Oracle there is an issue with sorting not always being honored. To recreate, remove the @SkipIfSysProp(DB_Oracle) in JakartaDataRecreateServlet.java (open-liberty/dev/com.ibm.ws.jpa.tests.jpa_32_fat/test-applications/jakartadata/src/io/openliberty/jpa/data/tests/web/JakartaDataRecreateServlet.java)
This individual test can be run against Oracle with the following command: ./gradlew com.ibm.ws.jpa.tests.jpa_32_fat:buildAndRun -Dfat.test.use.remote.docker=true -Dfat.bucket.db.type=Oracle
The test should fail because a Package with id 70077 is returned first when Package with id 70071 should be returned first.
You can find the recreate here : https://github.com/OpenLiberty/open-liberty/blob/integration/dev/com.ibm.ws.jpa.tests.jpa_32_fat/test-applications/jakartadata/src/io/openliberty/jpa/data/tests/web/JakartaDataRecreateServlet.java#L1132
Note: A similar issue was found in the DB2 database, which was resolved by this PR: #30076. The root cause was a problem with inserting values into DB2.
The text was updated successfully, but these errors were encountered: