Bug #4218
Switch migration task to direct db updates intead of YAML upgrades
Status: | Verified | Start date: | ||
---|---|---|---|---|
Priority: | Critical | Due date: | ||
Assignee: | Jesús García Crespo | % Done: | 0% | |
Category: | - | |||
Target version: | Release 1.3 | |||
Google Code Legacy ID: | atom-2270 | Tested version: | ||
Sponsored: | Requires documentation: |
Description
See Doctrine migration system:
http://www.slideshare.net/weaverryan/the-art-of-doctrine-migrations
[g] Legacy categories: Migration task
Related issues
History
#2 Updated by Anonymous about 10 years ago
- Priority changed from Critical to High
- Target version changed from Release 1.2.1 to Release 1.3
[g] Labels added: Milestone-Release-1.3, Priority-High
[g] Labels removed: Milestone-Release-1.2.1, Priority-Critical
#4 Updated by David Juhasz about 10 years ago
- Status changed from New to QA/Review
Finished in r11643.
[g] Labels added: Component-Migrations
[g] New owner: jessica%...@gtempaccount.com
#5 Updated by Jessica Bushey almost 10 years ago
[g] New owner: Jessica Bushey
#6 Updated by David Juhasz almost 10 years ago
- Priority changed from High to Critical
We need to address how to handle taxonomy and term "constant ids" with the new migration scheme. The old YAML way would transparently map the old primary key to the new primary keys, but this will be difficult to emulate in the db only migration script.
[g] Labels added: Priority-Critical
[g] Labels removed: Priority-High
[g] New owner: David Juhasz
#7 Updated by David Juhasz almost 10 years ago
- Status changed from QA/Review to In progress
#8 Updated by Jesús García Crespo almost 10 years ago
[g] New owner: Jesús García Crespo
#9 Updated by Jesús García Crespo almost 10 years ago
- Status changed from In progress to Verified
#10 Updated by Jesús García Crespo almost 10 years ago
- Status changed from Verified to In progress
#11 Updated by Jesús García Crespo almost 10 years ago
- Status changed from In progress to Verified
Fixed! :-)