openlp-core team mailing list archive

[Raoul Snyman <raoul@xxxxxxxxxxx>]

Ah, right, now I remember. We discussed this a while back and said that
we would only support migrating 2.0.5 -> 2.1.1, so users of a previous
version of OpenLP need to upgrade to 2.0.5 before upgrading further.

** Changed in: openlp
       Status: New => Won't Fix

-- 
You received this bug notification because you are a member of OpenLP
Core, which is subscribed to OpenLP.
https://bugs.launchpad.net/bugs/1388227

Title:
  Crash upgrading from 2.0.3 to 2.1.0.2435

Status in OpenLP - Worship Presentation Software:
  Won't Fix

Bug description:
  Windows 7
  In my case the Portable package, but has occurred for normal package too.

  I installed OpenLPPortable_2.0.3.paf.exe into a new location, and ran OpenLP.
  I then installed OpenLPPortable_2.1.0.2435.paf into the same location.

  Installation went fine. During first run it asked if I wanted to backup the database. I clicked OK.
  Following this, a crash occurred with this error.

   Traceback (most recent call last):
    File "c:\Python33\lib\site-packages\sqlalchemy\engine\base.py", line 940, in _execute_context
      statement,
    File "c:\Python33\lib\site-packages\sqlalchemy\engine\default.py", line 435, in do_execute
      if not parameters:
  sqlite3.OperationalError: no such column: authors_songs_1.author_type

  (See attached for full log)

  OpenLP then started, however exiting later the same error occurred.

To manage notifications about this bug go to:
https://bugs.launchpad.net/openlp/+bug/1388227/+subscriptions