The current persistent connection implementation is too restrictive
-------------------------------------------------------------------
Key: SEQUOIA-878
URL: https://forge.continuent.org/jira/browse/SEQUOIA-878
Project: Sequoia
Type: Improvement
Components: Core
Versions: Sequoia 3.0 beta1, Sequoia 2.10.3, Sequoia 2.10.2, Sequoia
2.10.1, Sequoia 2.10, Sequoia 2.9
Reporter: Ralph Hannus
Assigned to: Ralph Hannus
In order to correctly handle state that is associated with a backend database
connection, such as temporary tables and the last insert value for identity
columns, persistent connections maintain a relationship between the client
connection and connections to each of the enabled database backends for the
entire time the client has the connection open. Because this state can affect
the processing of update requests, all persistent connections must be closed
closed before a database backend can be enabled or disabled. This restriction
on backend enable/disable causes problems at customer sites where a client may
keep a connection open for a long period of time.
It would be better to enforce the restriction on backend enable/disable to the
period of time where the client is depending on the backend state, such as
using a temporary table.
--
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
_______________________________________________
Sequoia mailing list
[email protected]
https://forge.continuent.org/mailman/listinfo/sequoia
