From d0777581bb747a59affbb75e86b249598ed1a341 Mon Sep 17 00:00:00 2001 From: Deven Bansod Date: Fri, 22 May 2015 13:26:04 +0530 Subject: [PATCH] Edited the Documentation slightly Signed-off-by: Deven Bansod --- doc/faq.rst | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/doc/faq.rst b/doc/faq.rst index fb02377d48..298e2bf815 100644 --- a/doc/faq.rst +++ b/doc/faq.rst @@ -2049,18 +2049,18 @@ MySQL does not adjust the original privileges relating to these objects on its own. For Example: An User 'root'@'localhost' has a 'SELECT' privilege on a -column named 'id'. Now, if this column is now renamed to 'id_new', MySQL, +column named 'id'. Now, if this column is renamed to 'id_new'; MySQL, on its own, would **not** adjust the column privileges to the new column name. -** Note : ** +Notes : -* While adjusting privileges for a Database, the privileges of all table-related - privileges, all column-related privileges and all procedure-related privileges +* While adjusting privileges for a Database, the privileges of all *table-related + privileges*, all *column-related privileges* and all *procedure-related privileges* for the tables, columns and procedures inside that database are also adjusted to the Database's new name. * Similarly, while adjusting privileges for a Table, the privileges of all - column-related privileges for the columns inside the table are also adjusted + *column-related privileges* for the columns inside the table are also adjusted to the Table's new name. Thus, if you want to replicate the Database/ Table/ Column/ Procedure as it is