Re: [openlp-dev] MediaShout import bug

>First glance - looks like there might be a change in database schema >or a corrupted mediashout db. I'm not sure what version of MediaShout we initially developed against, but we should handle this case. There's nothing to indicate that the user did anything weird to their database. --

Re: [openlp-dev] MediaShout import bug

openlp/plugins/songs/lib/importer/mediashout.py line 69 cursor.execute('SELECT Name FROM Themes INNER JOIN SongThemes ON SongThemes.ThemeId = Themes.ThemeId ' 'WHERE SongThemes.Record = %s' % song.Record) And the list of tables in the songs5.mdb file: FireHistory

Re: [openlp-dev] MediaShout import bug

If you want a second pair of eyes, I can have a look tonight (friday night PST) On Thu, Jun 9, 2016 at 8:09 PM, Ian Knight wrote: > If you zap me the song DB, I'm happy to take a look (can't make any > guarantees until I get a better look though)On 10 Jun 2016 7:15 am,

Re: [openlp-dev] MediaShout import bug

If you zap me the song DB, I'm happy to take a look (can't make any guarantees until I get a better look though)On 10 Jun 2016 7:15 am, Raoul Snyman wrote: > > Hi guys, > > A user recently sent a MediaShout import bug through, and they are stuck > without songs until the bug is fixed. I don't