[mythtv-commits] Ticket #2775: utf8 query inside mythfrontend fails with german umlaut

MythTV mythtv at cvs.mythtv.org
Thu Mar 8 12:25:01 UTC 2007


#2775: utf8 query inside mythfrontend fails with german umlaut
-------------------------------------+--------------------------------------
 Reporter:  tormen <tormen at gmx.net>  |        Owner:  ijr     
     Type:  defect                   |       Status:  reopened
 Priority:  minor                    |    Milestone:  unknown 
Component:  mythtv                   |      Version:  0.20    
 Severity:  medium                   |   Resolution:          
-------------------------------------+--------------------------------------
Changes (by stuartm):

  * status:  closed => reopened
  * resolution:  fixed =>


Old description:

> Hi... I am not sure if this might be a bug inside mythtv:
>
> I have a gentoo installation:
> * dev-db/mysql
>      Installed:           5.0.26-r1
>
> * media-tv/mythtv
>      Installed:           0.20_p11626
>
> I tried to create a record rule today and there was a german umlaut in
> the record rule:
>         program.title LIKE 'Ein Fall für den Fuchs: %'
>
> After pressing test, I received the error message: "illegal mix of
> collations
> (latin1_swedish_ci,IMPLICIT) and (utf8_general_ci,COERCIBLE) for
> operation
> 'like'".
>
> I tried the sql command which mythfrontend supplied together with this
> error
> message inside "mysql" on the console:
>
> mysql> SELECT NULL FROM (program,channel) WHERE  program.title LIKE 'Ein
> Fall
> für den Fuchs: %';
> ERROR 1267 (HY000): Illegal mix of collations
> (latin1_swedish_ci,IMPLICIT) and
> (utf8_general_ci,COERCIBLE) for operation 'like'
>
> But then I changed the setting inside /etc/my.cnf:
> I changed the default-character-set from utf8 to latin1 within the
> [mysql]
> section.
>
> Then mysql did NOT complain anymore!
>
> But mythfrontend still does?!
>
> Is this a bug inside mythfrontend in the way it contacts the database or
> is it
> another setting inside my.cnf that is misssing?!
> It must be possible for mythfrontend to also send this query successfully
> like it is now possible with the mysql commandline client, or?
>
> I also tried to set the default-char-set for all sections to latin1
> inside the my.cnf, but the error message inside mythfrontend stayed.
>

> Greetings,
>
> tormen.
>

> P.S.:
>
> I compiled the mysql database with "-latin1".
> Afterwards I installed mythtv in the above mentioned version and began to
> use
> it for the first time.
>
> The my.cnf is the original one from the gentoo package, except the
> changed
> default-char-set as described before.
>
> phpmyadmin/ shows me that the collation for the mythconverg database is
> latin1_swedish_ci (the default collation for latin1 charset as mysql.com
> told
> me).

New description:

 Hi... I am not sure if this might be a bug inside mythtv:

 I have a gentoo installation:
 * dev-db/mysql
      Installed:           5.0.26-r1

 * media-tv/mythtv
      Installed:           0.20_p11626

 I tried to create a record rule today and there was a german umlaut in the
 record rule:
         program.title LIKE 'Ein Fall für den Fuchs: %'

 After pressing test, I received the error message: "illegal mix of
 collations
 (latin1_swedish_ci,IMPLICIT) and (utf8_general_ci,COERCIBLE) for operation
 'like'".

 I tried the sql command which mythfrontend supplied together with this
 error
 message inside "mysql" on the console:

 mysql> SELECT NULL FROM (program,channel) WHERE  program.title LIKE 'Ein
 Fall
 für den Fuchs: %';
 ERROR 1267 (HY000): Illegal mix of collations (latin1_swedish_ci,IMPLICIT)
 and
 (utf8_general_ci,COERCIBLE) for operation 'like'

 But then I changed the setting inside /etc/my.cnf:
 I changed the default-character-set from utf8 to latin1 within the [mysql]
 section.

 Then mysql did NOT complain anymore!

 But mythfrontend still does?!

 Is this a bug inside mythfrontend in the way it contacts the database or
 is it
 another setting inside my.cnf that is misssing?!
 It must be possible for mythfrontend to also send this query successfully
 like it is now possible with the mysql commandline client, or?

 I also tried to set the default-char-set for all sections to latin1 inside
 the my.cnf, but the error message inside mythfrontend stayed.


 Greetings,

 tormen.


 P.S.:

 I compiled the mysql database with "-latin1".
 Afterwards I installed mythtv in the above mentioned version and began to
 use
 it for the first time.

 The my.cnf is the original one from the gentoo package, except the changed
 default-char-set as described before.

 phpmyadmin/ shows me that the collation for the mythconverg database is
 latin1_swedish_ci (the default collation for latin1 charset as mysql.com
 told
 me).

--

Comment:

 Meant to close [2755]

-- 
Ticket URL: <http://svn.mythtv.org/trac/ticket/2775#comment:4>
MythTV <http://svn.mythtv.org/trac>
MythTV


More information about the mythtv-commits mailing list