.sql files are files filled with
insert into table(col1, col2, col3) values ('a', 'b', 'c')
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:
1. set migrate=true, fake_migrate_all=true
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
--
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.
