lazy_table supposed to do just that no?
Richard
On Thu, Jan 16, 2014 at 3:34 AM, Arnon Marcus a.m.mar...@gmail.com wrote:
Our schema is quite large (200+ Tables) and changes very seldom.
I was thinking, is there a way to not have to rebuild it in it's entierty
on every request?
I mean, is there a way to seperate-out the schema definition from the
connection object? Ideally, I would put the schema definition code in a
separate module in the modulesz folder, and import it into the model file
that creates the connecfion, and somehow pass the ready-made
schema-object(s) into the newly-created connection object on each request.
Can this be done?
What are the gotchas for this (if any)?
Are there restrictions for somed schema-definitions tbat can not be used
like this?
--
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.
For more options, visit https://groups.google.com/groups/opt_out.
--
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.
For more options, visit https://groups.google.com/groups/opt_out.
