OK, so I had a migration issue with my DB some time ago, the easy fix
was migrate=False on all of my tables. I knew this was a bad fix,
because it was a short-term solution. I get the error "Table feed
already exists" now this is true, so instead of trying to create the
table, skip the procedure of creating it?
I cleared out my databases folder
I added migrate=False to all of my folders
then I added a field through mysql onto my table "feed".
I wanted the field ("to_player") to be recognized by web2py. I get
this error when I try to db.feed.to_player
OperationalError: (1054, "Unknown column 'feed.to_player' in 'on
clause'")
mysql> show fields from feed;
+--------------+----------+------+-----+---------+----------------+
| Field | Type | Null | Key | Default | Extra |
+--------------+----------+------+-----+---------+----------------+
| id | int(11) | NO | PRI | NULL | auto_increment |
| account_id | int(11) | YES | MUL | NULL | |
| to_player | int(11) | NO | | NULL | |
| date_created | datetime | YES | | NULL | |
| message | longtext | YES | | NULL | |
+--------------+----------+------+-----+---------+----------------+
5 rows in set (0.00 sec)
Does this make sense in the way on how web2py is structured?
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"web2py Web Framework" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/web2py?hl=en
-~----------~----~----~----~------~----~------~--~---
