Hi Arnd, >> Can you please check ~/.pytrainer/log.out.1[2,3,4,5]? Logs are >> rotated and maybe there is useful info still there. > > OK, went into the (original) logs down to last december, but could not > find something enlightening (see below).
I understand. Those log entries are related to a check which is no longer in place. > Only thing I can try (w/o inspecting code, I'm a bit out of date here) > is once more rerun my backup data with a clean 1.8.0 and afterwards > apply 1.9.0-dev to it. Will do so later & report. That would be great because we need to find out the root cause for migration scripts not being executed. > As far as I understand my data is in a zombie state. Proper migration > isn't triggered, but on the other hand data aren't migrated, as I can't > access any record details. Actually what we know is that you miss "laptrigger" column in "laps" table, but we don't know if all others columns have been properly populated. To inspect this point you can do the following from command line: 1.- Access pytrainer's database (if I am not wrong you use sqlite): $ sqlite3 ~/.pytrainer/pytrainer.ddbb 2.- Check "laps" table structure: sqlite> .schema laps 3.- See how laps table is populated: sqlite> select * from laps; Anyway, _before_ any change in pytrainer's database, a backup copy is made appending date and time info to gzipped file (available under ~/.pytrainer/) Regards, David ------------------------------------------------------------------------------ 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
