Merge lp:~gary/launchpad/bug548-db-2 into lp:launchpad/db-devel
Status: | Merged |
---|---|
Approved by: | Gary Poster |
Approved revision: | no longer in the source branch. |
Merged at revision: | 10177 |
Proposed branch: | lp:~gary/launchpad/bug548-db-2 |
Merge into: | lp:launchpad/db-devel |
Diff against target: |
454 lines (+313/-1) 8 files modified
database/sampledata/current-dev.sql (+106/-0) database/sampledata/current.sql (+106/-0) database/schema/comments.sql (+3/-0) database/schema/patch-2208-38-0.sql (+7/-0) database/schema/security.cfg (+2/-0) lib/lp/bugs/doc/bugnotification-sending.txt (+19/-0) lib/lp/registry/interfaces/person.py (+22/-1) lib/lp/registry/model/person.py (+48/-0) |
To merge this branch: | bzr merge lp:~gary/launchpad/bug548-db-2 |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Gavin Panella (community) | Approve | ||
Stuart Bishop (community) | db | Approve | |
Robert Collins | db | Pending | |
Review via email: mp+48318@code.launchpad.net |
Description of the change
I made https:/
Beyond some relatively superficial problems, Stuart and Robert expressed fundamental concern about adding more columns to the Person table. Stuart suggested an alternate approach, and implemented the SQL for me. Thank you!
His SQL had two aspects I had to remove. The first, which I did with his blessing, is that I switched from using a trigger to create PersonSettings to using __init__. This fixed some access problems I found in tests, in which a newly-created Person object would not yet have a PersonSettings object around.
The other aspect is that he had moved verbose_
On the downside, in his original change, the Person table actually shrank a very small bit, while in the current version, it merely stays as it was. Making another table for shared Person-Team settings is unnecessary and out of scope for this branch.
I threw in a quick test to show that the new attribute was available. I was reading doctests to figure out what was going on and found them helpful, so I just threw the smoketest in there for now. When we actually have this feature implemented, I will advocate maintaining the doctests for new readers like me, while moving exceptional cases to unit tests.
Gary
Fine.
I suspect PersonSettings will end up with team settings too, but for now this is fine.