I don't normally have migration problems, but I came up today with a new
way to have some "fun".
I had added a new table (including a reference field), and it was good.
That migrate was successful. I could run a -S -M shell, and populate the
table. That was yesterday. Today I had a source control glitch, and
models/myapp.py was reverted to before the new table (adding to the fun, I
couldn't find any editor artifacts to help speed the recovery). Using the
postgres schema, I recreate the define_table(). And started going through
the migrate and fake_migrate settings, without being able to access the new
table from the -S -M shell any more. I've tweaked all 4 settings (db
migrate, db fake_migrate_all, table migrate, table fake_migrate) and
haven't gotten them right.
I should note that this app has 3 DAL objects, 2 of them for sqlite3 and 1
for postgres (9.2.4). The new table is in the 3rd object ("dby"), and the
main table for the app is also in the postgres dby object. The main table
is working fine.
I tried deleting the newtable.table file, and it doesn't get recreated.
The sql.log hasn't any new entries.
The table isn't a central part of the application, but a tool for analyzing
data from the main table. It isn't yet used in a controller function, and
I can still access it from psql, but it may get added to a controller at
some point.
I'm ready for some hand-holding.
/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 web2py+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/web2py/7dec3876-ee81-4316-b0c2-f431f29b0389%40googlegroups.com.
