As a web2py user with a few months of experience, this is my experience with migrations:
- Most of the time they work, specially if you use PostgreSQL - Sometimes they won't, and fake_migrate plus the sql log usually help to fix it. - In very rare occasions, fake_migrate might actually make things worse, like not resizing a char field when you change it in the model. I think migrations are one of the strengths of web2py, but they're not perfect. You learn to work around what breaks them, and to double check on deployment. Yes, occasionally you will fix the production database because it didn't migrate smoothly, even if testing did. On Sunday, January 31, 2016 at 1:52:33 PM UTC-6, Alex Glaros wrote: > > This finally worked. > > ALTER TABLE RelationshipType ADD COLUMN relationship_type_name varchar(512 > ); > > Can it be assumed that it is generally easier doing DB work on the > Postgres side and just leaving w2p set to migrate = False? > > Alex > -- 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.
