What ?

Add TRUNCATE and REPLACE keywords here.

Context

TRUNCATE is written in binlog as `Query` event type. Also commands like `REPLACE INTO` are written in binlog as `Query` event type in certain offerings of mysql such as percona.

Since `tableChanges` in a schema history record is populated only for create, alter or drop operations, the other operations if written in schema history, have to rely on DDL parser during the recovery phase, which is very slow in comparison to just deserializing `tableChanges`.