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.2755 05/06/10 21:21:41 paul@stripped +1 -0
manual.texi:
Added information about temporal value comparisons.
(Bug #9321)
Document bugfix. (Bug #9669)
Document bugfix. (Bug #10015)
Document bugfix. (Bug #10417)
Docs/manual.texi
1.2979 05/06/10 21:20:35 paul@stripped +29 -0
Added information about temporal value comparisons.
(Bug #9321)
Docs/manual.texi
1.2978 05/06/10 21:10:29 paul@stripped +4 -0
Document bugfix. (Bug #9669)
Docs/manual.texi
1.2977 05/06/10 21:04:45 paul@stripped +5 -0
Document bugfix. (Bug #10015)
Docs/manual.texi
1.2976 05/06/10 20:58:57 paul@stripped +7 -0
Document bugfix. (Bug #10417)
# 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.2975/Docs/manual.texi 2005-06-10 20:52:32 -05:00
+++ 1.2979/Docs/manual.texi 2005-06-10 21:20:35 -05:00
@@ -97919,6 +97919,35 @@
string containing no separators (such as @code{'20040815'}), provided it
makes sense as a date.
+When you compare a @code{DATE}, @code{TIME}, @code{DATETIME}, or
+@code{TIMESTAMP} to a constant string with the @code{<}, @code{<=},
+@code{=}, @code{>=}, @code{>}, or @code{BETWEEN} operators, MySQL normally
+converts the string to an internal long integer for faster comparision (and
+also for a bit more ``relaxed'' string checking).
+However, this conversion is subject to the following exceptions:
+
+@itemize @bullet
+
+@item
+When you compare two columns
+
+@item
+When you compare a @code{DATE}, @code{TIME}, @code{DATETIME}, or
+@code{TIMESTAMP} column to an expression
+
+@item
+When you use any other comparison method than those just listed, such as
+@code{IN} or @code{STRCMP()}.
+
+@end itemize
+
+For these exceptional cases, the comparison is done by converting the
+objects to strings and performing a string comparison.
+
+To keep things safe, assume that strings are compared as strings and use the
+appropriate string functions if you want to compare a temporal value to a
+string.
+
The special date @code{'0000-00-00'} can be stored and retrieved as
@code{'0000-00-00'.} When using a @code{'0000-00-00'} date through
MyODBC, it is automatically converted to @code{NULL} in
@@ -100448,6 +100477,15 @@
Bugs fixed:
@itemize @bullet
@item
+Using @code{ORDER BY} to sort the results of an @code{IF()} that contained a
+@code{FROM_UNIXTIME()} expression returned incorrect results due to integer
+overflow. (Bug #9669)
+@item
+Fixed a server crash resulting from accessing @code{InnoDB} tables within
+stored runctions. This is handled by prohibiting statements that do an
+explicit or explicit commit or rollback within stored functions or triggers.
+(Bug #10015)
+@item
Fixed a server crash resulting from the second invocation of a stored
procedure that selected from a view defined as a join that used @code{ON} in
the join conditions. (Bug #6866)
@@ -100643,6 +100681,13 @@
Bugs fixed:
@itemize @bullet
+@item
+Statements that create and drop triggers were not being written to the
+binary log, which affects replication and data recovery options.
+(Bug #10417)
+@c TODO: uncomment the following after adding the xref-ed section
+@c Trigger-related statements now are logged, subject to the
+@c issues and limitations discussed in [ADD XREF].
@item
The @code{mysql_stmt_execute()} and @code{mysql_stmt_reset()} C API
functions now close any cursor that is open for the statement, which
