Hi all, In TG 1.0.8, with Identity enabled and using SA, each page load causes quite a number of requests to Identity tables.
In a fresh, quickstarted project, loading the Welcome page as an authenticated caused 18 database SELECTs - 6 duplicates of this: SELECT visit.visit_key AS visit_visit_key, visit.created AS visit_created, visit.expiry AS visit_expiry FROM visit WHERE visit.visit_key = ? ['my_key'] SELECT visit_identity.visit_key AS visit_identity_visit_key, visit_identity.user_id AS visit_identity_user_id FROM visit_identity WHERE visit_identity.visit_key = ? ORDER BY visit_identity.oid LIMIT 1 OFFSET 0 ['my_key'] SELECT tg_user.password AS tg_user_password, tg_user.user_id AS tg_user_user_id, tg_user.user_name AS tg_user_user_name, tg_user.email_address AS tg_user_email_address, tg_user.display_name AS tg_user_display_name, tg_user.created AS tg_user_created FROM tg_user WHERE tg_user.user_id = ? [1] Is there a way to store authenticated sessions in the CherryPy session? Or some other method to reduce the DB overhead of identity? Thanks! James --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/turbogears?hl=en -~----------~----~----~----~------~----~------~--~---
