Re: [Firebird-devel] Global Connection Context Variables?

[Jim S. <ja...@ne...>]

Dmitry Yemanov wrote:

>"Thomas Steinmaurer" <ts...@ib...> wrote:
>  
>
>>I don't really know, how I should call the following,
>>or other DBMS call that. Well, I'll try to explain,
>>what I mean.
>>    
>>
>
>Think about a combination of connection-level temporary tables and two
>stored SQL functions (GET_VAR + SET_VAR). Both these features conform to the
>SQL standard and gives you the same abilities as connection context
>variables. And both are in our TODO lists.
>  
>
The SQL standard and almost all database implementations concern 
themselves only with database connections.  The rest of the world, 
however, is web based, which is not connection based.  Looking to the 
standard is not going to solve the problem.

Netfrastructure manages sessions with Java application objects.  Each 
application is defined with an application name and application class 
name.  The session manager creates a session by assigning a session id 
and creating an instance of the application objects.  Subsequent 
connections are associated with the session object by session id.  
Session state is carried by the session object, and is necessarily 
application specific.

Session management requires a more sophisticated security management 
model than provided by the SQL standard.  Netfrastructure uses a 
multiple role model where a set of roles, some active, some latent, are 
associated with a database account.  The session object, based on what 
it knows about the client and the type of database activity, can 
activate and deactivate roles as required, which delegates security 
checking to the database system rather than user code.

If you want a solution to a problem, look to your own resources, not the 
SQL standard.

-- 

Jim Starkey
Netfrastructure, Inc.
978 526-1376