They don’t do that anymore. You have to spoon feed them the issue on a silver platter or you’ll get shut down. Even for things that don’t work with the included example projects.
I find myself going around the triage system to get my issues actually looked at lately.
FWIW, according to the release notes, the only change involving MySQL between those versions is in 2025r2.
It’s certainly possible that Xojo updated the version of the plugin between those two versions, but I would expect that to be in the release notes somewhere.
If I remember correctly, the only time I’ve seen this error coming from MySQL was when I tried to execute a query where a double value had no trailing numbers. So the query contained something WHERE cost = 22. instead of WHERE cost = 22.00. Of course it was corrected, in my case, by changing that query to prepared statements (because it hadn’t been updated for some reason). But if you’re using prepared statements already, then I have no clue.
ups
and
ExecuteSQL(sql, CType( currValue, Double))
?
Thanks again to all for trying to help.
Note that William Yu just tagged the issue #80865 as reproductible and fixed for release 2026r1.