Thank you both the migrate was set to false on the table I was on excellent
I had tried deleting stuff in /databases but was not sure on the file name which should go sorting the migrate has fixed the immediate annoyance much appreciated and great response time thank you On Mar 27, 12:47 am, Anthony <abasta...@gmail.com> wrote: > Check the sections in the book about Migrations > (http://web2py.com/book/default/chapter/06#Migrations) and "Fixing Broken > Migrations" > (http://web2py.com/book/default/chapter/06#Fixing-Broken-Migrations). web2py > stores migration information for each table in files in the 'databases' > folder (so you may need to delete or fix them). Also, if you're expecting > some migrations but not seeing them, make sure you don't have 'migrate' set > to False. > > Anthony > > > > > > > > On Saturday, March 26, 2011 8:34:29 PM UTC-4, fib wrote: > > Hi all > > > I am learning the ropes so to speak and am using a remote mysql as a > > db > > I have sorted out the tables from legacy db to be generated by web2py > > along with the auth tables > > > I need to know what the quick way is to reset the db - as i learn and > > make mistakes > > in previous times I would just drop a table and I had assumed from > > what I read web2p would find it missing and reinstall / generate > > > This is not the case and when i make changes they do not seem to > > update the tables > > I cannot pack and reinstall because it remembers DB state > > > So I end up creating a new simple app and dropping in the files i used > > before db.py, default.py and any views etc I have altered > > then the system resets and lets me move on > > > there must be a better way? > > > Thank you in advance for your time > > newbie apologies
