Hi, >> The "trigger" column does not exist in 1.8.0 so I suspect the data you >> are upgrading has already been modified by an earlier 1.9.0-dev >> version. This may be the same problem Arnd is having. > > Oups, I certainly made a mistake in the past but I can't remember when > because I try to not mix data from test and stable environment... > Anyway, I did applied the tip proposed in ticket 130 before launching > pytrainer and then migration process went well.
Good to know that root cause was found on both Pierre's and Arnd's cases. What I find strange is that correspondant migration script wasn't trigger, so there is no real comparison between current user's database schema and pytrainer's official (desirable) one. Maybe we should work on providing "database sanity check" (as command line option) so user's database is compared with what it should be to make troubleshooting easier. 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
