Closed Bug 462836 Opened 16 years ago Closed 16 years ago

Unable to recode the databases to utf8.

Categories

(Bugzilla :: Installation & Upgrading, defect)

x86
Linux
defect
Not set
major

Tracking

()

RESOLVED DUPLICATE of bug 431201

People

(Reporter: d.sawicki, Unassigned)

References

()

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.3) Gecko/2008092417 Firefox/3.0.3
Build Identifier: 3.0.5 and/or 3.2rc1

Attempting to recode a database which is in the 2.20.1 standard.  I have attempted to use the recode.pl in 3.0.5 and 3.2rc1.

The failure is exactly like reported in the URL above.  The steps to reproduce are exactly the same.

Reproducible: Always

Steps to Reproduce:
1. Get a dump from an old 2.20.1 database with some german characters (é è ê, ç,
etc.)
2. Install a fresh 3.0.5 or 3.2rc1 bugzilla on a Fedora 9 linux server and get it running.
3. Drop existing databse bugs, recreate one with your dump in step one.
4. Run checksetup.pl so it can modify and update the schema.
5. When ask, run recode.pl with the option --charset=latin1

Actual Results:  
Wide character in subroutine entry at C:\Bugzilla\contrib\recode.pl 
line 251.

Expected Results:  
A converted database from latin1 to utf8 format with no warnings or errors.
Status: UNCONFIRMED → RESOLVED
Closed: 16 years ago
Resolution: --- → DUPLICATE
Please note that the size of the database is 1.6GB and also has one table that uses latin1_german2_ci COLLATE.  I'm new to this project and have limited knowledge of its history.  However, I'm not allowed to "lose" any data in the upgrade process.  Any suggestions on ways to resolve are of interest to me.

I have manually attempted to convert the data using the mysql command line, and have been able to get it working this way, but I get an error when doing a basic search after the manual upgrade.  If I attempt a advanced search... I run into no problems.  I can provide the search results that apache mentions, but again, this was a workaround because the recode.pl script did not work.  

***** Data Error Received with the Manual Change of the data in the DB *****

Please stand by ...
Software error:

DBD::mysql::st execute failed: Can't find FULLTEXT index matching the column list [for Statement "SELECT bugs.bug_id, bugs.bug_severity, bugs.priority, bugs.bug_status, bugs.resolution, bugs.bug_severity, bugs.priority, bugs.op_sys, map_assigned_to.login_name, bugs.bug_status, bugs.resolution, bugs.short_desc, (SUM(MATCH(longdescs_.thetext) AGAINST('test' )) + CASE WHEN bugs.short_desc LIKE '%test%' THEN 7 ELSE 0 END) AS relevance FROM bugs  INNER JOIN profiles AS map_assigned_to ON (bugs.assigned_to = map_assigned_to.userid) LEFT JOIN longdescs AS longdescs_ ON (bugs.bug_id = longdescs_.bug_id ) LEFT JOIN bug_group_map  ON bug_group_map.bug_id = bugs.bug_id  AND bug_group_map.group_id NOT IN (13,8,15,14,4,12,2,10,3,16,11,1,6,9,5,7)  LEFT JOIN cc ON cc.bug_id = bugs.bug_id AND cc.who = 600 WHERE ((bugs.bug_status IN ('UNCONFIRMED','NEW','ASSIGNED','REOPENED')) AND (MATCH(longdescs_.thetext) AGAINST('test' ) > 0 OR (bugs.short_desc LIKE '%test%'))) AND bugs.creation_ts IS NOT NULL AND ((bug_group_map.group_id IS NULL)    OR (bugs.reporter_accessible = 1 AND bugs.reporter = 600)     OR (bugs.cclist_accessible = 1 AND cc.who IS NOT NULL)     OR (bugs.assigned_to = 600) OR (bugs.qa_contact = 600) ) GROUP BY bugs.bug_id ORDER BY relevance desc LIMIT 200"] at /var/www/html/bugzilla/buglist.cgi line 1006

For help, please send mail to the webmaster (dsawicki@ds-linuxvm01.localdomain), giving this error message and the time and date of the error. 

****** End of Error  *******
Status: RESOLVED → UNCONFIRMED
Resolution: DUPLICATE → ---
This is a bug-tracker, not a support forum. Your bug is identical to another one, so it should be marked as a duplicate of that one. I do appreciate the data, thank you.
Status: UNCONFIRMED → RESOLVED
Closed: 16 years ago16 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.