ubuntu-accomplishments-contributors team mailing list archive

[cprofitt <cprofitt@xxxxxxxxxx>]

On Sun, 2012-03-11 at 15:16 -0700, Jono Bacon wrote:
> On 11 March 2012 14:54, Janos Gyerik <janos.gyerik@xxxxxxxxx> wrote:
> > Hi Jono,
> >
> >> In terms of uniqueness for Accomplishments, there should only ever be
> >> one application+descriptor combination
> >
> > Thanks, that's pretty clear like that!
> >
> >> In terms of the AccomplishmentProposal uniqueness question, I am not
> >> sure what you mean by it being unique?
> >
> > I meant it is NOT to be unique. And that's the dilemma: how to have
> > unique constraint on Accomplishment but NOT on AccomplishmentProposal,
> > when they both inherit from the same AccomplishmentBase model.
> 
> Oh I see, so if the Accomplishment is unique due to the app+descriptor
> combo, you mean that this would make AccomplishmentProposal unique and
> therefore not allow multiple contributions?
> 
>    Jono

I would agree that the proposals should be unique as well to make the
transition easier and avoid two non-unique proposals to be 'accepted'
since that would cause a conflict.