[Tickets #9617] Re: db_migrate and incorrect charset handling

[bugs at horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/9617
------------------------------------------------------------------------------
  Ticket             | 9617
  Updated By         | Michael Rubinsky <mrubinsk at horde.org>
-Summary            | db_migrate and duplicate tags in rampage
+Summary            | db_migrate and incorrect charset handling
  Queue              | Horde Framework Packages
  Version            | Git master
  Type               | Bug
  State              | Feedback
  Priority           | 1. Low
  Milestone          |
  Patch              |
  Owners             | Michael Rubinsky
------------------------------------------------------------------------------


Michael Rubinsky <mrubinsk at horde.org> (2011-03-04 21:52) wrote:


> Attached patch seemed to fix it for me.

It should be sufficient to convert from the db charset to utf-8 here.  
However, there was the missing conversion from the database to utf-8  
in the migration script that probably made the extra conversion in  
your patch necessary. This has been fixed.

> Another bug has appeared. Output from debug log:
> DEBUG: SQL SELECT user_id, user_name FROM `rampage_users` WHERE  
> user_name IN ('ntllt')
> DEBUG: SQL QUERY FAILED: Duplicate entry 'ntllt' for key  
> rampage_users_user_name' INSERT INTO `rampage_users` (user_name)  
> VALUES ('ntllt')


Yeah, looks like there is a bunch of charset conversions missing in  
content. Working on it, and updated the title of the ticket to reflect  
the actual problem.