Imported From: http://groups.google.com/group/in-portal-bugs/browse_thread/thread/e2637a0da4f53bdb#
I have all modules (even paid) installed and I was trying to upgrade from
4.3.9 to 5.1.0-RC1. This all failed with large SQL error, that LanguageId
column was missing in Phrase table, when upgrade script was trying to set
index on it.
That's how we are performing upgrade through 2 or more versions now (e.g.
from 5.0.0 to 5.0.2): 1.
- run "before" php upgrade script for 5.0.1 version
...
- run "before" php upgrade script for 5.0.2 version
...
- run sqls from 5.0.1 to 5.0.2 version
...
- run "after" php upgrade script for 5.0.1 version
...
- run "after" php upgrade script for 5.0.2 version
This process is repeated for each upgradeable module.
I thought at first, that wrapping version upgrade scripts (php + sql)
together will solve the problem: 1.
- run "before" php upgrade script for 5.0.1 version
...
- run 5.0.1 version sqls
...
- run "after" php upgrade script for 5.0.1 version
...
- run "before" php upgrade script for 5.0.2 version
...
- run 5.0.2 version sqls
...
- run "after" php upgrade script for 5.0.2 version
But this wasn't helping. Because when 1st module upgrade scripts will delete
columndelete column, that is used by 2nd module upgrade script, then we also got sql
errorsql error.
And so another idea approached my mind: you all know, that don't have
problems, when we upgrade for 1 version only (e.g. from 5.0.0 to 5.0.1 or
from 5.0.1 to 5.0.2). I've created dependency list for each module, where
I've listed what "Core" module version is required to perform successful
upgrade to each of given module versions.
*Patch will be coming soon.*
--
Best Regards,
...
Related Tasks
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|