From 9974069620b0f0e6ac2f1e9bd64819ae0a0e623b Mon Sep 17 00:00:00 2001
From: Tim Graham <timograham@gmail.com>
Date: Sun, 1 Jul 2012 07:25:24 -0400
Subject: [PATCH] Fixed #16882 - Clarified why one should not use
 'init_command' after initial database creation.

---
 docs/ref/databases.txt | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/docs/ref/databases.txt b/docs/ref/databases.txt
index ff7a349eb5..1f4d09f6cb 100644
--- a/docs/ref/databases.txt
+++ b/docs/ref/databases.txt
@@ -335,7 +335,9 @@ storage engine, you have a couple of options.
       }
 
   This sets the default storage engine upon connecting to the database.
-  After your tables have been created, you should remove this option.
+  After your tables have been created, you should remove this option as it
+  adds a query that is only needed during table creation to each database
+  connection.
 
 * Another method for changing the storage engine is described in
   AlterModelOnSyncDB_.