bk commit - mysqldoc tree (paul:1.2738)

[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.2738 05/03/17 18:13:34 paul@stripped +1 -0
  manual.texi:
    Small additions to TIMESTAMP and views sections.
    Update description for ERROR_FOR_DIVISION_BY_ZERO.

  Docs/manual.texi
    1.2573 05/03/17 18:12:56 paul@stripped +27 -11
    Small additions to TIMESTAMP and views sections.

  Docs/manual.texi
    1.2572 05/03/17 12:04:24 paul@stripped +7 -6
    Update description for ERROR_FOR_DIVISION_BY_ZERO.

# 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.2571/Docs/manual.texi	2005-03-17 10:38:58 -06:00
+++ 1.2573/Docs/manual.texi	2005-03-17 18:12:56 -06:00
@@ -19791,12 +19791,13 @@
 
 @cindex ERROR_FOR_DIVISION_BY_ZERO SQL mode
 @item ERROR_FOR_DIVISION_BY_ZERO
-Produce an error in strict mode (otherwise a warning) when we
-encounter a division by zero (or @code{MOD(X,0)}) during an @code{INSERT}/
-@code{UPDATE}. If this mode is not given, MySQL instead returns
-@code{NULL} for divisions by zero.  If used with @code{IGNORE}, MySQL
-generates a warning for divisions by zero, but the result of the operation is
-@code{NULL}.
+Produce an error in strict mode (otherwise a warning) when we encounter a
+division by zero (or @code{MOD(X,0)}) during an @code{INSERT} or
+@code{UPDATE}, or in any expression (for example, in a select list or
+@code{WHERE} clause) that involves table data and a division by zero.  If
+this mode is not given, MySQL instead returns @code{NULL} for divisions by
+zero.  If used with @code{IGNORE}, MySQL generates a warning for divisions
+by zero, but the result of the operation is @code{NULL}.
 (New in MySQL 5.0.2)
 
 @cindex HIGH_NOT_PRECEDENCE SQL mode
@@ -46113,7 +46114,7 @@
 
 As of MySQL 5.0.2, MySQL does not accept timestamp values that include
 a zero in the day or month column or values that are not a valid date.
-(The exception is the special value '0000-00-00 00:00:00'.)
+(The exception is the special value @code{'0000-00-00 00:00:00'}.)
 
 Beginning with MySQL 4.1.2, you have more flexible control over when
 automatic @code{TIMESTAMP} initialization and updating occur and which
@@ -46124,7 +46125,8 @@
 @item
 You can assign the current timestamp as the default value and the
 auto-update value, as before. But it is possible to have just one
-automatic behavior or the other, or neither of them.
+automatic behavior or the other, or neither of them. (It is not possible to
+have one behavior for one column and the other for another column.)
 
 @item
 You can specify which @code{TIMESTAMP} column to automatically initialize
@@ -46197,9 +46199,9 @@
 clause, the column has a default of 0 and is automatically updated.
 
 @item
-With a constant @code{DEFAULT} value and with @code{ON UPDATE
-CURRENT_TIMESTAMP} clause, the column has the given default and is
-automatically updated.
+With a constant @code{DEFAULT} value, the column has the given default.  If
+the column has an @code{ON UPDATE CURRENT_TIMESTAMP} clause, it is
+automatically updated, otherwise not.
 
 @end itemize
 
@@ -57755,6 +57757,9 @@
 This statement changes the definition of an existing view.
 The syntax is similar to that for @code{CREATE VIEW}.
 @xref{CREATE VIEW,  , @code{CREATE VIEW}}.
+This statement requires the @code{CREATE VIEW} and @code{DELETE} privileges
+for the view, and some privilege for each column referred to in the
+@code{SELECT} statement.
 @c end_description_for_help_topic
 
 This statement was added in MySQL 5.0.1.
@@ -58830,10 +58835,9 @@
 @findex CREATE VIEW
 
 @c TODO-VIEWS: add ALGORITHM syntax; point out that you can update a
-@c base table through the view (and conditions for that), discuss what
-@c privileges apply and when, etc., etc., etc.
+@c base table through the view (and conditions for that).
 
-@c example_for_help_topic CREATE VIEW
+@c example_for_help_topic CREATE VIEW  ALGORITHM MERGE TEMPTABLE WITH CHECK OPTION
 @example
 CREATE [OR REPLACE] [ALGORITHM = @{UNDEFINED | MERGE | TEMPTABLE@}]
     VIEW @var{view_name} [(@var{column_list})]
@@ -58847,6 +58851,11 @@
 @code{SELECT} statement that provides the definition of the view.
 The statement can select from base tables or other views.
 
+This statement requires the @code{CREATE VIEW} privilege for the view, and
+some privilege for each column referred to in the @code{SELECT} statement.
+If the @code{OR REPLACE} clause is present, you must also have the
+@code{DELETE} privilege for the view.
+
 A view belongs to a database.  By default, a new view is created in the
 current database.  To create the view explicitly in a given database,
 specify the name as @var{db_name.view_name} when you create it.
@@ -58875,7 +58884,7 @@
 tables or views in other databases by qualifying the table or view name with
 the proper database name.
 
-A view definition is subject to the following constraints:
+A view definition is subject to the following restrictions:
 
 @itemize @bullet
 
@@ -58906,9 +58915,9 @@
 @end itemize
 
 @c TODO: need to describe ALGORITHM clause
-@c TODO: use of anything other than simple column references
-@c makes view not updatable. Updatable views must select only table columns.
 @c TODO: use of TEMPTABLE makes view non-updatable
+@c TODO: use of anything other than simple column references
+@c makes view not updatable. (Updatable views must select only table columns.)
 
 The @code{WITH CHECK OPTION} clause can be given for an updatable view to
 prevent inserts or updates to rows except those for which the @code{WHERE}
@@ -58966,8 +58975,16 @@
 ERROR 1369 (HY000): CHECK OPTION failed 'test.v3'
 @end example
 
+The updatability of views may be affected by the value of the
+@code{updatable_views_with_limit} system variable.
+@xref{Server system variables}.
+
 The @code{CREATE VIEW} statement was added in MySQL 5.0.1.  The @code{WITH
 CHECK OPTION} clause was implemented in MySQL 5.0.2.
+
+@code{INFORMATION_SCHEMA} contains a @code{VIEWS} table from which information
+about view objects can be obtained.
+@xref{VIEWS Table,  , @code{VIEWS} Table}.
 
 
 @node DROP DATABASE, DROP INDEX, CREATE VIEW, Data Definition