#420: Status -> Statuses table renaming migration (#73) breaks earlier migrations (#63) (Fixed)

Back to ticket list | See last change | Previous ticket | Next ticket
Jul 14 2008 * 23:49
Reported by:   Assigned to:  
Priority: Normal  Milestone:  
Release:    Component:   

In upgrading to trunk from 1.0.3, the migrate fails on migration 63, which calls some code that is looking for the Statuses table, which won’t exist until migration #73 runs to rename status->statuses.

Changelog:

Modified by – Jul 14 2008 * 23:52

As a workaround, I was able to make this work by migrating up to version=62, then running migrate #73, then running 63-72 and then 74+.

Modified by – Aug 04 2008 * 20:41

  • Status changed from Open to Fixed

[r511] – Fixed migration 63

Add comment and/or change ticket properties



Markup reference | Preview comment

Status: Assigned to:
Priority: Milestone:
Release:    Component: