Wondering if there is any update on this? This issue already seems quite old, but I still ran into it today with DbUnit version 2.5.4 and 2.6.
Is anybody aware of a workaround? Because the default IdentityColumnFilter does not work for me. Would like to try the extended one or write my own if needed.
Last edit: Luc Feys 2019-02-25
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi, since you have a broken scenario, can you make a test(s) that reproduce the problem and attach as a patch or open a git merge request? If you know the fix, please include that too. I will review, apply, and publish as 2.6.1-SNAPSHOT with the fix.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
OK. Had a look at it. Seems like there is already a test for this feature, which actually fails if it is activated. But currently it is disabled in the mssql41 profile because IDENTITY_INSERT is added to the list of unsupported features. Which is why this went unnoticed so far.
So I will try to come up with a fix.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
View and moderate all "bugs Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Bugs"
Missing from ALL_PROPERTIES that is
Wondering if there is any update on this? This issue already seems quite old, but I still ran into it today with DbUnit version 2.5.4 and 2.6.
Is anybody aware of a workaround? Because the default IdentityColumnFilter does not work for me. Would like to try the extended one or write my own if needed.
Last edit: Luc Feys 2019-02-25
Hi, since you have a broken scenario, can you make a test(s) that reproduce the problem and attach as a patch or open a git merge request? If you know the fix, please include that too. I will review, apply, and publish as 2.6.1-SNAPSHOT with the fix.
OK. Had a look at it. Seems like there is already a test for this feature, which actually fails if it is activated. But currently it is disabled in the mssql41 profile because IDENTITY_INSERT is added to the list of unsupported features. Which is why this went unnoticed so far.
So I will try to come up with a fix.
Good find, thank you for investigating.
I have a fix that works for me. Created a merge request.
Thanks! Please see MR comments.