LOL - Make sure you use stable "Version 2.0.9 (2012-09-13 23:51:30)" of the latest trunk. Not any intermediate version. - do not use the wizard if you do not want crap. The wizard is experimental and not the best piece of web2py. - If your tables already exist and you are happy with them run onces with db = DAL(....,fake_migrate=True) and then run with DAL(...,migrate=false) - If instead you want web2py to create tables and use migrations, delete you database, re-create it empty, delete everything under yourapp/databases/ and run with DAL(...,migrate=True).
On Monday, 8 October 2012 17:33:06 UTC-5, Bill Thayer wrote: > > Ok, > > I have my Oracle database. From some attempted migrations I have the auth > tables defined and two other tables defined of about 17 tables.The typical > error is Object with that name already exists or some crap like that. I > figured clicking the clean button would help... DON"T DO THAT! Now my > browser just spins and spins. > > My SQL log has a bunch of crap that i do not want created in my database > like archive tables that the wizard created. Yet if I delete the log file > it will not re-create with a fresh log. > > After restoiring my backup my sql.log file has 2627 lines in it and the > time stamps go back 6 days when I started this all from scratch. > > Without having to re-create my application again. How can i just get a > nice clean SQL file and how, once connect to my DB can I get my new db.py > or db_wizard.py definitions to make the database tables that aren't already > created without throwing errors for the ones that already are? > > > > > > > > > > > > --
