On Thu, Aug 03, 2017 at 01:11:59AM +1000, Craig Sanders wrote: > On Wed, Aug 02, 2017 at 04:53:02PM +0200, Christian Marillat wrote:
> > Could you try to fix the database with the following tool ?
> >
> > /usr/share/doc/mythtv-backend/contrib/maintenance/optimize_mythdb.pl
>
> # /usr/share/doc/mythtv-backend/contrib/maintenance/optimize_mythdb.pl
> Database schema 1346 not supported.
> Bindings support schema version 1348
>
> It only does a repair, optimize, and analyze on all the mythconverg
> tables, and then re-orders 3 of the tables. wouldn't be too hard to
> write my own script to do that, without using MythTV.pm. might
> do that tomorrow morning (getting late here)
I just did that, and same result:
017-08-03 01:38:22.309454 C [19935/19935] CoreContext dbcheck.cpp:437 (performActualUpdate) - Upgrading to MythTV schema version 1347
2017-08-03 01:38:22.309595 E [19935/19935] CoreContext dbcheck.cpp:411 (performUpdateSeries) - DB Error (Performing database upgrade):
Query was: n
Error was: Driver error was [2/1064]:
QMYSQL: Unable to execute query
Database error was:
You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '' at line 1
I wonder if it's the "master.toUtf8()," on line 3361 of
.../mythtv/libs/libmythtv/dbcheck.cpp ?
I already had a suspicion from the junk being printed that it had something to
do with a utf8 conversion gone wrong, and that's the only unusual difference
between the update for 1347 and 1348 (and all the others I looked at).
in fact, that's the only place that the '.toUtf8' method occurs in the entire
file.
