MySQL Bugs: #16916: binlog feature request -- DML and DDL logging control

Bug #16916	binlog feature request -- DML and DDL logging control
Submitted:	30 Jan 2006 21:37	Modified:	23 Aug 2006 4:36
Reporter:	Sheeri Cabral (Candidate Quality Contributor)	Email Updates:
Status:	Verified	Impact on me:	None
Category:	MySQL Server: Replication	Severity:	S4 (Feature request)
Version:	4.1, 5.1	OS:	Linux (Fedora Core 3 i86_64)
Assigned to:	Assigned Account	CPU Architecture:	Any

Description:
I'd like there to be an option to log DDL only or DML only, or both DDL and DML (current functionality).  

ie, I should be able to have one logfile with both DDL and DML (as binlog works now), or a logfile with only DDL (alter/create/drop table), or a logfile with only DML (update, insert, replace, etc), or 2 logfiles, one with DDL and one with DML.

How to repeat:
binlog just works that way, there are no 'levels' of reporting or options of what to report in each logfile.

Suggested fix:
option --
binlog-dml
or
binlog-dml=path
or
binlog-ddl
or
binlog-ddl=path
or
binlog
or
binlog=path

Any combination of the above should work.

Thanx!

Thank you for the bug report.

Triggers on information_schema tables, writing changes to a logging table, seems like one approach to doing this without touching the binary log, which is already critical for disaster recovery and replication.

Bug #60132 was marked as a duplicate of this one.