Comment 3 for bug 253217

One reason we don't do it in the database layer is that we batch things together into one event. For example, if we edit both the status and importance, we issue only one event instead of two.

The other quite important reason is that in the database we don't always have access to the user doing the change. For example, if you set an attribute on the object, the database layer don't know which user did the change.

Not to mention that changing the way we currently issue notification would be a lot of work; a lot more than making sure that the API layer issues events. This is quite a serious bug, and it should get fixed before people start to use the API seriously.