Another thing: the wizard does not ask for, or create, certain settings
that are required by the code in models/db.py. so one cannot simply load
those settings and bind all values below:
if not request.env.web2py_runtime_gae:
# ---------------------------------------------------------------------
# if NOT running on Google App Engine use SQLite or other DB
# ---------------------------------------------------------------------
db = DAL(myconf.get('db.uri'),
pool_size=myconf.get('db.pool_size'),
migrate_enabled=myconf.get('db.migrate'),
check_reserved=['all'])
(pool_size and migrate) are not configured by the wizard, but they need to
be set somewhere for auto-created and manually created apps to be congruent.
On Tuesday, July 11, 2017 at 2:41:15 PM UTC-4, Terrence Brannon wrote:
>
> I am using the stable source code version of web2py. I created an
> application via the wizard and specified a MySQL database URI at that time.
>
> Now, 2 days later, I went looking for my data and realized it is in
> storage.sqlite... why? Because the automatically-created models/db.py
> attempts to connect to the database via AppConfig().get('db.uri')
>
> However models/0.py binds settings.database_uri to another value, which
> was set during the wizard dialogue.
>
> As a result, all of my data is in a SQLite database (because of the
> default setting of AppConfig().get('db.uri')) instead of being in the
> MySQL database I configured via the wizard dialogue.
>
> Has this been addressed in the bleeding edge versions of web2py?
>
--
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.
