Hi, >> - Started pytrainer in debug mode so I can check log files afterwords >> >> - I can access to existing activity without errors. > > That's good to hear :)
I will work with more activities when migrating from 1.7.1 to see if this makes any difference. >> Only thing I noticed is that files under upgrade/versions/ were loaded >> many times; not sure if needed or that can be fixed. > > During our migration process we ask sqlalchemy-migrate multiple times > what the current version is and what the available version is. Each > time we do so, it loads all upgrade scripts (whatever that means - I > guess just reading the dir contents and inspecting the file names for > the version numbers). We could reduce this by caching the result of > any sqlalchemy-migrate API calls. I didn't do this though because > getting spammed with that logging is annoying but it doesn't > significantly affect performance. Also, I figured such caching should > be done by sqlalchemy-migrate, not us. That makes sense, thanks! 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
