Michal Šída

Some simple workarround (patch) prepared in the related bug.

There is a simple workarround. I do not use dbUnit on my actual project, so I can not test it, could you run some tests and try it in some real project, please?

See my comment in the related bug.

Hi, I supposed, that three parameter of setNull is safe to call with null value in third parameter and it will be ignored by the jdbc driver (see specification ). But if it causes some problems it looks safe to change the implementation of PreparedBatchStatement.java and SimplePreparedStatement.java, that they will call 2-parameter variant in case that dataType.getSqlTypeName() returns null. The 3-paramater variant will be used only for non-null dataType.getSqlTypeName() return value - and the only...

I tried snapshot version dbunit-2.5.3-20160522.043317-16.jar and it fixed both my...

I tried snapshot version dbunit-2.5.3-20160522.043317-16.jar and it fixed both my...

I tried snapshot version dbunit-2.5.3-20160522.043317-16.jar and it fixed both my...

I prepared a fix for both problems. It allows NULL value for column with XMLTYPE...