|
If you were logged in you would be able to see more operations.
|
|
|
| Resolution Date: |
24/Jan/05 01:36 AM
|
|
With embedded pooled connections identity column values can be leaked from one user's connection to the other. With a PooledConnection the state of IDENTITY_VAL_LOCAL variable is not reset when the underlying EmbeddedConnection is re-used.
Thus an application can use this function to see a value that was returned to a previous user of the pooled connection.
A general reset() mechanism is needed on EmbeddedConnection/LanguageConnectionContext, this could replace and encapsulate the current single item that is reset, dropping of session temporary tables.
|
|
Description
|
With embedded pooled connections identity column values can be leaked from one user's connection to the other. With a PooledConnection the state of IDENTITY_VAL_LOCAL variable is not reset when the underlying EmbeddedConnection is re-used.
Thus an application can use this function to see a value that was returned to a previous user of the pooled connection.
A general reset() mechanism is needed on EmbeddedConnection/LanguageConnectionContext, this could replace and encapsulate the current single item that is reset, dropping of session temporary tables. |
Show » |
| No work has yet been logged on this issue.
|
|
Bug
Closed
Minor
IDENTITY_VAL_LOCAL not reset when new Connection returned from PooledConnection
