On Dec 6, 1:32 am, mdipierro <[EMAIL PROTECTED]> wrote: > I am still unsure on what specifically caused the problem but I see > one issure right away. In your model you have migrate=True (which > means web2py should create the tables) but you your pg_dump you have > "CREATE TABLE" statements. This means when you restore tha database > postgresql creates the tables and, web2py does not know, and tries do > it again.
OK. But I copied whole app, and in database I found serialized model for each table. While this worked on other machine I thought that copying whole app and restoring database from dump should work. > This may not be the end of the story but it is part of it. > clean everything in databases, restore the pg_dump and set all > migrate=False before starting your app again. > Let me know. I changed/added migrate=False to each table definition and that not helped: in console I got gluon.restricted.RestrictedError, in web interface ticket without stack trace. Maybe there is something with web2py version while I use newest 1.52, but on other machine it was some earlier version. I don't remeber but it probably was 1.49. Maybe some serialize object changed? Massimo, have you received zipped copy of app and pg_dump? Regards, Michał Niklas --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web2py Web Framework" group. To post to this group, send email to web2py@googlegroups.com 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 -~----------~----~----~----~------~----~------~--~---
