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

[Michael T. Dean]

On 03/12/2009 03:31 PM, Tom Dexter wrote:
> On Thu, Mar 12, 2009 at 3:00 PM, Michael T. Dean wrote:
>   
>> OK.  Just to clarify.  The MySQL Server configuration requirement (that most
>> Gentoo users' MySQL servers don't meet--i.e. configuring the server to use
>> the latin1 character set) is a requirement for -fixes databases, only.
>>  (I.e. you would need to have the proper configuration when you import your
>> -fixes database, but as soon as you run trunk's mythtv-setup to upgrade the
>> database, you can change the MySQL server configuration as desired.)
>>     
> Hi Mike...I remember when this came up earlier.  For those of us
> running 0.21-fixes with the default Gentoo UTF8 setup (where the
> server defaults are UTF8 but the database was in fact created with
> wc.sql with the latin1 defaults for mythconverg), does the statement
> you made here still apply?:
>
> http://www.gossamer-threads.com/lists/mythtv/users/362243#362243
>
> ...and I guess that what you're saying is that, whenever I upgrade to
> any upcoming version 0.22, I'd need to make sure that my my.cnf was
> set up so as to default to latin1 for everything in order for the
> conversion to work correctly, but can be set to UTF8 after?  I just
> wanted to be sure.
>
> The settings in my.cnf certainly get confusing enough:
>
> There are default-character-set listed under [mysql], [mysqladmin],
> [mysqlcheck], [mysqldump], [mysqlimport], [mysqlshow], and [mysqld],
> in addition to the character-set-server setting under [mysqld].
> Though some of those surely wouldn't affect the upgrade, I'd assume
> the safe bet is make sure they're all latin1 for the upgrade.

Best information is at 
http://www.mythtv.org/wiki/Fixing_Corrupt_Database_Encoding .

Section 2 ( 
http://www.mythtv.org/wiki/Fixing_Corrupt_Database_Encoding#Determining_if_your_database_is_misconfigured 
) will tell you whether you need to do anything before upgrading.

Before 0.22 is released, the patch on #5070 ( 
http://svn.mythtv.org/trac/ticket/5070 ) will be applied, and will 
prevent a user with a corrupt database from upgrading (until they've 
fixed the DB).  So, basically, when 0.22 is ready, you shouldn't be able 
to accidentally break your DB by doing an upgrade.  If you think you 
might be affected, but want to upgrade to trunk, apply the patch in #5070 .

If your DB is corrupt, you will need to follow the rest of the 
instructions at 
http://www.mythtv.org/wiki/Fixing_Corrupt_Database_Encoding , assuming 
the process is not taken care of for you by packager scripts.

Mike