← Back to team overview

launchpad-dev team mailing list archive

Re: DB constraints to ensure consistency of LFA.restricted and Bug.private?

 

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 07/29/2010 07:52 AM, Abel Deuring wrote:
> Hi Stuart,
> 
> I am currently working on
> https://bugs.edge.launchpad.net/malone/+bug/39674 (Attachments of
> private bugreports are public). This involves of course to set the
> attribute LFA.restricted to True for private bugs.
> 
> My first idea was to simply set the restricted flag of all LFAs of
> BugAttachments of a bug in the method Bug.setPrivate().
> 
> But a comment from Robert in
> https://code.edge.launchpad.net/~adeuring/launchpad/bug-39674-lfa-editable/+merge/29314
> let me think again if we should enforce the consistency of
> LFA.restricted and Bug.private on the database level.

Another option is to just make all bug attachments restricted, and let
the bug provide access to the attachments as appropriate.  This is the
approach we used with merge proposal diffs.

Aaron
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkxRgVUACgkQ0F+nu1YWqI20MQCeOuxz7VvbO5EipgLRkpPpPX7g
rPYAoIgnF4fGxA8WI680MbJH1axpY3WG
=fkoN
-----END PGP SIGNATURE-----



Follow ups

References