View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0004491 | mantisbt | relationships | public | 2004-09-06 09:02 | 2008-04-19 04:10 |
Reporter | pdugas | Assigned To | vboctor | ||
Priority | normal | Severity | minor | Reproducibility | have not tried |
Status | closed | Resolution | fixed | ||
Product Version | 0.19.0rc1 | ||||
Fixed in Version | 1.2.0a1 | ||||
Summary | 0004491: Deleting duplicate relationshilp left value in 'duplicate_id' field | ||||
Description | Had an issue that didn't show up in the ChangeLog page and figured out it had a non-zero value in the "duplicate_id" field. Perhaps the issue in question was marked a duplicate in an older version, not sure, but the "duplicate" relationship was deleted. Should the relationship_delete*() routines make sure the field is cleared when removing "duplicate" relathinships? | ||||
Tags | No tags attached. | ||||
In my opinion is the field 'duplicate_id' no longer necessary and should be removed to prevent inconsistency with the bug_relationship_table. |
|
The problem is due to the mixing of duplicate relationships and duplicate_id field in the same database. I guess we have to decide what to do. Do we have to maintain both the methods, or we can move to a unique solution based on just relationship (so removing every reference to the duplicate_id field)? |
|
I would like a unique solution based on relationship. |
|
I think we should do the following:
|
|
In Mantis 1.3, we can remove the duplicate_id field from the schema, remove associated history entries and remove it from language files. I just want to make sure we don't delete data for users that they may depend on it from ways I haven't considered. Fixed by svn: Revision: 5110 |
|