#185 Do not explicitly insert null into NOT NULL columns with DEFAULT

[Mattias Jiderhamn]

Continuation of feature request #184 (https://sourceforge.net/p/dbunit/feature-requests/184/):
If column is defined as NOT NULL and has a DEFAULT value, dbUnit should not explicitly include null value in insert operations, but instead skip the column to trigger the default.

[Mattias Jiderhamn]

Applied is a patch that implements this

[Mattias Jiderhamn]

[double post]

[Mattias Jiderhamn]

Is there any reason this patch has not been applied yet?

[Jeff Jensen]

Missed it and time. "Ping" on an issue is not a problem!

[Mattias Jiderhamn]

Created a Merge Request also, in case that speeds things up: https://sourceforge.net/p/dbunit/code.git/merge-requests/7/

[Jeff Jensen]

Thank you for adding this, with test.
(yes, merge request makes it easier!)

[Mattias Jiderhamn]

It should be noted that the INSERT statement generated is based on the first record in a dataset, which means that if the first record has a value for the NOT NULL + DEFAULT column, then an explicit NULL will be inserted for records without a value (potentially causing an error).

[Jeff Jensen]

Thanks for mentioning, good idea. We should add a note like this to the docs. Where do you suggest?