Merge lp:~seif/zeitgeist/fix-665607-and-643303 into lp:zeitgeist/0.1
Proposed by
Seif Lotfy
Status: | Merged |
---|---|
Merged at revision: | 1624 |
Proposed branch: | lp:~seif/zeitgeist/fix-665607-and-643303 |
Merge into: | lp:zeitgeist/0.1 |
Diff against target: |
46 lines (+14/-14) 1 file modified
_zeitgeist/engine/sql.py (+14/-14) |
To merge this branch: | bzr merge lp:~seif/zeitgeist/fix-665607-and-643303 |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Siegfried Gevatter | Approve | ||
Review via email: mp+39307@code.launchpad.net |
Description of the change
I tried to fix the bug by simple detecting the current core schema and "i" and then iterating through all update scripts in form of 'core_"i"_"i+1"' its simple and straight forward. No looking for paths and leaving us to actually only worry about upgrade +1 increasing upgrade scripts. If the basic idea is OK I can propose for merging.
Bugs fixed: #665607 and #643303
To post a comment you must log in.
From the previous merge proposal:
My comment:
> Looks good to me. Mikkel, Markus, do you agree this is the
> approach with which we want to handle database upgrades?
Markus' comment:
> okidoki, my take on this: I would like to have some kind of tests
> for the upgrade pathes, but please let's not do it like Seif tried
> in rev 1625.
> Therefor I suggest the following, let's merge this branch without
> rev 1625 into lp:zeitgeist, and then put some work into writing a
> testing framework for db schemes and upgrades.