launchpad-dev team mailing list archive

[Robert Collins <robertc@xxxxxxxxxxxxxxxxx>]

On Mon, May 2, 2011 at 12:55 PM, Gary Poster <gary.poster@xxxxxxxxxxxxx> wrote:
>> We need to decide what to do with these rows. Should they be removed?
>> Should we set BugSubscriptionFilter.structuralsubscription to NULL?
>> Are we removing the wrong StructuralSubscription rows?
>>
>> If they should be removed, it might be sane (and the simplest fix) to
>> make the BugSubscriptionFilter.structuralsubscription foreign key ON
>> DELETE CASCADE
>
> I believe that would be appropriate.  If someone (Stuart? Yellow squad?) could make this change, I would appreciate it.  We had our baby Saturday, so I will be out this week.

I'm assuming you mean 'on delete cascade is appropriate'.

Given that we need to merge to devel *today* be confident that we'll
hit the deploy window, I'm asking losa to merge only the qa-ok stuff
as normal. This happens to be immediately before the failing db patch;
the only thing behind it is the contents-generate-pocket patch from
jtv. If we can get this sorted and everything qa-ok in db-stable with
24 hours leeway before the downtime we can do another merge to bring
it across.

I've marked the patch qa-bad per our regular process, so the db-stable
deployment report will make it clear whats up.

-Rob