Unable to clean database due to Foreign Key Constraint Violation

[paulovictorv]

Hi, I'm having a problem with I suppose is with this extension, not the underlying DBUnit infrastructure. When the extension tries to clean the database after a test method, it fails to clean the database due to a foreign key constraint violation. The test method is as follows:

@test
@ShouldMatchDataSet("datasets/users-company.xml")
public void saveClientWithCompany(){
Client s = new Client();
s.setLogin("solicitante1");
s.setEmail("[email protected]");
s.setNome("paulo");
s.setSenha("123456");
s.setDepartamento("dep");
Company e = new Company();
e.setNome("empresa");
Set set = new HashSet();
set.add(s);
e.setListClient(set);
s.setCompany(e);
solMgt.saveClient(s);
}

As you can see, there is a ManyToOne relation between Client and Company, and there is a constraint in this relationship.
I tried to use @ApplyScriptBefore to deactivate the constraint check, but with no success. Apparently, the extension does not run the script, since if I run the command by hand it works as it should.

[bartoszmajsak]

Would it be possible to attach test case and used files in the forum community.jboss.org in arquillian space? thx!

[bartoszmajsak]

or ideally extracted project with failing test :)

[paulovictorv]

Of course. I will open a new thread there :)

[bartoszmajsak]

thank you, I will take care of the rest

[paulovictorv]

There : https://community.jboss.org/thread/213209 :)

[paulovictorv]

Hi, did you get a chance to see the topic? Is there something missing? Thanks

[bartoszmajsak]

Sorry, not yet. At Devoxx at the moment, but hopefully I will have time for that today :)

[bartoszmajsak]

The test itself is not that helpful. Could you provide entities as well? Also which version of Arquillian and Persistence Extension are you using? Which MySQL version and AS?

[bartoszmajsak]

Are you still facing the problem? Otherwise I would like to close this issue

[shoteff]

Hi,
I also faced the foreign key violation on DB cleanup. I'm using JSON datasets, MySQL DB with referential integrity enabled. The inserts into the DB are ordered as the definitions in the dataset(s). In order to avoid foreign key violations I have to first define the parent side of the relations (I'm assuming that there are no circular deps), then the childs. Cleaning up the data should be done in reverse order (not like it is currently in the order the data is inserted). At least from my point of view this can solve the problem in the most cases