[web2py] Re: migration reboot

2010-01-15 Thread kbochert
How about: 1. Save the database with "db.export_to_csv_file(open('somefile.csv', 'wb'))" -- The csv file should only contain columns defined in the current database. I have not checked this - seems reasonable. 2. Erase the entire contents of applications\myapp\databases -- This includes the

Re: [web2py] Re: migration reboot

2010-01-15 Thread Jeff Bauer
On 01/15/2010 03:36 PM, mdipierro wrote: On Jan 15, 3:24 pm, Jeff Bauer wrote: Use case: When I access my database outside of DAL, I've got a bunch of old columns that are no longer in use. I assume you use sqlite. sqlite cannot drop columns.With a different database (if migrate!=False) the d

[web2py] Re: migration reboot

2010-01-15 Thread mdipierro
On Jan 15, 3:24 pm, Jeff Bauer wrote: > Automatic database migration in web2py is great.  However, > after a few dozen iterations during development, I'd like > to 'reboot' through all the cruft and set database fields to > agree with my models.  I'm aware that I could go through and > set migrati