summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorpaul@teton.kitebird.com <>2002-07-24 17:26:05 -0500
committerpaul@teton.kitebird.com <>2002-07-24 17:26:05 -0500
commit69a1952565e2c25c7fed06dd427adc8f6f15be80 (patch)
tree933710862d2135e41b1689468f61150bbb39aa31
parentb126501bf3888b09fad83dbd2894709c45f009fc (diff)
downloadmariadb-git-69a1952565e2c25c7fed06dd427adc8f6f15be80.tar.gz
manual.texi Clarify (?) INSERT ...VALUES(DEFAULT)
-rw-r--r--Docs/manual.texi11
1 files changed, 7 insertions, 4 deletions
diff --git a/Docs/manual.texi b/Docs/manual.texi
index 566aa465909..be60e0de623 100644
--- a/Docs/manual.texi
+++ b/Docs/manual.texi
@@ -34492,10 +34492,13 @@ example, if you specify a column list that doesn't name all the columns in
the table, unnamed columns are set to their default values. Default value
assignment is described in @ref{CREATE TABLE, , @code{CREATE TABLE}}.
-You can also use the keyword @code{DEFAULT} to set a column to it's
-defaults value. (New in MySQL 4.0.3). This makes it easier to write
-insert statements as you don't have to use a field-name list just because
-you don't want to set a value for a few columns.
+You can also use the keyword @code{DEFAULT} to set a column to its
+default value. (New in MySQL 4.0.3.) This makes it easier to write
+@code{INSERT} statements that assign values to all but a few columns,
+because it allows you to avoid writing an incomplete @code{VALUES()} list
+(a list that does not include an value for each column in the table).
+Otherwise, you would have to write out the list of column names
+corresponding to each value in the @code{VALUES()} list.
MySQL always has a default value for all fields. This is something
that is imposed on MySQL to be able to work with both transactional