> -----Original Message-----
> From: Firebird-Architect@yahoogroups.com
> [mailto:Firebird-Architect@yahoogroups.com]On Behalf Of johnson_dave2003
> Sent: Martes, 09 de Agosto de 2005 8:24
>
> The traditional work around has been to open up the database with a
> generic user ID for the connection pool (Jim would say no security),
> and handle the authorization in the application.

The traditional solution has been to create SQL views.
:-)

If all requests are going to be invalidated when a role is switched
dynamically, I really do not see the big difference with reattaching to the
db. I wish there was a way to calculate those permissions quickly.
Otherwise, we are defeating the advantage of cached requests: they will be
only be valid for the current connection and while roles don't change.

C.