• cmiller@zippy.cornsilk.net's avatar
    Bug#36570: Parse error of CREATE PROCEDURE stmt with comments on \ · 573828aa
    cmiller@zippy.cornsilk.net authored
    	slave
    
    The stored-routine code took the contents of the (lowest) parser
    and copied it directly to the binlog, which causes problems if there
    is a special case of interpretation at the parser level -- which 
    there is, in the "/*!VER */" comments.  The trailing "*/" caused
    errors on the slave, naturally.
    
    Now, since by that point we have /properly/ created parse-tree (as 
    the rest of the server should do!) for the stored-routine CREATE, we
    can construct a perfect statement from that information, instead of
    writing uncertain information from an unknown parser state.  
    Fortunately, there's already a function nearby that does exactly 
    that.
    ---
    Update for Bug#36570.  Qualify routine names with db name when
    writing to the binlog ONLY if the source text is qualified.
    573828aa
sp_head.cc 96.7 KB