Merge lp:~stevenk/launchpad/db-add-information_type into lp:launchpad/db-devel
| Status: | Merged |
|---|---|
| Approved by: | Steve Kowalik on 2012-03-08 |
| Approved revision: | no longer in the source branch. |
| Merged at revision: | 11433 |
| Proposed branch: | lp:~stevenk/launchpad/db-add-information_type |
| Merge into: | lp:launchpad/db-devel |
| Diff against target: |
33 lines (+11/-0) 2 files modified
database/schema/comments.sql (+2/-0) database/schema/patch-2209-12-0.sql (+9/-0) |
| To merge this branch: | bzr merge lp:~stevenk/launchpad/db-add-information_type |
| Related bugs: |
| Reviewer | Review Type | Date Requested | Status |
|---|---|---|---|
| Stuart Bishop | db | 2012-03-07 | Approve on 2012-03-08 |
| Robert Collins (community) | 2012-03-07 | Needs Fixing on 2012-03-07 | |
|
Review via email:
|
|||
Commit Message
[r=stub][bug=933759][no-qa] Add an information_type column to Bug and Branch.
Description of the Change
Add an information_type column to Bug and Branch.
This is preliminary work to replace both Bug.security_
A new DB patch to add a NOT NULL constraint will be added after we have completely migrated to it.
| Stuart Bishop (stub) wrote : | # |
The comment is not very useful at the moment. Try something like 'Enum describing what type of information is stored, such as type of private or security related data, and used to determine how to apply an access policy.'
Otherwise the patch is fine.

Don't use default, it will take hours to apply. See the HotPatching wiki page/schemachan geprocess wiki page for docs.