Issue Details (XML | Word | Printable)

Key: CORE-2048
Type: Improvement Improvement
Status: Open Open
Priority: Major Major
Assignee: Unassigned
Reporter: Doru Constantin
Votes: 0
Watchers: 2
Operations

If you were logged in you would be able to see more operations.
Firebird Core

User can create global context variables in context of database.

Created: 22/Aug/08 05:02 AM   Updated: 22/Aug/08 10:43 AM
Component/s: Engine
Affects Version/s: 2.0.5, 2.1.2, 2.5 Beta 1
Fix Version/s: None

Issue Links:
Duplicate
 


 Description  « Hide
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.

 All   Comments   Change History   Subversion Commits      Sort Order: Ascending order - Click to sort in descending order
Ain Valtin added a comment - 22/Aug/08 06:32 AM

Sean Leyne added a comment - 22/Aug/08 10:43 AM
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.