Robert Hodges (JIRA)
2008-05-13 21:11:22 UTC
Implement call-outs at well-defined locations in the request follow to allow users to view, modify, and fulfill SQL requests within the connector
-------------------------------------------------------------------------------------------------------------------------------------------------
Key: MYO-58
URL: https://forge.continuent.org/jira/browse/MYO-58
Project: Myosotis
Type: Bug
Environment: All platforms and databases
Reporter: Robert Hodges
Assigned to: Gilles Rayrat
Priority: Critical
Fix For: 0.7
The connector needs to have a set of extension points that allow users to plug-in additional logic to look at, change, and respond directly to SQL requests before they are submitted for execution and after execution as well. Users should be able to implement classes that are called at the extension points, which should include the following:
* When the extension class is loaded
* When the extension class is unloaded
* At user login
* At user logout (including abnormal connection termination)
* When a request is read from the network
* Before a request is submitted to the database for execution
* After a result is returned from the database
* Before a result is returned to the user
Here are some use cases for extensions.
1.) Adding scripting logic in a manner similar to MySQL Proxy Lua scripts.
2.) Adding a parser that processes requests to set query metadata.
3.) Adding a query result cache that returns cached results rather than submitting the query to the database
4.) Adding a load balancer that selects alternate databases against which to run queries.
It should be possible to load more than one set of extensions, in which case extensions should execute in a deterministic order.
-------------------------------------------------------------------------------------------------------------------------------------------------
Key: MYO-58
URL: https://forge.continuent.org/jira/browse/MYO-58
Project: Myosotis
Type: Bug
Environment: All platforms and databases
Reporter: Robert Hodges
Assigned to: Gilles Rayrat
Priority: Critical
Fix For: 0.7
The connector needs to have a set of extension points that allow users to plug-in additional logic to look at, change, and respond directly to SQL requests before they are submitted for execution and after execution as well. Users should be able to implement classes that are called at the extension points, which should include the following:
* When the extension class is loaded
* When the extension class is unloaded
* At user login
* At user logout (including abnormal connection termination)
* When a request is read from the network
* Before a request is submitted to the database for execution
* After a result is returned from the database
* Before a result is returned to the user
Here are some use cases for extensions.
1.) Adding scripting logic in a manner similar to MySQL Proxy Lua scripts.
2.) Adding a parser that processes requests to set query metadata.
3.) Adding a query result cache that returns cached results rather than submitting the query to the database
4.) Adding a load balancer that selects alternate databases against which to run queries.
It should be possible to load more than one set of extensions, in which case extensions should execute in a deterministic order.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://forge.continuent.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://forge.continuent.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira