Merge lp:~j-corwin/openlp/migration into lp:openlp
Proposed by
Jonathan Corwin
Status: | Merged |
---|---|
Merged at revision: | not available |
Proposed branch: | lp:~j-corwin/openlp/migration |
Merge into: | lp:openlp |
Diff against target: |
270 lines (+217/-11) 2 files modified
openlp/migration/migratebibles.py (+196/-2) openlpcnv.pyw (+21/-9) |
To merge this branch: | bzr merge lp:~j-corwin/openlp/migration |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Tim Bentley | Approve | ||
Raoul Snyman | Approve | ||
Review via email:
|
This proposal supersedes a proposal from 2010-03-22.
Description of the change
Attempt to get Bible migration working for Windows. Done it via openlpcnv, rather than bible-1to2-
Not entirely sure what I was doing in migratebibles, just copying from migratesongs and hoping for the best, so criticism expected, hopefully constructive!
Used an insert statement for the verses, since doing it the same as everything else was far too slow to be practical and I don't know sqlalchemy so didn't know what alternatives I had.
To post a comment you must log in.
The openlpcnv.pyw is a hack at best, and the code from bible-1to2- converter. py is used in an online migration tool I am writing.
The reason the bible-1to2- converter. py script borks on Windows is because that module does not exist, and it requires a full edition of Visual C++ in order to compile (I tried it with the express edition, but it doesn't have one particular tool required in the linking process). I mostly created those two 1to2 scripts for our use as developers to easily convert 1.x stuff to 2.
Personally, I think that the online conversion tool should be the official upgrade tool, it would allow folks to upgrade without needing to install anything else on their computers. Of course folks are welcome to bring their own ideas to the table, but to me an online converter makes the most sense.