Hi, Justin! On Dec 11, Justin Swanhart wrote: > I disagree about as vehemently as possible. You should get a warning on > comparisons between incompatible types that cause float conversions. You > get unexpected wrong results otherwise. The MySQL warning is therefor > critical.
That would be true if you get unexpected wrong results otherwise. But here you don't (and no float conversion either, as far as I know). In this query no explicit type conversion is requested and internal type conversons for comparison purposes should not generate warnings as long as they stay completely internal. Wrong results means that the internal implementation is leaking into the user space - and that's when you start needing a warning. Regards, Sergei _______________________________________________ Mailing list: https://launchpad.net/~maria-discuss Post to : maria-discuss@lists.launchpad.net Unsubscribe : https://launchpad.net/~maria-discuss More help : https://help.launchpad.net/ListHelp
