Closed
Bug 997468
Opened 11 years ago
Closed 11 years ago
Migration 759 can't be run
Categories
(addons.mozilla.org Graveyard :: Maintenance Scripts, defect, P1)
Tracking
(Not tracked)
RESOLVED
FIXED
2014-04
People
(Reporter: yboniface, Assigned: magopian)
References
Details
I got this pastebin from mat who got it from jason, but we have the idea: https://jason.pastebin.mozilla.org/4817671
@washort, as it seems you added this migration (https://github.com/mozilla/olympia/commit/ad7b8e4f84c787c20c0c34d874f8e3aa0d047963#diff-10), do you have any hint?
For the record:
Running SQL migration 759:
DROP TABLE prices;
DROP TABLE price_currency;
DROP TABLE addon_purchase;
DROP TABLE addons_premium;
DROP TABLE refunds;
DROP TABLE addon_payment_data;
DROP TABLE paypal_checkstatus;
ALTER TABLE stats_contributions
DROP COLUMN user,
DROP COLUMN type,
DROP COLUMN price_tier,
DROP COLUMN related;
Error: Had trouble running this: BEGIN;
DROP TABLE prices;
DROP TABLE price_currency;
DROP TABLE addon_purchase;
DROP TABLE addons_premium;
DROP TABLE refunds;
DROP TABLE addon_payment_data;
DROP TABLE paypal_checkstatus;
ALTER TABLE stats_contributions
DROP COLUMN user,
DROP COLUMN type,
DROP COLUMN price_tier,
DROP COLUMN related;
UPDATE schema_version SET version = 759;
COMMIT;
stdout:
stderr: ERROR 1217 (23000) at line 2: Cannot delete or update a parent row: a foreign key constraint fails
returncode: 1
Comment 1•11 years ago
|
||
This prevents olympia to be updated on dev.
Priority: -- → P1
Target Milestone: --- → 2014-04
Comment 2•11 years ago
|
||
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Comment 3•11 years ago
|
||
evidently doesn't work on -dev. deleting for now, will readd later.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Assignee | ||
Comment 4•11 years ago
|
||
Assignee: nobody → mathieu
Assignee | ||
Updated•11 years ago
|
Status: REOPENED → RESOLVED
Closed: 11 years ago → 11 years ago
Resolution: --- → FIXED
Updated•9 years ago
|
Product: addons.mozilla.org → addons.mozilla.org Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•