[TurboGears] Re: Change to IdentityProvider API

[Jeff Watkins]

Um... Revision 385 also introduces another column to the TG_SecretToken table: expiry. You'll need to rebuild that table some how. I think SQLObject has a way to do this, but I've never bothered to find out. On 27 Dec, 2005, at 4:23 pm, [EMAIL PROTECTED] wrote: Hello Jeff, identity management worked great for me so far, I really like it! I have setup a small login/logout/show current user application based on the docs from http://trac.turbogears.org/turbogears/wiki/IdentityManagement but unfortunately the new revision 385 breaks the apps, I only get: [...] "/usr/lib/python2.4/site-packages/SQLObject-0.7.0-py2.4.egg/sqlobject/mysql/mysqlconnection.py", line 60, in _executeRetry     return cursor.execute(query)   File "/usr/lib/python2.4/site-packages/MySQLdb/cursors.py", line 137, in execute     self.errorhandler(self, exc, value)   File "/usr/lib/python2.4/site-packages/MySQLdb/connections.py", line 33, in defaulterrorhandler     raise errorclass, errorvalue OperationalError: (1054, "Unknown column 'expiry' in 'field list'") Is there some documentation how to setup identity management with the new provider or a howto what to change in current apps? With best Regards, Fabian Erbach -- Jeff Watkins http://newburyportion.com/ “In science it often happens that scientists say, ‘You know that’s a really good argument; my position is mistaken,’ and then they actually change their minds and you never hear that old view from them again. They really do it. It doesn’t happen as often as it should, because scientists are human and change is sometimes painful. But it happens every day. I cannot recall the last time something like that happened in politics or religion.” Carl Sagan, 1987