MySQLi behaviors using Floating Point Numbers & Double where the column is an Integer
I'm curious about why each time I update an older behavior such as Update & Insert the new MySQLi version uses Floating point numbers as the type for the "Lookup column" ID and uses Double for the binding "Submit as:".
The columns being updated or inserted into, are int(11).
The conversion is working great and I can easily change it back to an int, but I was wondering if the extension was seeing something I am overlooking.
In most cases, the value is provided by a form field but sometimes it's a session. When I open the Update wizard and look in bindings, it shows int(11) in the type column but for each line it has Double selected instead of int. Do I have an issue somewhere I need to address? Would it even make a difference?
By the way, this has also happened when converting an older recordset that has a parameter compared to an id which is an integer. But this happens only occasionally.