The least disruptive method would be to use the general query log. The query log output can be a database table or a log (text) file; however it does not support filtering by DML operation or database so all SELECT statements on all databases will be logged as well. Obviously you can filter the logging output later.
The session sql_log_off variable can be set to ON or OFF to disable or enable general query logging for the current connection.
This means that with some injected logic, you could conceivably disable logging for SELECTs.
Another solution is to use triggers on UPDATE, INSERT, DELETE. This will directly affect the database in question but not other databases running in the same instance.
See also SO questions here and here.