User can create global context variables in context of database. [CORE2048] #2484
Comments
|
Commented by: Ain Valtin (ain) Kind of similar request: |
|
Commented by: Sean Leyne (seanleyne) 1 - Session variables are already released when the current user session is disconnected! What else do you need for the User variables? 2 - As Ain has already outlined, System/namespace variables is already noted as a Feature Request. 3 - There is already a Feature Request to support the scheduled execution of SPs. So, by leveraging this feature, you would be able to create a procedure to release/reset the system variable based on a "timeout". 4 - Your description of a "database mutex" makes me think that you are trying to have the database perform network locking. This is not what a SQL database is for. There are a number of tools (we have written our own) which can integrate locking into your application. |
Submitted by: Doru Constantin (doru_constantin)
Duplicates CORE1863
Extend Generic user and system context variable(s) to create global variables in context of curent database. The server should release this variable when user who create it is disconnected, when the database is dettached form server, when time is out (additional parameter), or when is released by the user who create it. It is like a database mutex.
The text was updated successfully, but these errors were encountered: