Aha!<br><br><br>You're right... I had my versionnumbers mixed all up :P<br><br>Now it's starting to make more sense to me! So we're actually moving away from the brokeness, and not towards it.<br><br>Though, I still wonderif it will be possible to use UTF8 (assuming it's done for all: "Server characterset, Db characterset, Client characterset and Conn. characterset") ?<br>
<br><br><div class="gmail_quote">2009/3/30 Michael T. Dean <span dir="ltr"><<a href="mailto:mtdean@thirdcontact.com">mtdean@thirdcontact.com</a>></span><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="im">On 03/30/2009 04:08 AM, Glenn Sommer wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
I saw at <a href="http://www.mythtv.org/wiki/Fixing_Corrupt_Database_Encoding" target="_blank">http://www.mythtv.org/wiki/Fixing_Corrupt_Database_Encoding</a> that mythtv 0.22 can only handle latin1 connections to the MySQL database - but uses UTF8 internally (Actually it writes UTF8 into the database).<br>
</blockquote>
<br></div>
You've got your versions wrong.<br>
<br>
MythTV 0.21-fixes and below use UTF-8. MythTV 0.21-fixes and below stores UTF-8 in the database. MythTV 0.21-fixes and below tells MySQL that the text columns are actually latin1. MythTV 0.21-fixes and below does /not/ use latin1.<br>
<br>
MythTV trunk use UTF-8. MythTV trunk stores UTF-8 in the database. MythTV trunk tells MySQL that the text columns are actually UTF-8. MythTV trunk does /not/ use latin1.<br>
<br>
In other words, the /only/ difference is that MythTV 0.21-fixes and below doesn't tell MySQL what encoding is actually in use.<div class="im"><br>
<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
I don't understand why MythTV doesn't use UTF8 all the way - so no encoding/decoding is required when talking to the database?<br>
Also, putting UTF8 text in a latin1 database is in my opinion wrong...<br>
</blockquote>
<br></div>
It does. It used to store UTF-8 data in MySQL without /allowing/ MySQL to know that the data inside was UTF-8 to reduce the size of the database columns and indices significantly for a database where MySQL knows the data is UTF-8 if most of the data is actually latin1 (as it is for a /large/ number of users). And, MythTV had to wait until MySQL had sufficient support for sufficiently-long columns and indices, and we've only recently started /requiring/ versions of MySQL that do.<div class="im">
<br>
<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Other clients will be unable to read the data correctly (like phpMyAdmin for example).<br>
</blockquote>
<br></div>
Well, the /only/ client that should be using MythTV database is really MythTV or other clients designed for use with MythTV (and, therefore, aware of the encoding). And, that being said, if you knew what you were doing, you could actually make it work rather easily even in "other" clients that didn't realize what was going on.<div class="im">
<br>
<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
In my opinion latin1 text is for latin1 databases - and UTF8 text is for UTF8 databases...<br>
<br>
Surely I must be missing something here?<br>
</blockquote>
<br></div>
Yes. You're missing an understanding of what that page actually said. :)<div class="im"><br>
<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
What is the reason for breaking the database - instead of fixing MythTV?<br>
</blockquote>
<br></div>
Again, re-read that page. We're simply telling people who have completely broken data (because they had configurations where they told MySQL to ignore the database schema's defined charset, so MySQL did character-set conversions it should /not/ have done) that they cannot successfully upgrade their databases until they fix the data.<br>
<br>
Mike<br>
_______________________________________________<br>
mythtv-users mailing list<br>
<a href="mailto:mythtv-users@mythtv.org" target="_blank">mythtv-users@mythtv.org</a><br>
<a href="http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users" target="_blank">http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users</a><br>
</blockquote></div><br>