'error in running finalizer' when running MySQL.query with an 'update' command

[xximranxx]

Running MySQL.query with a 'update' command prints an error message (though does not end in an error) after gc() is run:

Doing the same with a 'select' command prints no error message

connection = MySQL.connect(ip,user,password,port=port,db=initial_schema)
command_update = "update table set value=2 where name='x'"
MySQL.query(connection,command_update)
gc() # prints 'error in running finalizer: Base.MethodError(f=typeof(Base.unsafe_convert)(), args=(Ptr{Void}, 0), world=0x0000000000005579)'

command_select = "select * from table where name='x'"
MySQL.query(connection,command_update)
gc() # prints nothing

This is with julia 0.6.2 and MySQL 0.5.2

[xximranxx]

Probably related to this function:

function mysql_binary_interpret_field(buf, T::Type)
    value = unsafe_load(convert(Ptr{T}, buf), 1)

    if typeof(value) == MYSQL_TIME
        if value.timetype == MYSQL_TIMESTAMP_DATE
            return convert(Date, value)

        elseif (value.timetype == MYSQL_TIMESTAMP_TIME
                || value.timetype == MYSQL_TIMESTAMP_DATETIME)
            return convert(DateTime, value)

        else
            throw(MySQLInterfaceError("MySQL Time type not recognized."))
        end
    end

    return value
end

Looks like buf==0 in the result the 'insert' command?

[essenciary]

I'm getting the same with "CREATE TABLE" queries, ex:

error in running finalizer: Base.MethodError(f=typeof(Base.unsafe_convert)(), args=(Ptr{Void}, 0), world=0x0000000000005dd0)

[essenciary]

Is there a way to stop these from being outputted? I'm running some large data import tasks and these just keep going on for minutes.

[quinnj]

Will be ultimately fixed by the package overhaul in #139