So I have a JDBC driver on the publisher channel. Optimization is turned off in the driver properties and for several attributes. However the driver still optimizes and will not push an add-value through if the value is already present. If all of the values are equal, then nothing happens.

This poses a problem, because the pub command transform never is evaluated.

If you want to only do something on a modify operation for example, then you have to do it after the matching rule has been evaluated. But if nothing is modifying until you hit the cmd-trans, then it never hits. If you put it in the event transform, then lets say an add is converted to a merge which nets no changes. So it doesn't fire because when it went through the event transform, it was an add not a modify, and because there are no net changes yet, the event transform never fires....

What am I missing here?