> On 4 Apr 2015, at 15:01, Niphlod <[email protected]> wrote: > > if you look at the source code, you'll see that it's just an ini parser by > default. > All that it does is speedup the "settings" part without users knowing > anything about python (think when you finish an app and you deploy it on a > system you may not have access to, or if you ship an app to your users) > > migrate = 1 or True in this case doesn't make a difference, since it's not > fetched. > However, the "migrate" implementation takes a "truey/falsey" value and > doesn't do strict type checking, so casting it to int would make it work fine. > > In case you'd like to pass your own cast function you can. > Beware: since it's made for speed, once you take out the "reload" on the > initialization, values will be stored indefinitely as they are fetched the > first time.
Sorry for late intromission. Is all of this documented in the book? If I got right, this can change the programer’s expectation about when the system parameters will be refreshed. Until now, it was refreshed on each request. Now, If I understood, it just occurs when the server is reloaded. Am I right? — Vinicius. -- 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.
