On Wednesday, February 25, 2015 at 1:14:34 PM UTC-8, Niphlod wrote:
>
> .sql files are files filled with
>
> insert into table(col1, col2, col3) values ('a', 'b', 'c')
>I used to know that =8-O > > web2py can't parse them, and frankly, it doesn't need to. it's a job best > served by native tools. > it'll better to restore the dump using native tools, then read the > section on the book > <http://web2py.com/books/default/chapter/29/06/the-database-abstraction-layer#Legacy-databases-and-keyed-tables>, > > which basically resorts to: > Okay, I didn't look far enough on my first try. > 1. set migrate=true, fake_migrate_all=true > (more evidence that I didn't look far enough) > 2. create models accordingly > 3. verify that all works fine > 4. set fake_migrate_all=false > 5. continue working as usual with application development > > as previously pointed, 2. can be satisfied (for the most part) with the > extract_mysql_models.py > > I am happy to not have had to do much to do much migrating. The last time I had anything close, it was adding fields, and I was in a position to re-start with a clean slate, and use CSV files to import into the new tables via appadmin. One of these days my luck will run out, and I'll need the above instructions. Thanks for your patience. /dps -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
