<blushing> I think the test sequence below verifies that the problem was mine and not web2py's. Basically, I thought I had removed all the .table and storage files from version control, but it turns out I missed a few. This was causing all sorts of problems as I went back and forth between the development host and the PDA target, especially since I was making changes and committing them from either side!
Once I tracked down and removed, (hopefully) all the offending files, everything regenerated and I'm now able to make and propagate model changes from either end. That's one h*ll of a system, Massimo! Consider this an enthusiastic testimonial. My apologies for taking up so much of the group's bandwidth and I do really appreciate all the support. Hopefully this thread can be of some use to the next newbie who tries cross develop between hosts. Cheers, Mike ON DEVELOPMENT HOST (Macbook) 1. Removed everything in my app's databases folder from version control (SVN) and deleted all files from the folder. 2. Changed migrate to True for all tables in db.py. Committed changes to SVN 3. Restarted web2py 4. Added sample values to the 4 tables that hold the allowed values for the fields in my 'config' table. The latter is presented as a SQLForm from the app's index page and has 4 fields that match the 4 tables of allowed values. 5. Went to the index page for my app and entered values in the form. Clicked submit. No errors. So far so good. ON PDA TARGET (N800) 6. Removed databases/*.table from SVN and deleted all files. Updated from SVN to get changes (migrate=True) committed from development host. 7. Started web2py 8. Added sample values and then entered values in index page (as in steps 4 & 5 above). No errors ON DEVELOPMENT HOST 9. With web2py still running, Add extra field to 'config' table and added correponding allowed value table in db.py 10. Browse to index page. New field appears in form. Excellent! 11. Add sample values to new field's table using Database Admin page. 12. Back to index page, fill in all fields. Submit. Success! 13. Commit changed db.py to SVN. ON PDA TARGET 14. With web2py still running, update from SVN to get changed db.py file. 15. Test as in steps 10 - 12 above. Success! 16. Edit db.py to remove extra field and table creation. Commit to SVN. 17. Visit index page. Verify that deleted field is not in form and everything still works. ON DEVELOPMENT HOST 18. With web2py still running, update from SVN. 19. Visit index page. Deleted field is gone and everything still works. Amazing! Cheers, Mike On Jul 1, 8:45 am, MikeEllis <michael.f.el...@gmail.com> wrote: > I'm confused, too! > > Tables were created by web2py > yes, they are sqlite tables > > This is important for me to resolve, so I'm going to spend some time > trying to reliably reproduce the problem in as few steps as possible. > > Thanks again for the help, web2py is a truly impressive product and I > really want to make it work for this application. > > Mike > > On Jun 30, 7:57 pm, mdipierro <mdipie...@cs.depaul.edu> wrote: > > > Now I am confused. migrate=False is not an alterantive to migrate=True > > when the latter is not working. > > > before you take any action: > > > are you trying to access tables created by web2py? > > if yes, are these sqlite tables? > > if no, did you change username/password? > > if yes. let me know because your .table files got corrupted > > but they can be recoevered > > if no, migrate=False is the only choice. web2py cannot migrate > > preexisting tables. > > > In all other cases... did you move the content of the databases > > folder? Did you rename any of the files in there? > > > Massimo > > > On Jun 30, 4:07 pm, MikeEllis <michael.f.el...@gmail.com> wrote: > > > > Thanks Fran, that makes it much clearer. It would be nice if > > > migrate=True worked as described in the manual, but I can live with > > > migrate=False for the time being. Just have to make sure to get my > > > table designs correct from the start (LOL). > > > Cheers, > > > Mike > > > > On Jun 30, 4:52 pm, Fran <francisb...@googlemail.com> wrote: > > > > > On Jun 30, 4:57 pm, MikeEllis <michael.f.el...@gmail.com> wrote: > > > > > > doesn't migrate=False prevent me from altering the > > > > > table's structure within a running instance of web2py? > > > > > Mostly correct - migrate=False means that Web2Py doesn't try to create > > > > the Table, but assumes this exists already. > > > > > > am I misunderstanding > > > > > what migrate=False does? I'm assuming it means the table will be > > > > > dropped with all its data and a new one will be created? > > > > > No it won't drop the table/data - migrate=False simply means that only > > > > Table Data not Structure is editable. > > > > > F > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web2py Web Framework" group. To post to this group, send email to web2py@googlegroups.com To unsubscribe from this group, send email to web2py+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/web2py?hl=en -~----------~----~----~----~------~----~------~--~---
