Don't understand exactly your problem... When it is dropped it gone most of the time... If you talk about the file of SQLite in database folder and if you are under mercurial version control as you seems to be, may be you can recover your old SQLite file if you haven't commit your change yet.
SQL.log if you had activated it could help maybe, but if your old database have been generated by web2py as long as you where creating it (migrating=true) your database have been created by little piece of DDL trought out your work... It will be difficult to resynthetise all your database from these SQL instruction... Richard On Tue, May 3, 2011 at 5:26 PM, pbreit <[email protected]> wrote: > I am having trouble getting a column added to a Postgres table. Have I made > an unrecoverable error in deleting the *.table files without backing up? Is > there any way to recover short of dropping the DB? I can regenerate the > /table files of course but are they incompatible with the existing DB? > > I have tried various combinations of migrate, fake_migrate, migrate_enabled > and fake_migrate_all set to True/False. I'm not sure what these do exactly > and how and when to use them. > > Is it OK to add a new Field() in the middle or do I need to add it at the > end? > > Would one solution be to manually edit my DB so that it matches sql.log? > > Also, can someone suggest a strategy for what to hgignore in the databases > directory? I currently am ignoring *.table and storage.sqlite locally and > databases/* on my servers. Does that sound right? >
