Hi all, David García Granda schrieb am 29.10.2011 19:29:
>> If you get this error, then >> pytrainer/upgrade/versions/010_default_upgrade.sql has not been >> successfully executed. Can you please check ~/.pytrainer/log.out log >> file to see if any related error has been reported there? > > Any news from your side, Arnd? Sorry David, my fault, I actually overread your reply (was hidden behind my longer traceback ;). Anyway: I repeated the whole procedure (my 1.8.0 productive data are well backuped), but don't see anything interesting: 2011-10-30 08:59:10,937|DEBUG|base|__init__|Loading script /home/arnd/bin/pytrainer/lib/python2.7/site-packages/pytrainer/upgrade/versions/010_default_upgrade.sql... 2011-10-30 08:59:10,937|DEBUG|base|__init__|Script /home/arnd/bin/pytrainer/lib/python2.7/site-packages/pytrainer/upgrade/versions/010_default_upgrade.sql loaded successfully (whole log attached) But this isn't the migration itself, or? Is it possible to enforce it explicitely? As already said, my data is everything I recorded with pytrainer, therfore *rather* inhomogenous: pre-1.8.0 data, gpx-less data, splitted/paused records etc ;) greetz & thx for caring Arnd
log.out.gz
Description: GNU Zip compressed data
------------------------------------------------------------------------------ Get your Android app more play: Bring it to the BlackBerry PlayBook in minutes. BlackBerry App World™ now supports Android™ Apps for the BlackBerry® PlayBook™. Discover just how easy and simple it is! http://p.sf.net/sfu/android-dev2dev
_______________________________________________ Pytrainer-devel mailing list Pytrainer-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/pytrainer-devel
