Alberto Valverde <[EMAIL PROTECTED]> writes:
This should be possible in an app-independant way if database.py is implemented as middleware because all it would need is to peek into environ for REMOTE_USER (which an upper auth. layer has placed there) and pull or create a connection from the pool belonging to that user.
I was thinking more on changing the AUTH inside an already existing connection. Something exactly like what SET SESSION AUTHORIZATION or SET ROLE do: they change the identification of the user that is going to be performing the next commands inside the session in use. In the end, you reset the information for the "superuser" that was used initially. -- Jorge Godoy <[EMAIL PROTECTED]> --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears Trunk" 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-trunk?hl=en -~----------~----~----~----~------~----~------~--~---
