Hit send too early. Take a look at _update_author and everywhere it's called in this file to see what I originally did. We didn't migrate sessions, which made it easier. http://trac-hacks.org/browser/tracmergescript/tracmerge.py#L50
On Mon, Mar 16, 2009 at 2:33 PM, Chris Mulligan <chris.mulli...@gmail.com>wrote: > Off the top of my head, it looks like you're missing Ticket CC & Component > owner. > > I updated login names a while back when we were consolidating Tracs. We had > switched to using Kerberos and all users went from "username" to " > usern...@domain.com" so I added the @DOMAIN.COM to everything. It didn't > really have many complications. > > > On Sat, Mar 14, 2009 at 6:19 PM, Doruk Fisek <dfi...@fisek.com.tr> wrote: > >> >> Hi, >> >> I'm trying to integrate Trac 0.11 into a system where people can change >> their login name. >> >> I've a setup where Trac uses MySQL. As I've examined the MySQL tables, >> when a user changes its login, updating these fields accordingly seems >> suffice : >> >> attachment.author >> component.owner >> permission.username >> revision.author >> session.sid >> session_attribute.sid >> ticket.owner >> ticket.reporter >> ticket_change.author >> ticket_change.oldvalue if ticket_change.field = owner >> ticket_change.newvalue if ticket_change.field = owner >> wiki table.author column >> >> Am I missing anything? Is login name stored anywhere else? >> >> Are there any complications of changing login name that I'm not seeing? >> >> Doruk >> >> -- >> FISEK INSTITUTE - http://www.fisek.org.tr >> >> >> >> > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Users" group. To post to this group, send email to trac-users@googlegroups.com To unsubscribe from this group, send email to trac-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~----------~----~----~----~------~----~------~--~---
