Community
Participate
Working Groups
There are several failures in the JPA FullRegressionTestSuite when running on MySQL. Diagnose these failures and ensure it is possible to run this suite on MySQL by either fixing the tests, fixing the underlying code, or changing the tests so log a warning and filing abug MySQL will be used as the test server for our nightly builds. In order to run automated testing we will need our test suites to run on an Open source DB. We have chosen MySQL because of its feature set (compared to Derby) and the accessibility of an instance of MySQL on the Eclispe build server.
Created attachment 82976 [details] patch for fixes that go in the eclipselink.jpa.test project
Created attachment 82977 [details] patch for fixes that go in the eclipselink.core project
Attaching two patch files 1. Fix to MySQL4Platform and DatabasePlatform to allow stored procedure calls to be written properly 2. Test fixes to throw a warning on an Oracle-only test and fix the cleanup of one test These changes solve all but one problem on MySQL in FullRegressionTestSuite. That problem is already solved by a separate transaction that is currently in progress.
Note: No new tests have been added for this bug because it specifically fixes broken test cases. To test the bug, run the JPA FullRegressionTestSuite on MySQL.
Created attachment 82988 [details] updated eclipselink.core changes after changes suggested by Guy Pelletier
The attached changes have been checked in. See above for description of changes and how it was tested. The JUnit JPA tests have been run against both Oracle and MySQL to verify this fix. Reviewed by Guy Pelletier
The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink