From 94edc847c2de95e14e7d5ceac63754669a32fb4e Mon Sep 17 00:00:00 2001 From: Markus Makela Date: Wed, 30 Dec 2015 14:50:03 +0200 Subject: [PATCH] Updated readconnroute limitations The limitation with readconnroute and LONGBLOB is only when data is being sent from the client to MaxScale. The client can still query for LONGBLOB data without any side-effects. --- Documentation/About/Limitations.md | 2 +- Documentation/Release-Notes/MaxScale-1.3.0-Release-Notes.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/Documentation/About/Limitations.md b/Documentation/About/Limitations.md index f3df71ff7..fb3a5bf29 100644 --- a/Documentation/About/Limitations.md +++ b/Documentation/About/Limitations.md @@ -18,7 +18,7 @@ The default master selection is based only on MIN(wsrep_local_index). This can b * If Master changes (ie. new Master promotion) during current connection the router cannot check the change -* LONGBLOB is not supported +* Sending of LONGBLOB data is not supported ## Limitations in the Read/Write Splitter 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 a14fb1abd..bbc115a68 100644 --- a/Documentation/Release-Notes/MaxScale-1.3.0-Release-Notes.md +++ b/Documentation/Release-Notes/MaxScale-1.3.0-Release-Notes.md @@ -237,7 +237,7 @@ the most serious of this are listed below. * When users have different passwords based on the host from which they connect MaxScale is unable to determine which password it should use to connect to the backend database. This results in failed connections and unusable usernames in MaxScale. -* LONGBLOB are currently not supported. +* The readconnroute module does not support sending of LONGBLOB data. * Galera Cluster variables, such as @@wsrep_node_name, are not resolved by the embedded MariaDB parser.