I installed web2py 2 times, once for development and once for production.
The db.py file in the development version has the following connection
string:
db = DAL('postgres://username:password@localhost:5432/db_development',
lazy_tables=True, migrate_enabled=False, pool_size=1,
check_reserved=['all'])
The db.py file in the deployment version has the following connection
string:
db = DAL('postgres://username:password@localhost:5432/db_deployment',
lazy_tables=True, migrate_enabled=False, pool_size=0,
check_reserved=['all'])
In both db.py files auth_define_tables has the following settings:
auth.define_tables(migrate=False, username=True, signature=False)
Now when I alter a table and migrate the changes the development version
migrates the changes without problem. however, the deployment version
returns
an error ticket telling me "table_auth_user already exists". Since the only
difference between the applications is the pool_size setting in the
connection string
I wonder whether this causes the error. I set pool_size = 0 because at
webfaction pool_size = 1 causes performance issues.
Kind regards,
Annet
--
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.
