"bug in database"
Jeff Mitchell
kde-dev at emailgoeshere.com
Wed Jul 26 09:43:51 UTC 2006
I apparently had updated on this computer after your commit but before
Bart's...I had Podcast Tables v3 and Persistent v15. Didn't have anything
terribly important so I just wiped the database and started over.
--Jeff
On Tuesday 25 July 2006 23:18, Seb Ruiz wrote:
> If it was us, then you would have noticed this problem about a week
> ago. In case you hadn't updated, you need to ensure that Persistent
> Tables Version = 14 and Podcast Tables Version = 2.
>
> Editing these tables should fix your problem.
>
> Seb
>
> Quoting Martin Aumueller <aumueller at uni-koeln.de>:
> > I got this because of a podcast code update by Seb - this included a db
> > version update, but this change was reverted by Bart a short time later
> > without providing an upgrade path.
> >
> > On Wed July 26 2006 02:03, Jeff Mitchell wrote:
> >> Guys--
> >>
> >> Did anyone commit a database update recently? Suddenly I'm getting
> >> this:
> >>
> >> amarok: BEGIN: void CollectionDB::checkDatabase()
> >> amarok: [CollectionDB] Beginning database update
> >> amarok: [CollectionDB] [ERROR!] There is a bug in Amarok: instead of
> >> destroying your valuable database tables, I'm quitting
> >>
> >> Is this a known issue, or did my database just get messed up somehow?
> >>
> >> --Jeff
> >> _______________________________________________
> >> Amarok mailing list
> >> Amarok at kde.org
> >> https://mail.kde.org/mailman/listinfo/amarok
> >
> > _______________________________________________
> > Amarok mailing list
> > Amarok at kde.org
> > https://mail.kde.org/mailman/listinfo/amarok
More information about the Amarok
mailing list