Subject | Re: [Firebird-Architect] Re: User name SYSDBA |
---|---|
Author | Nando Dessena |
Post date | 2005-08-09T13:25:28Z |
Dmitry, Helen,
H> necessary (or even rational) to defer authorisation until execution
H> time.
two things come to mind:
1) to be able to cache prepared statements across different
transactions/connections/users.
2) to implement row-level security.
Ciao
--
Nando Dessena
http://www.flamerobin.org
>>The question is not whether it can be done at the execution time but whetherH> Me too. I've been really struggling to understand why it would ever be
>>it should be. IIRC, the SQL spec explicitly requires permissions to be
>>checked at the prepare time. And it makes a lot of sense to me.
H> necessary (or even rational) to defer authorisation until execution
H> time.
two things come to mind:
1) to be able to cache prepared statements across different
transactions/connections/users.
2) to implement row-level security.
Ciao
--
Nando Dessena
http://www.flamerobin.org