Method ambiguity error introduced in 2.3 for MySQL

[angusmoore]

Using DBInterface 2.3.0 and MySQL 1.1.2 and executing a query that doesn't take parameters (possibly other types of queries too, this is just where I hit the ambiguity error in my code):

import DBInterface, MySQL
con = DBInterface.connect(MySQL.Connection, "0.0.0.0", "user", "password", db = "fizzbuzz")
DBInterface.execute(con, "DROP DATABASE IF EXISTS fizzbuzz;")

Results in the following method ambiguity:

ERROR: MethodError: execute(::MySQL.Connection, ::String, ::Array{Any,1}) is ambiguous. Candidates:
  execute(conn::MySQL.Connection, sql::AbstractString, params; mysql_store_result) in MySQL at /home/angus/.julia/packages/MySQL/pLoSZ/src/execute.jl:132
  execute(conn::DBInterface.Connection, sql::AbstractString, params::Union{Tuple, AbstractDict, AbstractArray{T,1} where T, NamedTuple}) in DBInterface at /home/angus/.julia/packages/DBInterface/YRJF9/src/DBInterface.jl:119
Possible fix, define
  execute(::MySQL.Connection, ::AbstractString, ::Union{Tuple, AbstractDict, AbstractArray{T,1} where T, NamedTuple})

Downgrading DBInterface to 2.2 eliminates the ambiguity error and behaves as expected.

[quinnj]

Thanks for the report; this PR should fix it: #33.

[angusmoore]

Amazing, thanks for the quick response @quinnj, appreciate all the work you do!