It is the way the repoze.who and repoze.what sqlalchemy plugins work that makes that happen. It should be quite easy to implement your own identificator and authenticator to avoid multiple look ups. Just fill all the request.identity related dictionaries to keep compatibility with the predicates.
On Mon, Aug 1, 2011 at 1:15 PM, Mengu <[email protected]> wrote: > Hi all, > > I don't know if it's repoze.who or TurboGears doing that but in every > request it sends 3 db requests to user, group and the permission > tables. Why is this necessary? I don't want this to happen. This > information can stay in session until it expires. Please lighten my > way here. > > -- > 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. > > -- 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.
