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

Configuration-Guide.md

Browse Source
This commit is contained in:
Kolbe Kegel
2015-02-04 16:46:56 -08:00
parent 13842a5b5f
commit f48b961586
1 changed files with 6 additions and 13 deletions
Download Patch File Download Diff File Expand all files Collapse all files

19
Getting-Started/Configuration-Guide.md
View File

@ -692,11 +692,8 @@ The ability to route some statements to *Slave*s is important because it also de
Queries which can be routed to slaves must be auto committed and belong to one of the following group:
* read-only database queries,
* read-only queries to system, or user-defined variables,
* SHOW statements, and
* `SHOW` statements, and
* system function calls.
#### Routing to every session backend
@ -705,15 +702,11 @@ Third class of statements includes those, which modify session data, such as ses
Session commands include for example:
* SET statements
* USE <dbname>
* embedded system/user-defined variable assignments (SELECT (@myvar := 5)) in read-only statements
* PREPARE statements
* QUIT, PING, STMT RESET, CHANGE USER, etc. commands
* `SET` statements
* `USE *<dbname>*`
* embedded system/user-defined variable assignments (`SELECT (@myvar := 5)`) in read-only statements
* `PREPARE` statements
* `QUIT`, `PING`, `STMT RESET`, `CHANGE USER`, etc. commands
Note: if variable assignment is embedded in write statement it is routed to master only. For example, INSERT INTO t1 values(@myvar:=5, 7) would be routed to master only.