Thank you, Anthony! But I think, that this fact ( web2py does not migrate changes in attributes) makes web2py unsuitable for db-schema development, i.e. I have to consider all the details and write holy code at once. The situation gets worse by the fact that migrate is only half-migrate without any warnings - it may be better to have a log-file with something like "table ... was migrated, but attributes ...... were not changed " It would be nice to have something like DAL-construction-mode, when changing tables definition causes dropping all tables (except auth_* ) and recreating from scratch
On Saturday, October 8, 2016 at 4:43:58 PM UTC+3, Anthony wrote: > > From the book: > > Notice that web2py only migrates new columns, removed columns, and changes >> in column type (except in sqlite). web2py does not migrate changes in >> attributes such as changes in the values of default, unique, notnull, >> and ondelete. >> > > In particular, when adding "notnull", you must first replace any existing > null values with something, and the DAL wouldn't know what value to use > (though I suppose it could assume the "default" value if one has been set). > Similarly for adding "unique", you must first resolve any existing > duplicates. > > Anthony > -- 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
