update trigger don't fire on "replace"

This maybe is by design, but it is conceptually a bug.
A "replace" can be an insert or an update, and all update trigger must fire, but they are ignored. This problem makes it more cumbersome to write logic that catches what to do when existing data is there.
Please consider extending update triggers to the statement "replace" when the primary key is there already.