I have probably the same issue. After it popped up and I couldn't resolve it I have manually added the fields to postgre.
As I understand fake migrate it will regenerate the data needed for migrate. So after a fake migrate adding a field and the normal migrate should work out great. It dosen't. It tries to migrate on every table that has a reference field and fail with foreign key exists for Postgre. I think there is some bug recording foreign key field (By fake migrate) in the Postgre DAL driver. kl. 15:13:34 UTC+1 fredag 12. desember 2014 skrev Niphlod følgende: > > nope, can't reproduce the issue. Something very weird is going on on your > development system. > > -- 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.
