On the extractor side, there is an optimization that indicates that all values
of columns (or keys) are NULL.
However, on keys, there is an issue where all values are set to null whereas
this is not truly the case (some values should not be null)
As a consequence, some statements will fail to update or delete rows and the
log will show :
WARN applier.JdbcApplier UPDATE or DELETE statement did not process any row...
Original issue reported on code.google.com by stephane...@continuent.com on 7 Aug 2013 at 10:00
Original issue reported on code.google.com by
stephane...@continuent.com
on 7 Aug 2013 at 10:00