> > In summary, I am using sqlite db. There is a table that I don't wish to > store in the sqlite db, but yet have that particular table data be served / > accessed like a normal table (as if from the db). Is that possible, and how > can I achieve this? >
I don't think so. If you need to have reference fields to this table, then it must exist in the same SQLite database. If the data in the table are fairly static, maybe just create a new copy of the table within each app that needs it. > Why did I ask this question? Because I vaguely recall some very old > examples of web2py where items are inserted to a "virtual" table, that only > exists in that controller (it wasn't defined in the model). So only when > you call that controller, that particular table will be "loaded", and with > that particular set of data. If another controller tried to access that > table, that data had vanished. ...but it's so long ago I don't recall where > they are, the details of the code etc. I just remembered it was possible. > You can put a DAL *model definition* in a controller function so the model itself only exists in that controller, but the underlying database table will persist beyond requests to the controller (unless it is a SQLite memory database). Obviously, the data must be persisted somehow. Anthony -- 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.
