how best to clean up data mining files after an updated custom workflow

Albert Ting altlist at
Wed May 30 01:22:52 UTC 2007

On 5/29/07, Max Kanat-Alexander <mkanat at> wrote:
> On Tue, 29 May 2007 14:03:57 -0700 "Albert Ting" <altlist at>
> wrote:
> > While the new flow works, I'd like to clean up the data mining files
> > (and perhaps the bugs_activity table) to reflect the new workflow.
>         ./ --regenerate

Yes, but collectstats includes both the old and new status/resolution values.

> > It sounds like I'll need to run a bunch of mysql commands to clean up
> > the database and then regenerate the data mining files.  But was
> > wondering if there was a better solution?
>         Custom workflow isn't really "done" yet, upstream. So I'd wait
> until we're done with it. You could file a bug about this particular
> fact, if you want.
>         However, I personally think that bugs_activity shouldn't be
> modified, as it's a historical record.

I agree, I may just keep things as is for now.  If the powers-to-be
don't like it, I'll
look into hacking up the database.

More information about the developers mailing list