Hi, In the WorkLogPlugin, I have an ITicketChangeListener that watches to see if any tickets that someone is currently working on is closed.
Depending on the options and setup WorkLogPlugin can add a comment to the ticket to state how long the user has worked on that ticket. The problem comes if a comment is left when closing the ticket (either via the website or via the svn commit message integration hook). Under these circumstances a ticket_change is added with a timestamp +field parameter. My ITicketChangeListener will see this and then try to add it's own timestamp+field combo that is the same as the normal one and thus there is a unique key violation. To do this properly I think I would really need an ITicketManipulator to edit (e.g. append to) or add a comment to the existing change. AFAIK that's not implemented yet. Does anyone know of a strategy to avoid such clashes? I'm sure I tried to catch the exception thrown by the db and add 1 to the time but I'm sure that eneded my up in hot water when I tried before with some bizarre, always triggering issue. Has anyone got any insights into this? Col --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Development" 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-dev?hl=en -~----------~----~----~----~------~----~------~--~---
