Merge lp:~lifeless/launchpad/bugmessage into lp:launchpad/db-devel
Proposed by
Robert Collins
on 2010-09-16
| Status: | Merged |
|---|---|
| Approved by: | Stuart Bishop on 2010-09-16 |
| Approved revision: | no longer in the source branch. |
| Merged at revision: | 9790 |
| Proposed branch: | lp:~lifeless/launchpad/bugmessage |
| Merge into: | lp:launchpad/db-devel |
| Diff against target: |
46 lines (+15/-1) 3 files modified
database/schema/comments.sql (+4/-1) database/schema/patch-2208-14-0.sql (+9/-0) lib/lp/bugs/model/bugmessage.py (+2/-0) |
| To merge this branch: | bzr merge lp:~lifeless/launchpad/bugmessage |
| Related bugs: |
| Reviewer | Review Type | Date Requested | Status |
|---|---|---|---|
| Stuart Bishop | db | 2010-09-16 | Approve on 2010-09-16 |
| Launchpad code reviewers | 2010-09-16 | Pending | |
|
Review via email:
|
|||
Commit Message
Permit getting bug message indices from the DB in the future.
Description of the Change
Permit future improvements to all bug pages that show messages or attachments by removing a current rather crazy runtime analysis for message sequence.
To post a comment you must log in.

This version adds a unique constraint rather than a unique index, which I prefer as it puts a little more metadata into PG.
SET client_ min_messages= ERROR; _bug__index_ _key UNIQUE (bug, index); seRevision VALUES (2208, 14, 0);
ALTER TABLE BugMessage ADD COLUMN index integer;
ALTER TABLE BugMessage ADD CONSTRAINT bugmessage_
INSERT INSERT INTO LaunchpadDataba
As discussed, we need to populate this after the rollout and then land a followup patch setting the column NOT NULL.