-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Rollback not working with postgresql 9.1 #25
Comments
@regis-leray Is this issue still relevant? |
The rollback doesnt work, my fix is just a hack. |
Have you tried with the latest version of Spring DBUnit? (1.3.0) |
Hmm don't bother testing with another version. It seems that the way you fixed the problem should be done in the background for you. The thing is that if you don't specify the tearDownOperation, nothing will be done. |
@regis-leray Could you test the version given by branch fix-25 (link above this comment)? I think I've nailed the problem, but as I didn't write the whole library, I might have missed something. I don't have anything to test with me :) |
@regis-leray Have you had time to try with the fix I've pushed? |
sorry i dont use anymore this library. And i dont have the project setup on my machine. But you can create a integration test like i did. With a simple object and in memory database Implements the same as my example in unit test |
Will do, thanks for the test case! |
@rsertelon, can you tell me when you will release a new version with this bug fix? |
It try to use the rollback feature but it doesnt seems to work.
im using
Here my log
https://gist.github.com/regis-leray/f5fbd8aa4f6e5e475057
In my junit test
in My applicationContext-datasource xml file
Also the transaction management is working well my test shouldSaveConfiguration() doesnt create a record in the database, but the dbunit dataset is not remove from the database table.
If i have time , l will run the unit test of spring dbunit with postgres 9 with the rollback feature
PS:
I find a way to resolve that with the dbunit feature
The text was updated successfully, but these errors were encountered: