View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0003568 | mantisbt | bugtracker | public | 2004-02-16 08:41 | 2004-08-29 01:29 |
| Reporter | evelk | Assigned To | vboctor | ||
| Priority | normal | Severity | minor | Reproducibility | always |
| Status | closed | Resolution | fixed | ||
| Product Version | 0.18.1 | ||||
| Summary | 0003568: Monitor deleted bugs? | ||||
| Description | When I add a new bug (#123), monitor it for a user (Jim), delete the bug (#123) and create a new bug (again #123) then user Jim is still monitoring this (completely different!) bug! | ||||
| Steps To Reproduce | create bug | ||||
| Additional Information | The monitoring records should be deleted when a bug is deleted! | ||||
| Tags | No tags attached. | ||||
|
Fixed in CVS. Will be available in the next release. The only thing I am not sure about, is how do you re-add the bug with the same id!!! |
|
|
If you create a new bug, delete it and then create a new one, the same id will be used! |
|
|
That must be a strange MySQL setting G but as far as i know its possible to make the autoinc in a way it use the next free number maybe you index the tables daily or something like that ? |
|
|
bug_id is set to autonumber in schema so that shouldn't be possible unless you've accidently turned off the auto-numbering. Other issue is fixed in previous cvs, so resolving this. |
|
|
Table type was ISAM instead of MyISAM. In that case the highest value (+1) will be reused in auto-increment fields! |
|
|
hmm, interesting mysql behaviour then :) anyway, as victor patched in cvs to handle this (persumably, deleting a bug now deletes monitoring links, this issue can be resolved still. If this isn't the case, let us know. |
|