It looks like there is a bug: In tools.py ( http://code.google.com/p/web2py/source/browse/gluon/tools.py#1515):
migrate=self.__get_migrate( settings.table_event_name, migrate) should be: migrate=self.__get_migrate( settings.table_cas_name, migrate) It doesn't cause a problem when migrate=True, but when migrate is set to a string prefix, it will try to use the auth_event migration file for the auth_cas table, and I think it may actually trigger a migration of the auth_event table (in addition to skipping creation of the auth_cas table). Anthony On Sunday, June 10, 2012 7:10:23 PM UTC-4, Brad Miller wrote: > > Alright I've done some more investigating, I've backed out the changes I > made to my app over the last couple of days and it is related to the > migrate option. > > On a clean database, (sqlite or postgresql) when call auth.define_tables > like this: > > auth.define_tables(migrate='myprefix') > > Then auth_cas does not get created. > > If I go back to auth.define_tables(migrate=True) > > Then it works and auth_cas is created. > > Brad > > On Sunday, June 10, 2012 5:44:58 PM UTC-5, Brad Miller wrote: >> >> Hi, >> >> I recently upgraded from 1.99.4 to 1.99.7 on my webfaction server. I >> just did a clean checkout of my repo into a beta app folder under >> applications. I have two databases set up. One for production, and one >> for testing. I dropped all the tables in my beta database. The databases >> folder was completely empty. Then I brought up the app. Error! >> >> S'<class \'psycopg2.ProgrammingError\'> relation "auth_cas" does not >> exist\n' >> >> there is no auth_cas.table file. >> The sql.log file has no entry for creating auth_cas, However there is >> this line: >> >> timestamp: 2012-06-10T17:29:31.032641 >> ALTER TABLE auth_cas ADD service VARCHAR(512); >> >> The following tables are created: >> auth_user >> auth_group >> auth_membership >> auth_permission >> auth_event >> >> What can I do to get past this? >> >> Brad >> > On Sunday, June 10, 2012 7:10:23 PM UTC-4, Brad Miller wrote: > > Alright I've done some more investigating, I've backed out the changes I > made to my app over the last couple of days and it is related to the > migrate option. > > On a clean database, (sqlite or postgresql) when call auth.define_tables > like this: > > auth.define_tables(migrate='myprefix') > > Then auth_cas does not get created. > > If I go back to auth.define_tables(migrate=True) > > Then it works and auth_cas is created. > > Brad > > On Sunday, June 10, 2012 5:44:58 PM UTC-5, Brad Miller wrote: >> >> Hi, >> >> I recently upgraded from 1.99.4 to 1.99.7 on my webfaction server. I >> just did a clean checkout of my repo into a beta app folder under >> applications. I have two databases set up. One for production, and one >> for testing. I dropped all the tables in my beta database. The databases >> folder was completely empty. Then I brought up the app. Error! >> >> S'<class \'psycopg2.ProgrammingError\'> relation "auth_cas" does not >> exist\n' >> >> there is no auth_cas.table file. >> The sql.log file has no entry for creating auth_cas, However there is >> this line: >> >> timestamp: 2012-06-10T17:29:31.032641 >> ALTER TABLE auth_cas ADD service VARCHAR(512); >> >> The following tables are created: >> auth_user >> auth_group >> auth_membership >> auth_permission >> auth_event >> >> What can I do to get past this? >> >> Brad >> >
