[mythtv-users] Current Trunk, mysql latin1 and gentoo oddities

[Michael T. Dean]

On 03/11/2009 11:56 AM, Wayde Milas wrote:
> I'm hoping someone  can help me. I'm currently struggling to get an
> initial mythconverg database setup for svn trunk. I'm getting the
> following error:
>
> 2009-03-09 19:15:18.762 The database seems to be empty - not attempting
> a backup
> 2009-03-09 19:15:18.772 Newest Schema Version : 1232
> 2009-03-09 19:15:18.773 Inserting MythTV initial database information.
> 2009-03-09 19:15:18.773 New DB connection, total: 3
> 2009-03-09 19:15:18.774 Connected to database 'mythconverg' at host:
> localhost
> 2009-03-09 19:15:18.774 Upgrading to schema version 1226
> 2009-03-09 19:15:18.774 DB Error (Performing database upgrade):
> Query was: ALTER DATABASE mythconverg DEFAULT CHARACTER SET utf8;
> Error was: Driver error was [2/1295]:
> QMYSQL3: Unable to prepare statement
> Database error was:
> This command is not supported in the prepared statement protocol yet
>
> new version: 1226
> 2009-03-09 19:15:18.774 Database Schema upgrade FAILED, unlocking.
> 2009-03-09 19:15:18.774 Couldn't upgrade database to new schema.
>
>
> I read a thread a while back stating that mysql was configured wrong
> during compile (in gentoo) and that it left the latin1 flag out. I've
> re-compiled with the latin1 flag in. I've also gone into my.cnf and
> changed all the utf8 references to latin1. Still no dice.
>
> Any idea whats going wrong here? I'm guessing it has something to do
> with character encoding but I can't figure out what...

That's unrelated to the Gentoo configuration of MySQL server.

It's actually a bug in Qt 4.5.0.  You can either run Qt 4.4.x or apply a 
patch to Qt.  I have such a patch, but am still trying to create a 
reproducible test case before uploading the patch/reporting the bug to 
Qt's bug tracker.  I'll post more details once I get the bug reported.

(Great timing, BTW, as I just tracked down that bug yesterday.  :)

As for the Gentoo character set issues, see 
http://www.mythtv.org/wiki/Fixing_Corrupt_Database_Encoding , but note 
that you /only/ need to do that (and only need to compile MySQL with the 
+latin1 USE flag) if you're using -fixes and/or you already have a 
database created from a 0.21-fixes or below MythTV system.

On trunk (when starting your DB with trunk), you can use the default 
Gentoo configuration of MySQL (with -latin1).

Mike