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

MXS-2498: Document temp tables in multi-statments

Browse Source 
When a temporary table is created with a multi-statement query, it won't
be detected by MaxScale.

Also removed the wrong limitations section from the document.
This commit is contained in:
Markus Mäkelä 2019-12-18 14:47:25 +02:00 committed by Johan Wikman
parent 4ae22f9991
commit b80d6c7305
1 changed files with 10 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

20
Documentation/Routers/ReadWriteSplit.md
View File

@ -685,16 +685,6 @@ the session state and the actual data in the database by adding routing hints
to DDL/DML statements which are then directed to slave servers. Only use routing
hints when you are sure that they can cause no harm.
## Limitations
For a list of readwritesplit limitations, please read the
[Limitations](../About/Limitations.md) document.
## Legacy Configuration
In older versions of MaxScale, routers were configured via the _router_options_
parameter. This functionality was deprecated in 2.2 and was removed in 2.3.
## Examples
Examples of the readwritesplit router in use can be found in the
@ -778,6 +768,11 @@ Read queries are routed to the master server in the following situations:
* if there are multiple statements inside one query e.g.
`INSERT INTO ... ; SELECT LAST_INSERT_ID();`
### Legacy Configuration
In older versions of MaxScale, routers were configured via the _router_options_
parameter. This functionality was deprecated in 2.2 and was removed in 2.3.
### JDBC Batched Statements
Readwritesplit does not support pipelining of JDBC batched statements. This is
@ -791,6 +786,11 @@ will always be routed to the master. See
[`strict_multi_stmt`](../Routers/ReadWriteSplit.md#strict_multi_stmt) for more
details.
If the multi-statement query creates a temporary table, it will not be
detected and reads to this table can be routed to slave servers. To
prevent this, always execute the temporary table creation as an individual
statement.
#### Limitations in client session handling
Some of the queries that a client sends are routed to all backends instead of