Error when trying to create milestone with existing name

[finn@…]

If you try to create a new milestone with the same name as an existing one, you get a python error message and traceback. This should be handled gracefully with an instruction to the user about choosing another name.

Traceback (most recent call last):
  File "/usr/lib/python2.3/site-packages/trac/web/modpython_frontend.py", line 206, in handler
    dispatch_request(mpr.path_info, mpr, env)
  File "/usr/lib/python2.3/site-packages/trac/web/main.py", line 139, in dispatch_request
    dispatcher.dispatch(req)
  File "/usr/lib/python2.3/site-packages/trac/web/main.py", line 107, in dispatch
    resp = chosen_handler.process_request(req)
  File "/usr/lib/python2.3/site-packages/trac/ticket/roadmap.py", line 355, in process_request
    self._do_save(req, db, milestone)
  File "/usr/lib/python2.3/site-packages/trac/ticket/roadmap.py", line 413, in _do_save
    milestone.insert()
  File "/usr/lib/python2.3/site-packages/trac/ticket/model.py", line 576, in insert
    (self.name, self.due, self.completed, self.description))
  File "/usr/lib/python2.3/site-packages/trac/db.py", line 219, in execute
    args or [])
  File "/usr/lib/python2.3/site-packages/trac/db.py", line 211, in _rollback_on_error
    return function(self, *args, **kwargs)
IntegrityError: column name is not unique

[Christian Boos]

Right, the problem is still there.

[Christian Boos]

(Sorry)

[anonymous]

Somehow related to the problematic discussed in #4130.

[Christian Boos]

Duplicate report: #4849.

[Emmanuel Blot]

#5217 marked as a duplicate.

[Christian Boos]

Yep, this one is pretty annoying and got reported often… moving up on the prio list.

[Christian Boos]

Fixed in r5276.

[Christian Boos]

Hm, not really, renaming a milestone to an existing one still crashes.

[Christian Boos]

Corrected in r7790 (0.11-stable) and r7793 (trunk).