List:Internals« Previous MessageNext Message »
From:arjen Date:November 2 2001 1:19am
Subject:bk commit into 4.0 tree
View as plain text  
Below is the list of changes that have just been committed into a
4.0 repository of arjen. When arjen does a push, they will be propogated 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@stripped, 2001-11-02 11:18:50+10:00, arjen@stripped
  Fixed typos/lingo, from notes by Stefan Hinz (German translator).

  Docs/manual.texi
    1.629 01/11/02 11:18:46 arjen@stripped +13 -10
    Fixed typos/lingo, from notes by Stefan Hinz (German translator).

# 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:	arjen
# Host:	co3064164-a.bitbike.com
# Root:	C:/home/mysql-4.0

--- 1.628/Docs/manual.texi	Fri Nov 02 09:53:02 2001
+++ 1.629/Docs/manual.texi	Fri Nov 02 11:18:46 2001
@@ -4265,9 +4265,9 @@
 mapped tables.
 
 @item
-You cannot build in another directory when using
+You cannot build the server in another directory when using
 MIT-pthreads. Because this requires changes to MIT-pthreads, we are not
-likely to fix this.
+likely to fix this. @xref{MIT-pthreads}.
 
 @item
 @code{BLOB} values can't ``reliably'' be used in @code{GROUP BY} or
@@ -4496,6 +4496,7 @@
 in this section that we know of.  If you find something which you believe
 to be an error, please contact us about it at @email{docs@@mysql.com}.
 
+@c FIX this is bad lingo: "supported limits", etc.
 For a list of all supported limits, functions, and types, see the
 @code{crash-me} Web page at 
 @uref{http://www.mysql.com/information/crash-me.php}.
@@ -4705,7 +4706,7 @@
 most-used C API functions.
 For example, it changes instances of @code{msqlConnect()} to
 @code{mysql_connect()}. Converting a client program from @code{mSQL} to
-MySQL usually takes a couple of minutes.
+MySQL usually requires only minor effort.
 @end table
 
 @menu
@@ -4722,7 +4723,7 @@
 @cindex converting, tools
 @cindex tools, converting
 
-According to our experience, it would just take a few hours to convert tools
+According to our experience, it doesn't take long to convert tools
 such as @code{msql-tcl} and @code{msqljava} that use the
 @code{mSQL} C API so that they work with the MySQL C API.
 
@@ -4824,8 +4825,10 @@
 @pxref{CREATE TABLE, , @code{CREATE TABLE}}):
 @itemize @bullet
 @item
+@c FIX bad lingo, needs rephrasing
 @code{ENUM} type for one of a set of strings.
 @item
+@c FIX bad lingo, needs rephrasing
 @code{SET} type for many of a set of strings.
 @item
 @code{BIGINT} type for 64-bit integers.
@@ -5381,11 +5384,11 @@
 Before going to the other benchmarks we know of, we would like to give
 some background on benchmarks:
 
-It's very easy to write a test that shows ANY database to be best
+It's very easy to write a test that shows ANY database to be the best
 database in the world, by just restricting the test to something the
-database is very good at and not test anything that the database is not
-good at.  If one after this publishes the result with a single figure,
-things are even easier.
+database is very good at and not testing anything that the database is
+not good at.  If one, after doing this, summarises the result with as
+a single figure, things are even easier.
 
 This would be like us measuring the speed of MySQL compared to PostgreSQL
 by looking at the summary time of the MySQL benchmarks on our web page.
@@ -5692,9 +5695,9 @@
 @item
 Add @code{PREPARE} of statements and sending of parameters to @code{mysqld}.
 @item
-Extend the server/client protocol to support warnings.
+Extend the client/server protocol to support warnings.
 @item
-Add options to the server/protocol protocol to get progress notes
+Add options to the client/server protocol to get progress notes
 for long running commands.
 @item
 Add database and real table name (in case of alias) to the MYSQL_FIELD
Thread
bk commit into 4.0 treearjen2 Nov
Re: Binlog has bad magic number errorMats Kindahl31 Aug
  • Re: Binlog has bad magic number errorRick James31 Aug