I've been using PythonAnywhere Postgres hosting for a while. Used pg_dump and pg_restore to recreate the database in ElephantSQL. Not sure if this has contributed to the problem, but had to use options that drop owner and privileges (otherwise pg_restore generated errors, complaining about non-existing roles etc.) In the end, everything works perfectly except that I must use migrate=false option only. If migrate=true - it attempts to recreate all the tables and, obviously, complains that tables already exist - because they do exist. Greatly appreciate suggestions on how to fix this.
A side question on efficiency: visually I notice that PythonAnywhere postgres hosting works quicker (but ElephantSQL is theoretically better hosting). Is it because in PA both app and db run "in close proximity", presumably on the same server? -- 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/abcae64b-e9b3-4d30-9ae7-98ff01cb51ban%40googlegroups.com.
