Closed (fixed)
Project:
Version Control API
Version:
5.x-1.0-rc4
Component:
API module
Priority:
Normal
Category:
Bug report
Assigned:
Reporter:
Created:
31 Jan 2008 at 17:18 UTC
Updated:
15 Apr 2014 at 22:25 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
ezyang commentedAttached is a patch that adds a regular KEY to the column. However, I think a UNIQUE KEY on repo_id and revision would be more useful (after all, commits are unique to a repository). This means putting repo_id in the commits table, though.
Comment #2
jpetso commentedI want to get the 5.x-1.0 out of the door, so for that one we'll have the simple solution with just an added key. For the upcoming database changes, {versioncontrol_commits} will be merged into {versioncontrol_operations}, so we can get our unique key back (this time also including the 'type' column in it, of course).
The change to add the key is trivial (for Postgres as well, which is not taken into account in the above patch), the real work (but not all too much either) is in the upgrade function. Let me come up with that after the pizza baguette which should be ready by now.
Comment #3
jpetso commentedFixed in commit 100219, to be released with versioncontrol 5.x-1.0.
Comment #4
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.