In auditors we can raise a 'Reject' exception.
This should have the effect that changes are *NOT* committed to the
database.

In the current development version such an exception will commit changes
to the database anyway although an exception is raised.

I've gone back to the version e1e40674a0bc from end of 2016 -- I'm
running that version on a production system -- which doesn't show this
behaviour.

I haven't triaged this yet to find out when this change was introduced.

IMO this is release-critical as many auditors depend on the ability to
prevent erroneous changes to the database.

--
Ralf