From 90e12034f35a1c6d245969a2866e23d66e898c26 Mon Sep 17 00:00:00 2001
From: Marc Delisle <marc@infomarc.info>
Date: Sun, 29 Jan 2006 13:30:08 +0000
Subject: [PATCH] new usage of MaxExactCount

---
 Documentation.html | 17 ++++++++++++-----
 1 file changed, 12 insertions(+), 5 deletions(-)

diff --git a/Documentation.html b/Documentation.html
index 14f306773..d85bcc4ff 100755
--- a/Documentation.html
+++ b/Documentation.html
@@ -1767,11 +1767,18 @@ GRANT SELECT, INSERT, UPDATE, DELETE ON &lt;pma_db&gt;.* TO 'pma'@'localhost';
 
     <dt><b><a name="cfg_MaxExactCount"></a>$cfg[MaxExactCount] </b>integer</dt>
     <dd>
-        Determines for how large tables phpMyAdmin should get exact row count by
-    <code>SELECT COUNT</code>. If approximate row count is smaller than this
-    value, <code>SELECT COUNT</code> will be used, otherwise only value
-    returned by <code>SHOW TABLE STATUS</code>. This has currently an impact
-    only on InnoDB tables.
+        <ul>
+            <li>For InnoDB tables, determines for how large tables phpMyAdmin 
+            should get the exact row count using <code>SELECT COUNT</code>. 
+            If the approximate row count as returned by 
+            <code>SHOW TABLE STATUS</code> is smaller than this value, 
+            <code>SELECT COUNT</code> will be used, otherwise the approximate
+            count will be used.
+            </li>
+            <li>For VIEWs, since obtaining the exact count could have an
+            impact on performance, this value is the maximum to be displayed.
+            </li>
+        </ul>
     </dd>
 
     <dt><a name="wysiwyg"></a>