[mythtv] Ticket #6820: Invalid default values specified for some fields in MythArchive dbcheck.cpp

[Michael T. Dean]

On 08/07/2009 05:17 PM, Jonathan Martens wrote:
> On 7-8-2009 23:07, MythTV wrote:
>> #6820: Invalid default values specified for some fields in 
>> MythArchive dbcheck.cpp
> [...]
>> Changes (by danielk):
>>
>>    * priority:  blocker =>  trivial
>>    * severity:  medium =>  low
>>    * milestone:  0.22 =>  unknown
>
> If I may be so bold... what is the reason for assigning them to an 
> unknown milestone and assigning them non-blockers? This one, as well 
> as issue 6802 and 6811, stop internal database upgrades and therefore 
> hamper functionality AFAICT.
>
> As there are patches applied to all of them so they could be easily 
> fixed or am I missing some vital information here, if so please fill 
> me in. 

Turn off MySQL's STRICT* mode.

http://dev.mysql.com/doc/refman/5.0/en/faqs-sql-modes.html
http://dev.mysql.com/doc/refman/5.0/en/server-sql-mode.html

There's a /lot/ of SQL code in Myth that doesn't conform to strict 
standards.  We appreciate your finding/patching/reporting these issues, 
but if you run Myth on a database with STRICT* mode enabled, it will 
likely break things.

Since you're the first person to report these issues in the 5+ years 
I've been using Myth, I'm guessing that every single Linux distribution 
ships with a MySQL configuration that does not enable STRICT modes.  I 
would have assumed that the Windows install of MySQL would be the same, 
but if not, the Windows installer script should probably be fixed to 
unset STRICT mode.  After all, the MySQL server default configuration is 
no modes set--which is the most permissive--so some installer is either 
installing a modified my.cnf or starting mysqld with 
--sql-mode="<something>" specified.

Mike