CLOB support is broken in <loadUpdateData>
, because LoadUpdateDataChange
does not support prepared statements:
@Override
protected boolean hasPreparedStatementsImplemented() { return false; }
This is not documented, which is why I consider it a bug (note that loadUpdateData
has an attribute named usePreparedStatements
which effectively does nothing because of this bug).
How else can I solve the problem of multiple optional data feeds with potential intersections? If I use <loadData>
, which does support CLOB files, I run into unique key violations that way.
I know I could choose the hard way and use plain SQL or a precondition for each record to be inserted to check if the record already exists, but that would bloat the changeSet and make it pretty much unmaintainable.