From 8bea1a7e4eacfe311651eafb506ab1f4e7691feb Mon Sep 17 00:00:00 2001 From: Tim Graham Date: Sun, 1 Jul 2012 07:25:24 -0400 Subject: [PATCH] [1.4.X] Fixed #16882 - Clarified why one should not use 'init_command' after initial database creation. Backport of 9974069620 from master --- 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 5440f488e2..5580d65816 100644 --- a/docs/ref/databases.txt +++ b/docs/ref/databases.txt @@ -342,7 +342,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_.