Bug #53425 LOAD DATA, START TRANSACTION and HANDLER filters don't work

Description:
Using 

  LOAD DATA
  START TRANSACTION
  HANDLER ...

filters don't show any of these commands.

The query-type sent by the agent for this queries doesn't match when the UI filters on:

  LOAD DATA INFILE ... -> query-type="LOAD" != filter="LOAD DATA"
  START TRANSACTION -> query-type="START" != filter="START TRANSATION"
  HANDLER CLOSE -> query-type="HANDLER" != filter="HANDLER CLOSE"

How to repeat:
Runs queries throw the QUAN-enabled proxy and filter by them in the UI.

Suggested fix:
Fix the UI to filter on the "LOAD" and "HANDLER".
Fix the Agent to use "BEGIN" as query-type in case of "START TRANSACTION".

Mark Matthews writes: 
Are we talking filter-only on these "mappings"? (my preference btw). I think we should retain what the statement was classified as originally, as quite a few of them have the same starting token, but different semantics, so they're not really the same statements in some contexts.

Josh Sled writes: 
revno: 8074
revision-id: jsled@asynchronous.org-20100511204806-4jqbi5jqqg1co7ov
parent: markm@sun.com-20100511204529-gtc7dswm29dfhq2r
committer: Josh Sled <jsled@asynchronous.org>
branch nick: 2.2
timestamp: Tue 2010-05-11 16:48:06 -0400
message:
  EM-4471: LOAD DATA -> LOAD, START_TRANSACTION -> START, HANDLER ... {OPEN,CLOSE,READ} -> HANDLER for statement filter types

Andy Bang writes: 
In build 2.2.1.1718.

Diego Medina writes: 
Verified fixed on 2.2.1.1718

A note has been added to the 2.2.1 changelog: 

       The filters for <literal>LOAD DATA                                                                                               
        INFILE</literal>, <literal>START TRANSACTION</literal>,                                                                          
        and <literal>HANDLER CLOSE</literal> statements in the Query                                                                     
        Analyzer interface did not filter statements correctly.