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.1209 04/02/02 14:14:03 paul@stripped +1 -0
Tweak unique_subquery/index_subquery wording.
Docs/manual.texi
1.1115 04/02/02 14:14:02 paul@stripped +6 -5
Tweak unique_subquery/index_subquery wording.
# 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: teton.kitebird.com
# Root: /home/paul/mysqldoc
--- 1.1114/Docs/manual.texi Mon Feb 2 14:04:03 2004
+++ 1.1115/Docs/manual.texi Mon Feb 2 14:14:02 2004
@@ -26531,16 +26531,17 @@
resolving subqueries.
@item unique_subquery
-It replace @code{ref} for some IN subqueries which looks like:
+This type replaces @code{ref} for some @code{IN} subqueries of the following
+form:
@example
value IN (SELECT primary_key FROM single_table WHERE some_exp)
@end example
-@code{unique_subquery} is just index lookup function which replace subquery
-completely for more efficiency.
+@code{unique_subquery} is just an index lookup function that replaces the
+subquery completely for more efficiency.
@item index_subquery
-Like @code{unique_subquery} replace IN subquery, but it works for non-unique
-indexes:
+Like @code{unique_subquery}, this type replaces @code{IN} subqueries, but
+it works for non-unique indexes:
@example
value IN (SELECT key_field FROM single_table WHERE some_exp)
@end example
| Thread |
|---|
| • bk commit - mysqldoc tree (paul:1.1209) | paul | 2 Feb |