Also, I'm assuming you've also read through this: http://web2py.com/books/default/chapter/29/06/the-database-abstraction-layer?search=migrate#Other-DAL-constructor-parameters
-Jim On Tuesday, February 7, 2017 at 9:14:54 AM UTC-6, Jim S wrote: > > Can you show the migrate options you've tried? > > I do this all the time with MySQL and it works great. > > Another possibility is that it ran through migration already on a > different instance of the database. If so, turn on fake_migrate_all and > remove the column. That should remove it from the files in the databases > folder. Then turn on migration and add the column back. There is a file, > sql.log, in the databases folder that should show you all the sql > statements that were run for you by the migration. > > Hope that helps. > > -Jim > > On Tuesday, February 7, 2017 at 9:00:02 AM UTC-6, Martin wrote: >> >> Still having this issue! Do the migration not work for mysql databases? I >> never had this problem with sqlite, but for various reasons I cannot use an >> sqlite database. >> >> I have now also tried manually adding the field by altering the table in >> the database and can then start the app. However, when trying to add values >> to the field in the admin ui the same problem arises. The field is of type >> string:list. >> > -- 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.
