Mailing List Archive

Re: Ticket #6820: Invalid default values specified for some fields in MythArchive dbcheck.cpp
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.

Kind regards,

Jonathan
_______________________________________________
mythtv-dev mailing list
mythtv-dev@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev
Re: Ticket #6820: Invalid default values specified for some fields in MythArchive dbcheck.cpp [ In reply to ]
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
_______________________________________________
mythtv-dev mailing list
mythtv-dev@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev
Re: Ticket #6820: Invalid default values specified for some fields in MythArchive dbcheck.cpp [ In reply to ]
On Fri, 2009-08-07 at 23:17 +0200, Jonathan Martens wrote:
> On 7-8-2009 23:07, MythTV wrote:
> > #6820: Invalid default values specified for some fields in MythArchive dbcheck.cpp

> 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.

For correctness, those patches will be applied shortly. But you appear
to be running mysql in strict mode, which is not supported. It is likely
to cause the DB to get subtly corrupted leading to other problems which
will be difficult to debug. When running mysql in traditional mode the
problems you have helpfully identified will be silently ignored and
MythTV will run normally.

-- Daniel

_______________________________________________
mythtv-dev mailing list
mythtv-dev@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev
Re: Ticket #6820: Invalid default values specified for some fields in MythArchive dbcheck.cpp [ In reply to ]
On 08/07/2009 05:53 PM, Daniel Kristjansson wrote:
> On Fri, 2009-08-07 at 23:17 +0200, Jonathan Martens wrote:
>
>> On 7-8-2009 23:07, MythTV wrote:
>>
>>> #6820: Invalid default values specified for some fields in MythArchive dbcheck.cpp
>> 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.
>>
>
> For correctness, those patches will be applied shortly. But you appear
> to be running mysql in strict mode, which is not supported. It is likely
> to cause the DB to get subtly corrupted leading to other problems which
> will be difficult to debug. When running mysql in traditional mode the
> problems you have helpfully identified will be silently ignored and
> MythTV will run normally.

Or, if TRADITIONAL mode doesn't work, try just removing all modes:

sql-mode=""

and, really, if you find TRADITIONAL doesn't work, we'd appreciate
hearing so--as it seems no one really knows the minimum required as
(most?) everyone has been running with the defaults/without a mode set.

Thanks,
Mike
_______________________________________________
mythtv-dev mailing list
mythtv-dev@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev