I came across yserial and thought it would make a good sidekick for web2py!
http://yserial.sourceforge.net ( y_serial :: warehouse compressed Python objects with SQLite ) My idea is to capture into a temporary table ( SQLFactory??) a set of data records each containing several options (eg a test of multiple choice questions). These are transposed into a python object(dictionary/list of lists??) and serialised into another sqlite db managed by yserial thus all web2py stores in a relevant field is the yserial reference. When this 'Test' composed of sets of options is selected, it reconstructs from the py object back into a temporary table for presentation to the user by web2py as usual ( or written to XML or JSON) My Logic :-/ preliminary testing yserial seems to co-exist happily in web2py similar to a pickling system but more flexible this plan eliminates some complex joins in web2py a reference in one row in web2py table can access a complete 'Test' My question Is there any advance on the temp table thread ( maybe in new DAL ?) Following up some old threads on temporary tables but I noticed more recent posts with similar needs/ideas can the above idea be more easily done in pure web2py? any suggestions? (maybe it can be of use to others) web2py is great - this group rocks
