From e40944c9b940dc752e6b7c6f9b5e53eda8f6d026 Mon Sep 17 00:00:00 2001 From: Markus Makela Date: Wed, 30 Dec 2015 11:31:27 +0200 Subject: [PATCH] Added note about persistent connections Since the persistent connections do not track session state, a note should be added somewhere which states this. --- Documentation/Release-Notes/MaxScale-1.3.0-Release-Notes.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/Documentation/Release-Notes/MaxScale-1.3.0-Release-Notes.md b/Documentation/Release-Notes/MaxScale-1.3.0-Release-Notes.md index 8f645d2c2..a14fb1abd 100644 --- a/Documentation/Release-Notes/MaxScale-1.3.0-Release-Notes.md +++ b/Documentation/Release-Notes/MaxScale-1.3.0-Release-Notes.md @@ -24,6 +24,12 @@ using the *Persistent Connection* feature as it may reduce the time it takes from establishing a connection from the client through MaxScale to the backend server. +**NOTE**: The persistent connections do not track session state. This means +that changing the default database or modifying the session state will cause +those changes to be active even for new connections. If you use queries with +implicit databases or use connections with different client settings, you +should take great care when using persistent connections. + Additional information is available in the following document: * [Administration Tutorial](../Tutorials/Administration-Tutorial.md)