I just downloaded and tested the latest source for testers on GAE. Migration does work perfectly for the tables inside the models but still does not work for the "auth.settings.extra_fields['auth_user'] = (...Fields)" It is no big deal for me as I have installed phpMyAdmin (as an app version) and manually created the extra field for auth_user table but just so you know it.
Thanks for the update! On Saturday, 28 March 2015 17:29:24 UTC+1, Massimo Di Pierro wrote: > > http://web2py.com/examples/default/download > > On Saturday, 28 March 2015 11:14:44 UTC-5, Sébastien Loix wrote: >> >> Hello Massimo, >> Where can I find the version for tester? >> Also I am using SQL with MySQL with GAE through Cloud SQL, so the >> check_reserved keywords is necessary right? >> >> Once I have the new version I will test it and report here. >> Thanks >> >> >> El martes, 24 de marzo de 2015, 17:32:09 (UTC+1), Massimo Di Pierro >> escribió: >>> >>> I spoke too soon. Please wait I post a new version for testers. I will >>> email this list. >>> Then try: >>> >>> db = DAL('google:sql://[app-name]:[db-name]/[table-name]') >>> ... >>> auth.settings.extra_fields['auth_user'] = [Field('username_fb', >>> length=128, default="", unique=True, writable=False, readable=False)] >>> auth.define_tables(username=False, signature=False) >>> >>> consider that migrate_enabled is true by default so no need to set it. >>> Also the check_reserved keywords is designed for SQL and not GAE. It does >>> not hurt but it is not necessary. I do not swear by lazy_table because they >>> have some caveats. Let's try without that. >>> >>> Can you help us check if this work? If, not what behaviour do you see? >>> Do you get a traceback? >>> >>> >>> On Tuesday, 24 March 2015 11:18:06 UTC-5, Sébastien Loix wrote: >>>> >>>> Thank you for the answer. >>>> Could you explain a bit more the "there are no migrations on GAE", is >>>> it only for the actual version and the fixed version will solve it? >>>> I realised that I am using the 2.10.0-beta version of web2py. The one >>>> downloaded from the main download page. >>>> Thanks for the help >>>> >>>> El martes, 24 de marzo de 2015, 8:31:51 (UTC+1), Massimo Di Pierro >>>> escribió: >>>>> >>>>> 1) there are no migrations on GAE, web2py will still create .table >>>>> files but they serve no purpose. >>>>> 2) GAE support is broken in 2.9.12. It works in trunk pydal and we >>>>> will released a fixed version this week >>>>> >>>>> On Monday, 23 March 2015 21:53:04 UTC-5, Sébastien Loix wrote: >>>>>> >>>>>> Hi, >>>>>> >>>>>> I am having difficulties with table migration on GAE. >>>>>> >>>>>> I deployed perfectly in the Google App Engine and everything is >>>>>> working fine. >>>>>> >>>>>> I then needed to make some change in the auth_user adding some extra >>>>>> field but when I deploy again the new version, the migration doesn't >>>>>> occur >>>>>> and the new column is not created. >>>>>> >>>>>> Here is the code used: >>>>>> >>>>>> db = DAL('google:sql://[app-name]:[db-name]/[table-name]', >>>>>> migrate_enabled=True, check_reserved=['all'], lazy_tables=True) >>>>>> >>>>>> then below: >>>>>> >>>>>> auth.settings.extra_fields['auth_user'] = [Field('username_fb', >>>>>> length=128, default="", unique=True, writable=False, readable=False)] >>>>>> auth.define_tables(username=False, signature=False, migrate=True) >>>>>> >>>>>> Any idea why the migration doesn't occur? >>>>>> >>>>>> Is there a way to force web2py to do migration somehow? >>>>>> >>>>>> Thanks for the help! >>>>>> Best, >>>>>> Sebastian >>>>>> >>>>> -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to web2py+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
