Description Adrian Goerler 2009-11-19 11:49:11 EST

In the test suite eclipselink.jpa.test, there are two entities 

org.eclipse.persistence.testing.models.jpa.ddlgeneration.MachineState

and 

org.eclipse.persistence.testing.models.jpa.cascadedeletes.MachineState.

Both are mapped to the table "MACHINESTATE". In the "cascadedeletes" model there is additionaly a foreign key constraint referencing the table "MACHINESTATE".

Executing the eclipselink.jpa.test test suite leaves the table "MACHINESTATE" in the state corresponding to the "cascadedeletes" model with the fk constraint on it.

If I execute the testsuite again, the "ddlgeneration" model cannot be properly as the table "MACHINESTATE" can't be dropped/created as there is a constraint on the table not known to the "ddlgeneration" model. Consequently, a test fails.

To fix this, I propose to rename one version of "MACHINESTATE" to "MACHINE_STATE".