Hi guys, this looks like a great product. I've MySQL5 and have no desire to install another DB so I've been reading with interest the comments and tickets around issues with MySQL5 and I just wanted to see if I could get a status update from someone on the inside trac, together with your recommendation on whether it is worth me waiting for a future trac release (and if so, which one, and when).
One major problem was a MySQL limitation on primary key length and trac's use of 'path' as a part of that primary key, with the result that paths can't be longer than 111-characters. Is this still the situation if in the latest trac distribution? 1. My path lengths I think will be longer than are currently allowed; so this looks like the biggest issue. Is ALTER TABLE `node_change` DROP PRIMARY KEY , ADD PRIMARY KEY ( `rev` ( 39 ) , `path` ( 255 ) , `change_type` ( 39 ) ) ; still considered the best manual fix for this? Has anyone tried it with success? 2. MySQL 5 doesn't support MyISAM anyway, so use of an InnoDB to get over the utf issue isn't such a big deal for me, I think. 3. #5120 - mysql_backend.py only passes db, user, passwd, host, and port to MySQLdb. I think I can live with that. That's all I could see on still opened MySQL issues. Did I miss anything? If not, the only thing stopping me is path length restrictions. thanks in advance, John McMahon --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~----------~----~----~----~------~----~------~--~---
