hcq/MaxScale
hcq/MaxScale
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Updated readconnroute limitations

Browse Source 
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.
This commit is contained in:
Markus Makela 2015-12-30 14:50:03 +02:00
parent cec2c3670d
commit 94edc847c2
2 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
Documentation/About/Limitations.md
View File

@ -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

2
Documentation/Release-Notes/MaxScale-1.3.0-Release-Notes.md
View File

@ -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.