Closed (won't fix)
Project:
Version Control API
Version:
6.x-2.x-dev
Component:
API module
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
16 Nov 2010 at 21:11 UTC
Updated:
18 Nov 2010 at 22:25 UTC
Following the already committed logic of removing {versioncontrol_operation_items} table(almost completed at #972058: Complete removing of {versioncontrol_operation_items} table), doesn't it would be the same for {versioncontrol_operation_labels}?
Is there a reason why we are still keeping it there?
Sam told me on IRC that it stays because it would be a place to store tag timestamps(project* would need one), but also refer me the idea to deal with it in other way if possible, so I think this is really related to #879600: Meta: introduce an activity stream separate from commit logs, where that kind of info should be stored.
Comments
Comment #1
sdboyer commentedSo I just remembered the biggest reason for retaining this table - we need to store the mappings between commits and branches somewhere. That's a one-to-many relationship, so it definitely needs a separate table. This is the one that makes sense for that purpose. We might get rid of the action field, but we definitely need the mapping.