If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

Don't delete old chart data; document problems instead

RESOLVED FIXED in Bugzilla 2.18

Status

()

Bugzilla
Reporting/Charting
--
blocker
RESOLVED FIXED
13 years ago
5 years ago

People

(Reporter: gerv, Assigned: gerv)

Tracking

2.18
Bugzilla 2.18
Bug Flags:
approval +
approval2.18 +

Details

Attachments

(1 attachment)

(Assignee)

Description

13 years ago
Currently, the migration code I checked in with a recent chart update deletes
and remigrates all the chart data. This isn't good, really - it's been too long,
and the corruption window was quite small anyway. Myk and I have decided it's
best to document the issue and let people nuke their own data if they want :-)

This bug covers backing out the auto-nuking and updating the docs.
(Assignee)

Comment 1

13 years ago
Created attachment 163969 [details] [diff] [review]
Patch v.1

This patch should hopefully do the trick. As for "updating the docs", I think
this is an appropriate subject for a section in the release notes. 

"If you updated to a development release (2.17.5 or 2.17.6) or CVS snapshot
between 2003-06-25 and 2004-02-12, and then edited some charts (either your own
or auto-created) before updating to a release post-2004-02-12 (e.g. 2.17.7 or
later) then the charts you edited may be corrupted, and be getting invalid
data. It is suggested that you create new charts for those queries and move the
old ones somewhere out of the way (currently there's no deletion mechanism)."

I'm sure that can be phrased better.

Gerv
Blocks: 244831
Comment on attachment 163969 [details] [diff] [review]
Patch v.1

>-    print "Deleting possibly-corrupt new-chart data " . 
>-           "(it will be re-migrated) ...\n" unless $silent;

Geez, how did this ever pass review?  ;)  That should have never been masked
when in silent mode, that's one of those things that the sysadmin really
*would* have wanted to see in his cron mail :)

Otherwise, this looks good to me, let's get it in before the upgrade this
weekend :)
Attachment #163969 - Flags: review+
Flags: approval2.18+
Flags: approval+
Target Milestone: --- → Bugzilla 2.18
(Assignee)

Comment 3

13 years ago
Fixed on trunk:

Checking in checksetup.pl;
/cvsroot/mozilla/webtools/bugzilla/checksetup.pl,v  <--  checksetup.pl
new revision: 1.315; previous revision: 1.314
done

Fixed on branch:

Checking in checksetup.pl;
/cvsroot/mozilla/webtools/bugzilla/checksetup.pl,v  <--  checksetup.pl
new revision: 1.289.2.13; previous revision: 1.289.2.12
done

Gerv
Status: NEW → RESOLVED
Last Resolved: 13 years ago
Resolution: --- → FIXED
QA Contact: matty_is_a_geek → default-qa
You need to log in before you can comment on or make changes to this bug.