Thanks Niphlod. Deleting the database fixed it. I had encountered a few similar errors in the past where deleting the database fixed it. However, this is the first one I've come across where the app would still partially work and not fail immediately at startup.
Sounds like SQLite may not even be a good choice for development considering the bug, chasing fantom errors due to how it handles altered tables/columns. Is there a dbms you suggest that works most nicely with web2py for small applications? From my very minor experience and only reading on the web, I see few negatives with Postgres. Thanks again. -- 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/groups/opt_out.
