Details
-
Task
-
Status: Open (View Workflow)
-
Minor
-
Resolution: Unresolved
-
None
-
None
Description
Choosing from the application layer the type of binlog format can be a requirement for the DBA that would like to enforce a specific default format , but wan't to act differently in some batch or a set of tables used by an application.
Unfortunately the only way to do this is by giving the application the SUPER privilege
set session binlog_format=ROW; break without the super priv .
Giving that the super privilege can lead to data corruption by simply changing the replication position , this is a major security concern that would be address by introducing a BINLOG FORMAT privilege that will only affect the session binlog_format change.
This privilege can be split again in BINLOG FORMAT ROW or BINLOG FORMAT STATEMENT to enable one or the other move , script that specifically need to run statement based like online alter can than be restricted to what format they need without being able to impacting the default by mistake.