From b7eee3ed1cbdff174a58f0a042c25831f4dee1e6 Mon Sep 17 00:00:00 2001 From: Markus Makela Date: Thu, 11 Jun 2015 16:59:44 +0300 Subject: [PATCH] Fixed markdown table. --- Documentation/Routers/SchemaRouter.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Documentation/Routers/SchemaRouter.md b/Documentation/Routers/SchemaRouter.md index 34da8506c..4f3cc4966 100644 --- a/Documentation/Routers/SchemaRouter.md +++ b/Documentation/Routers/SchemaRouter.md @@ -45,7 +45,7 @@ This would in effect allow the user 'john' to only see the database 'shard' on t The schemarouter supports the following router options: |option |parameter |description| ---------------------------------------------- +|-------------------|-----------|-----------| |max_sescmd_hitory | |Set a limit on the number of session modifying commands a session can execute. This sets an effective cap on the memory consupmtion of the session.| |disable_sescmd_history||Disable the session command history. This will prevent growing memory consumption of a long-running session and allows pooled connections to MaxScale to be used. The drawback of this is the fact that if a server goes down, the session state will not be consistent anymore.| |refresh_databases|true, false|Enable database map refreshing mid-session. These are triggered by a failure to change the database i.e. `USE ...``queries.