Merge lp:~stevenk/launchpad/db-specification-new-access-policy into lp:launchpad/db-devel
Proposed by
Steve Kowalik
Status: | Merged |
---|---|
Approved by: | Steve Kowalik |
Approved revision: | no longer in the source branch. |
Merged at revision: | 12272 |
Proposed branch: | lp:~stevenk/launchpad/db-specification-new-access-policy |
Merge into: | lp:launchpad/db-devel |
Diff against target: |
158 lines (+126/-1) 4 files modified
database/schema/patch-2209-28-6.sql (+78/-0) database/schema/security.cfg (+1/-0) lib/lp/blueprints/tests/test_specification_access_policy_triggers.py (+46/-0) lib/lp/testing/factory.py (+1/-1) |
To merge this branch: | bzr merge lp:~stevenk/launchpad/db-specification-new-access-policy |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Stuart Bishop (community) | db | Approve | |
Review via email: mp+143230@code.launchpad.net |
Commit message
Add new columns Specification.
Description of the change
Add new columns on Specification, access_
To post a comment you must log in.
Looks good.
70 +CREATE OR REPLACE FUNCTION specification_ maintain_ access_ cache_trig( ) RETURNS trigger denorm_ access( NEW.id) ;
71 + LANGUAGE plpgsql AS $$
72 +BEGIN
73 + PERFORM specification_
74 + RETURN NULL;
75 +END;
76 +$$;
If you want you can add an 'if NEW.id <> OLD.id then specification_ denorm_ access( OLD.id) ' here to cope with someone updating the id column, not that we ever actually do that.