| List: | Commits | « Previous MessageNext Message » | |
| From: | mcbrown | Date: | October 24 2006 5:33pm |
| Subject: | svn commit - mysqldoc@docsrva: r3721 - trunk/internals | ||
| View as plain text | |||
Author: mcbrown Date: 2006-10-24 17:33:29 +0200 (Tue, 24 Oct 2006) New Revision: 3721 Log: Fixed numerous spelling/typos Modified: trunk/internals/algorithms.xml trunk/internals/client-server-protocol.xml trunk/internals/coding-guidelines.xml trunk/internals/custom-engine.xml trunk/internals/innodb-sources.xml trunk/internals/innodb.xml trunk/internals/myisam.xml trunk/internals/mysql-sources.xml trunk/internals/optimizer.xml trunk/internals/replication.xml Modified: trunk/internals/algorithms.xml =================================================================== --- trunk/internals/algorithms.xml 2006-10-24 15:02:32 UTC (rev 3720) +++ trunk/internals/algorithms.xml 2006-10-24 15:33:29 UTC (rev 3721) Changed blocks: 10, Lines Added: 11, Lines Deleted: 11; 4850 bytes @@ -720,7 +720,7 @@ This means "weight equals term frequency times inverse of document frequency", or "increase weight for number of times term appears in one document, decrease weight for number of documents the term - appears in". (For historical rasons we're using the word "weight" + appears in". (For historical reasons we're using the word "weight" instead of "distance", and we're using the information-retrieval word "document" throughout; when you see it, think of "the indexed part of the row".) @@ -1080,7 +1080,7 @@ B</literal>. The problem is that <literal>+A B</literal> can <emphasis role="bold">not</emphasis> be rewritten in and/or terms (that's the reason why this—extended—set of operators - was chosen). Still, aproximations can be used. <literal>+A B + was chosen). Still, approximations can be used. <literal>+A B C</literal> can be approximated as <literal>A or (A and (B or C))</literal> or as <literal>A or (A and B) or (A and C) or (A and B and C)</literal>. Applying the above logic (and omitting @@ -1168,7 +1168,7 @@ values and small fields. During my explorations of the code I didn't find places where <literal>float</literal> or <literal>double</literal> were to be converted into small fields. - Remeber that I talk only of conversions where field length and + Remember that I talk only of conversions where field length and precision are not given. In this case a sufficient field length is selected at several places, except for a bug where it was selected wrongly. If a field length is given, a different conversion is @@ -1326,7 +1326,7 @@ <para> Nevertheless, the function is still not perfect. It is not - possible to guess how many sigificant digits a number has. Given + possible to guess how many significant digits a number has. Given that, it is not simple to tell how long the resulting string would be. This applies to numbers with an absolute value smaller then 1. There are probably ways to figure this out, but I doubt that we @@ -1454,8 +1454,8 @@ </para> <para> - But all of this is probably completely unneccessary, since we are - only speaking of ceses where no user-supplied field length is + But all of this is probably completely unnecessary, since we are + only speaking of cases where no user-supplied field length is given. So MySQL selects the field length on its own. So it is totally possible, indeed highly desirable, that MySQL selects a field length, which allows for a maximum of precision for all @@ -1560,7 +1560,7 @@ <listitem> <para> The "maintenance" thread. See sql_manager_cc. Like the old - "sync" daemon in unix, this thread occasionally flushes myisam + "sync" daemon in unix, this thread occasionally flushes MyISAM tables to disk. InnoDB has a separate maintenance thread, but BDB also uses this one to occasionally call berkeley_cleanup_log_files(). Begins at startup and persists @@ -1713,7 +1713,7 @@ } MYSQL_FIELD;</programlisting> <para> - Character set and collation informaiton are specific to a server + Character set and collation information are specific to a server version and installation, and are generated automatically from the <filename>sql/share/charsets/Index.xml</filename> file in the source distribution. @@ -2690,7 +2690,7 @@ <row> <entry><literal>get_charset_name()</literal></entry> <entry>Collation ID</entry> - <entry>Charactet set name</entry> + <entry>Character set name</entry> </row> <row> <entry><literal>get_internal_charset()</literal></entry> @@ -2790,7 +2790,7 @@ <para> Set this if we should abort the current statement (and any multi-line statements) because something went fatally wrong. - (for example, astored procedure should be able to catch this). + (for example, a stored procedure should be able to catch this). This is reset by <literal>mysql_reset_thd_for_next_command()</literal>. </para> @@ -3206,7 +3206,7 @@ <tbody> <row> <entry>1</entry> - <entry>Force replace filnames library with 'dsk'</entry> + <entry>Force replace filenames library with 'dsk'</entry> </row> <row> <entry>2</entry> Modified: trunk/internals/client-server-protocol.xml =================================================================== --- trunk/internals/client-server-protocol.xml 2006-10-24 15:02:32 UTC (rev 3720) +++ trunk/internals/client-server-protocol.xml 2006-10-24 15:33:29 UTC (rev 3721) Changed blocks: 4, Lines Added: 4, Lines Deleted: 4; 1878 bytes @@ -310,7 +310,7 @@ <para> Alternative terms: Handshake Initialization Packet is also called - "greeting package". protocolversion is also called "Prot. + "greeting package". Protocol version is also called "Prot. version". server_version is also called "Server Version String". thread_number is also called "Thread Number". current server charset number is also called "charset_no". scramble_buff is also @@ -445,7 +445,7 @@ The client sends the encrypted scramble_buff value to the server. The server encrypts the original random string using a value in the mysql database, mysql.user.Password. - The server compares its encryted random string to what the client sent + The server compares its encrypted random string to what the client sent in scramble_buff. If they are the same, the password is okay. </programlisting> @@ -686,7 +686,7 @@ sqlstate: The server translates errno values to sqlstate values with a function named mysql_errno_to_sqlstate(). The possible values are listed in the manual, and in the - MySQL source code file file /include/sql_state.h. + MySQL source code file /include/sql_state.h. message: The error message is a string which ends at the end of the packet, that is, its length can be determined from @@ -1314,7 +1314,7 @@ code: always COM_EXECUTE -statement_id: statemeent identifier +statement_id: statement identifier flags: reserved for future use. in MySQL 4.0, always 0. Modified: trunk/internals/coding-guidelines.xml =================================================================== --- trunk/internals/coding-guidelines.xml 2006-10-24 15:02:32 UTC (rev 3720) +++ trunk/internals/coding-guidelines.xml 2006-10-24 15:33:29 UTC (rev 3721) Changed blocks: 4, Lines Added: 4, Lines Deleted: 4; 1875 bytes @@ -23,7 +23,7 @@ <quote>mutex_count=</quote> with an editor and miss assignments that look like <quote>mutex_count =</quote> with a space before the equal sign (which is non-conforming). Knowing our rules, you'll find it - easier to read our code, and when you you decide to contribute + easier to read our code, and when you decide to contribute (which we hope you'll consider!) we'll find it easier to read your code. </para> @@ -764,7 +764,7 @@ <listitem> <para> The function is handling the normal case, not some extra - functionallity that most users will not use. + functionality that most users will not use. </para> </listitem> @@ -1520,7 +1520,7 @@ Declares all plugins, in a comma-separated list, that are required for the named plugin to be built. If the named plugin is selected, it will in turn enable all its - depenencies. All plugins listed as a dependency must already + dependencies. All plugins listed as a dependency must already have been declared with <literal>MYSQL_PLUGIN()</literal>. </para> @@ -1545,7 +1545,7 @@ <para> Actually performs the task of generating the shell scripts for <command>configure</command> based upon the declarations - made previously. It emits the shell code neccessary to check + made previously. It emits the shell code necessary to check the options and sets the variables accordingly. </para> Modified: trunk/internals/custom-engine.xml =================================================================== --- trunk/internals/custom-engine.xml 2006-10-24 15:02:32 UTC (rev 3720) +++ trunk/internals/custom-engine.xml 2006-10-24 15:33:29 UTC (rev 3721) Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 474 bytes @@ -175,7 +175,7 @@ </para> <remark> - TODO: Update this... after antony gets hot-plugable stuff pushed + TODO: Update this... after antony gets hot-pluggable stuff pushed </remark> <programlisting> Modified: trunk/internals/innodb-sources.xml =================================================================== --- trunk/internals/innodb-sources.xml 2006-10-24 15:02:32 UTC (rev 3720) +++ trunk/internals/innodb-sources.xml 2006-10-24 15:33:29 UTC (rev 3721) Changed blocks: 3, Lines Added: 3, Lines Deleted: 3; 1718 bytes @@ -738,7 +738,7 @@ in the program (you might miss it at first glance) titled "IMPLEMENTATION OF THE SERVER MAIN PROGRAM" in which you'll find explanations about thread priority, and about what the - responsibiities are for various thread types. + responsibilities are for various thread types. </para> <para> @@ -933,7 +933,7 @@ readers". So a typical InnoDB row-read involves: (a) if the reading is for writing, then check if the row is locked and if so wait; (b) if according to the information in the row header the row has been - changed by some newer ransaction, then get the older version from + changed by some newer transaction, then get the older version from the log. We call the (b) part "versioning" because it means that a reader can get the older version of a row and thus will have a temporally consistent view of all rows. @@ -1010,7 +1010,7 @@ separator, then there is an individual name. For the main program in a subdirectory, the individual name may be a repeat of the subdirectory name. For example, there is a file named ha0ha.c (the - first two letters ha mean "it's in in subdirectory ..\ha", the next + first two letters ha mean "it's in subdirectory ..\ha", the next letter 0 means "0 separator", the next two letters mean "this is the main ha program"). This naming convention is not strict, though: for example the file lexyy.c is in the \pars subdirectory. Modified: trunk/internals/innodb.xml =================================================================== --- trunk/internals/innodb.xml 2006-10-24 15:02:32 UTC (rev 3720) +++ trunk/internals/innodb.xml 2006-10-24 15:33:29 UTC (rev 3721) Changed blocks: 2, Lines Added: 2, Lines Deleted: 2; 1192 bytes @@ -684,7 +684,7 @@ pair, "Page Header" and "Page Directory", are mostly the concern of the \page program group, while the outer pair, "Fil Header" and "Fil Trailer", are mostly the concern of the \fil program - group. The "Fil" header also goes goes by the name of "File Page + group. The "Fil" header also goes by the name of "File Page Header". </para> @@ -1016,7 +1016,7 @@ "Infimum" and "supremum" are real English words but they are found only in arcane mathematical treatises, and in <literal>InnoDB</literal> comments. To - <literal>InnoDB</literal>, an infimum is lower than the the + <literal>InnoDB</literal>, an infimum is lower than the lowest possible real value (negative infinity) and a supremum is greater than the greatest possible real value (positive infinity). <literal>InnoDB</literal> sets up an infimum record Modified: trunk/internals/myisam.xml =================================================================== --- trunk/internals/myisam.xml 2006-10-24 15:02:32 UTC (rev 3720) +++ trunk/internals/myisam.xml 2006-10-24 15:33:29 UTC (rev 3721) Changed blocks: 5, Lines Added: 5, Lines Deleted: 5; 2548 bytes @@ -690,7 +690,7 @@ <listitem> <para> Example: a MySQL 5.0 <literal>DECIMAL(21,9)</literal> - column conaining + column containing <literal>111222333444.555666777</literal> looks like: <literal>hexadecimal 80 6f 0d 40 8a 04 21 1e cd 59</literal> -- (flag + '111', '222333444', @@ -944,7 +944,7 @@ <literal>MEDIUMBLOB</literal>'s preceding length is three bytes long (the size of a <literal>MEDIUMINT</literal>), it's easy to think there's some sort of correspondence - between the the <literal>BLOB</literal> and + between the <literal>BLOB</literal> and <literal>INT</literal> types. There isn't — a <literal>BLOB</literal>'s preceding length is not four bytes long (the size of an <literal>INT</literal>). @@ -1668,7 +1668,7 @@ (<literal>MI_MAX_KEY</literal>). The maximum number of segments in a key is 16 (<literal>MI_MAX_KEY_SEG</literal>). The maximum key length is 500 - (<literal>MI_MAX_KEY_LENGTH</literal>). The maimum block + (<literal>MI_MAX_KEY_LENGTH</literal>). The maximum block length is 16384 (<literal>MI_MAX_KEY_BLOCK_LENGTH</literal>). All these MI_... constants are expressed by #defines in the <filename>myisamdef.h</filename> file. @@ -1871,7 +1871,7 @@ <para> The code trees are binary trees. Every node has exactly two - childs. The childs can be leafs or nodes. Each leaf contains one + children. The children can be leaves or nodes. Each leaf contains one original, uncompressed value. The nodes do not contain values, but only pointers to the left and right child. The Huffman codes represent the navigation through the tree. Every left branch @@ -1890,7 +1890,7 @@ </para> <para> - The representaion of the trees in the compressed data file is + The representation of the trees in the compressed data file is almost the same. But instead of writing all bits of the unsigned integers, only as many bits are written as are required to represent the highest value or offset respectively. One more bit Modified: trunk/internals/mysql-sources.xml =================================================================== --- trunk/internals/mysql-sources.xml 2006-10-24 15:02:32 UTC (rev 3720) +++ trunk/internals/mysql-sources.xml 2006-10-24 15:33:29 UTC (rev 3721) Changed blocks: 3, Lines Added: 3, Lines Deleted: 3; 941 bytes @@ -1447,7 +1447,7 @@ <listitem> <para> - mi_packrec.c --- read from a data file compresed with + mi_packrec.c --- read from a data file compressed with myisampack </para> </listitem> @@ -1809,7 +1809,7 @@ <listitem> <para> - \ndb --- for MySQL Cluster tsts + \ndb --- for MySQL Cluster tests </para> </listitem> @@ -1896,7 +1896,7 @@ <listitem> <para> - charset-def.c --- Inclcude character sets in the client + charset-def.c --- Include character sets in the client using </para> </listitem> Modified: trunk/internals/optimizer.xml =================================================================== --- trunk/internals/optimizer.xml 2006-10-24 15:02:32 UTC (rev 3720) +++ trunk/internals/optimizer.xml 2006-10-24 15:33:29 UTC (rev 3721) Changed blocks: 5, Lines Added: 5, Lines Deleted: 5; 2296 bytes @@ -99,7 +99,7 @@ best_access_path() /* Find a (sub-)optimal plan among all or subset */ /* of all possible query plans where the user */ - /* controlls the exhaustiveness of the search. */ + /* controls the exhaustiveness of the search. */ greedy_search() best_extension_by_limited_search() best_access_path() @@ -1134,7 +1134,7 @@ <para> is for a <literal>SEL_ARG</literal> object with an interval on the same field as this - <literal>SEL_ARG</literal> object. Intervals bewtween + <literal>SEL_ARG</literal> object. Intervals between the current and <quote>left</quote> objects are disjoint and <literal>left_sel_arg_cond.sup_val <= inf_val</literal>. @@ -1145,7 +1145,7 @@ <para> is for a <literal>SEL_ARG</literal> object with an interval on the same field as this - <literal>SEL_ARG</literal> object. Intervals bewteen the + <literal>SEL_ARG</literal> object. Intervals between the current and <quote>right</quote> objects are disjoint and <literal>left_sel_arg_cond.min_val >= max_val</literal>. @@ -1824,7 +1824,7 @@ <listitem> <para> - After the join order has been choosen, + After the join order has been chosen, <literal>add_not_null_conds()</literal> adds appropriate <literal>IS NOT NULL</literal> predicates to the conditions of the appropriate tables. @@ -2196,7 +2196,7 @@ <para> For <literal>RANGE</literal> partitioning, each partition occupies one interval on the partition function value - axis, and the intervals are disjoint, as ahown here: + axis, and the intervals are disjoint, as shown here: </para> <programlisting> Modified: trunk/internals/replication.xml =================================================================== --- trunk/internals/replication.xml 2006-10-24 15:02:32 UTC (rev 3720) +++ trunk/internals/replication.xml 2006-10-24 15:33:29 UTC (rev 3721) Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 836 bytes @@ -1037,7 +1037,7 @@ 4 bytes. The server ID of the <literal>mysqld</literal> which created this event. When using circular replication (with option <literal>--log-slave-updates</literal> on), we - use this server ID to avoid endless loops. Suppose tthat M1, + use this server ID to avoid endless loops. Suppose that M1, M2, and M3 have server ID values of 1, 2, and 3, and that they are replicating in circular fashion: M1 is the master for M2, M2 is the master for M3, and M3 is that master for
| Thread | ||
|---|---|---|
| • svn commit - mysqldoc@docsrva: r3721 - trunk/internals | mcbrown | 24 Oct |
© 1995-2008 MySQL AB, 2008-2009 Sun Microsystems, Inc.
Page generated in 0.470 sec. using MySQL 5.1.14-beta-log