MySQL STRICT mode errors

[teraßyte]

This is just a quick topic to mention that I often notice MySQL STRICT mode errors being reported. All IPS devs should switch their local servers to use it and that would avoid all reports about it, plus it's also better for coding too as you'll be sure you are always passing the proper data to MySQL without relying on MySQL having to "fix" it itself.

[AndyF]

I usually run my localhost permanently in strict mode so I can catch these occurrences at QA...

[teraßyte]

I usually run my localhost permanently in strict mode so I can catch these occurrences at QA...

To be picky, having the devs do it in the first place makes a beta version more stable too for QA. It's easier to catch those errors developing since you test much more extensively the new features while coding them :P

[bfarber]

We agree, and this is already done with our 4.0 development.

            if ( IN_DEV )
            {
                self::$multitons[ $identifier ]->query( "SET sql_mode=STRICT_ALL_TABLES" );
            }

[teraßyte]

Good :P