Due to recent database issues and also being good practice to have a primary key on tables due to replication, I will be attaching a patch to add a primary key to the profiles_activity table. dkl
Severity: normal → enhancement
OS: Linux → All
Hardware: x86_64 → All
Summary: Add a new autoinc primary key for the profiles_activity table → Add a primary key to the profiles_activity table
Created attachment 632760 [details] [diff] [review] Patch to add incrementing primary key to profiles_activity table (v1)
Attachment #632760 - Flags: review?(glob)
Comment on attachment 632760 [details] [diff] [review] Patch to add incrementing primary key to profiles_activity table (v1) r=glob
Attachment #632760 - Flags: review?(glob) → review+
I found a place where this new primary key will be useful: in contrib/recode.pl. On checkin, add a comment in SPECIAL_KEYS right above profiles_activity => 'userid,profiles_when,fieldid' that the PK only exists since 4.4 (else someone is going to accidentally remove this entry).
Flags: approval? → approval+
Target Milestone: --- → Bugzilla 4.4
Committing to: bzr+ssh://firstname.lastname@example.org/bugzilla/trunk modified contrib/recode.pl modified Bugzilla/Install/DB.pm modified Bugzilla/DB/Schema.pm Committed revision 8291.
Status: ASSIGNED → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.