There are quite a few postings about this but I have never exactly understood how this is supposed to work. My expectation is that fake_migrate should work alongside migrate like this:
1. If migrate = True, fake_migrate = True: DB and .table files are both modified/migrated. 2. If migrate = True, fake_migrate = False: DB modified but .table files are not. 3. If migrate = False, fake_migrate = True: DB not modified but the .table files are (to correspond with the model). 4. If migrate = False, fake_migrate = False: Nothing is modified. Notes a. You always get an exception if Web2py cannot get the DB to correspond with the .table files. In that case you have to fiddle around and get the two singing off the same sheet. b. There is no way of creating a model or a .table file from an existing DB. If you search hard you'll find some hacked code that gives a head start, but really it's something you have to do by hand. Now, having written the above, I have two questions: 1. Are my expectations correct? (e.g. I think I'm wrong about 1?). 2. Why doesn't 3 seem to work? I cannot get fake_migrate to create a .table file. If it does not, could we please have a function that does so? Regards, -- David -- You received this message because you are subscribed to the Google Groups "web2py-users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/web2py?hl=en.
