I have the same problem. Fake migrate didn't work. Tried deleting table in
"databases" folder, stopped and started PostGres and w2p servers, etc.
Any ideas I can try?
db = DAL('postgres://postgres:myPasswrod@localhost:5432/postgres', migrate=
False,fake_migrate=True )
*ProgrammingError: column
This finally worked.
ALTER TABLE RelationshipType ADD COLUMN relationship_type_name varchar(512);
Can it be assumed that it is generally easier doing DB work on the Postgres
side and just leaving w2p set to migrate = False?
Alex
--
Resources:
- http://web2py.com
- http://web2py.com/book
As a web2py user with a few months of experience, this is my experience
with migrations:
- Most of the time they work, specially if you use PostgreSQL
- Sometimes they won't, and fake_migrate plus the sql log usually help
to fix it.
- In very rare occasions, fake_migrate might
We might need to see your model and then information about your database
columns.
I'm just getting ready to switch from development mode to production and am
getting worried about managing my Postgres (since now I don't worry about it
and just re-create the DB when I make big schema changes).
See the book, chapter 6 fixing broken migration. Here is an excerpt,
good luck:
The solution consists of disabling migrations for all tables and
enabling fake migrations:
db.define_table(,migrate=False,fake_migrate=True)
This will rebuild web2py metadata about the table according to the
5 matches
Mail list logo
