bk commit - mysqldoc tree (paul:1.2529)

[paul]

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.2529 05/02/11 21:58:07 paul@stripped +1 -0
  manual.texi:
    Note a change in 4.1 regarding ODBC syntax. (Bug #8443)

  Docs/manual.texi
    1.2337 05/02/11 21:57:30 paul@stripped +19 -0
    Note a change in 4.1 regarding ODBC syntax.

# 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.2336/Docs/manual.texi	2005-02-11 16:53:01 -06:00
+++ 1.2337/Docs/manual.texi	2005-02-11 21:57:30 -06:00
@@ -10925,6 +10925,25 @@
 for @command{mysqld}, either. Use @code{--transaction-isolation=SERIALIZABLE}
 instead.
 
+@item
+@strong{Incompatible change:}
+The statement parser accepts ODBC syntax of the following form:
+
+@example
+INSERT INTO t (datetime_col) VALUES (@{ts '2005-02-11 10:17:01'@});
+@end example
+
+Before MySQL 4.1.1, the parser was less strict and its string-to-date
+conversion would ignore everything up to the first digit. As a result,
+invalid statements such as the following were accepted:
+
+@example
+INSERT INTO t (datetime_col) VALUES ('@{ts \'2005-02-11 10:17:01\'@}');
+@end example
+
+As of MySQL 4.1.1, the parser now correctly treats the syntax as invalid and
+the preceding statement results in a warning.
+
 @end itemize
 
 @strong{C API Changes:}