bk commit - mysqldoc tree (paul:1.2869)

[paul]

Below is the list of changes that have just been committed into a local
mysqldoc repository of paul. When paul does a push these changes will
be propagated to the main repository and, within 24 hours after the
push, to the public repository.
For information on how to access the public repository
see http://www.mysql.com/doc/I/n/Installing_source_tree.html

ChangeSet
  1.2869 05/04/15 09:32:41 paul@stripped +1 -0
  manual.texi:
    You can use INFORMATION_SCHEMA with USE.

  Docs/manual.texi
    1.2701 05/04/15 08:15:05 paul@stripped +5 -4
    You can use INFORMATION_SCHEMA with USE.

# This is a BitKeeper patch.  What follows are the unified diffs for the
# set of deltas contained in the patch.  The rest of the patch, the part
# that BitKeeper cares about, is below these diffs.
# User:	paul
# Host:	frost.snake.net
# Root:	/Volumes/frost2/MySQL/bk/mysqldoc

--- 1.2700/Docs/manual.texi	2005-04-14 18:18:21 -05:00
+++ 1.2701/Docs/manual.texi	2005-04-15 08:15:05 -05:00
@@ -81390,10 +81390,11 @@
 standard name is @code{INFORMATION_SCHEMA}.
 
 In effect, we have a new ``database'' named @code{information_schema},
-though there is never a need to make a file by that name.  It is not
-possible to issue  @code{USE INFORMATION_SCHEMA}.  The only thing you can do
-with these tables is @code{SELECT}.  You cannot update, insert, delete, or
-even reference them.
+though there is never a need to make a file by that name.  It is possible to
+select @code{INFORMATION_SCHEMA} as the default database with a @code{USE}
+statement, but the only way to access the contents of its tables is with
+@code{SELECT}.  You cannot insert into them, update them, or delete from
+them.
 
 @strong{Privileges}