On Jan 4, 2007, at 2:15 AM, Jorge Godoy wrote:
One of the most problematic things I see with ORMs and web apps in
general is
the auth (both auths) part with the database.
Ideally one would be able to open a connection (to reuse a pool of
connections) and immediately change to another user (usually one DB
user per
app user, but it isn't necessarily true) so that there is a stronger
protective layer on the database. Today we simply connect to the
DB and have
to use specific SQL commands for that -- when people know that they
can do
that... -- or we have to have some inefficient connection mechanism.
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.
Alberto
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
