[mythtv-users] database upgrade fail: schema 1160 to 1244

[Michael T. Dean]

On 12/08/2009 11:40 PM, Jeff Bryner wrote:
> Just updated mythtv from 20 to 22 and am stuck on the database update.
>
> Here's the error:
>
> 2009-12-08 20:24:31.875 DB Error (Performing database upgrade):
> Query was: `/w
> 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 '`/w' at line 1
>
> new version: 1170
> 2009-12-08 20:24:31.875 Database Schema upgrade FAILED, unlocking.
> 2009-12-08 20:24:31.875 Couldn't upgrade database to new schema
>
>
> The odd character makes me think I may be a victim of the mysql 
> latin/utf collation bug (I'm gentoo),

No, the problem is that you're using an old version of 0.22-fixes (or 
0.22 release tarball).  You need to update to current 0.22-fixes (at 
least r22550).

> but I though skipping .21 and moving to .22 would avoid that no?

No, it won't avoid it.  The failure (and notification of failure) just 
won't hit until it's doing the post 0.21 upgrades.

> Anyone recognize this as either a collation-related item or an 
> existing bug? I searched the archives to no avail..but I did find 
> other things I'm going to run into.
>
> FWIW here's my mysql info:
> mythtv # mysql -umythtv -p mythconverg -e 'status;'
> Enter password:
> --------------
> mysql  Ver 14.12 Distrib 5.0.84, for pc-linux-gnu (x86_64) using 
> readline 6.0
>
> Connection id:          39
> Current database:       mythconverg
> Current user:           mythtv at localhost
> SSL:                    Not in use
> Current pager:          stdout
> Using outfile:          ''
> Using delimiter:        ;
> Server version:         5.0.84-log Gentoo Linux mysql-5.0.84-r1
> Protocol version:       10
> Connection:             Localhost via UNIX socket
> Server characterset:    utf8
> Db     characterset:    utf8
> Client characterset:    utf8
> Conn.  characterset:    utf8
> UNIX socket:            /var/run/mysqld/mysqld.sock
> Uptime:                 9 hours 5 min 4 sec
>
> Thanks for any guidance! 

If that's the configuration of the server you were running 0.20 on, 
you'll definitely have charset issues.  You should a) upgrade to current 
0.22-fixes, and b) go back to the 0.20 backup and try 
http://www.mythtv.org/wiki/Fixing_Corrupt_Database_Encoding .

Mike