working with temp tables in any webapp is kinda scary, just because temp tables (at least in sql world) are actually though to survive an entire "connection". If instead you mean "temp table" as a real table, that gets created and dropped (so, managed) entirely by your application, again you'll find hard times managing concurrency, auto-expiration and such. If strictly needed, I'd go with a fixed table ... something like user_id ref_id 1 2 1 10 1 16
with indexes on both fields and manage the join as db.x.art_id = db.fixed.ref_id & db.fixed.user_id == 1 . You can then manage expiration, renewal, updates, and such just doing db(db.fixed.user_id == 1).delete(), etc. -- 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.
