Bug #11567 Variable 'foreign_key_checks', and other variables, differs binlog tests
Submitted: 25 Jun 2005 14:58 Modified: 20 Jul 2005 17:20
Reporter: Kent Boortz
Status: Closed
Category:Server: Replication Severity:S2 (Serious)
Version:5.0.8-pre OS:Microsoft Windows (Windows XP (Professional))
Assigned to: Bugs System Target Version:

[25 Jun 2005 14:58] Kent Boortz 
Description:
The tests 'user_var-binlog', 'ctype_ucs_binlog' and 'mysqlbinlog2'
fails. The diff contains lines like

-SET @@session.foreign_key_checks=1, @@session.sql_auto_is_null=1,
@@session.unique_checks=1;
+SET @@session.foreign_key_checks=67108864, @@session.sql_auto_is_null=16384,
@@session.unique_checks=134217728;

The new values are always the same.

How to repeat:
Run the test suite on Windows, using 5.0.8-pre
[13 Jul 2005 17:43] Elliot Murphy 
I have a fix for the original issue described, but now that this is fixed another problem
shows up in mysqlbinlog2.test, it seems that --start-datetime and --stop-datetime options
to mysqlbinlog are not working correctly on Windows. Since mysqlbinlog2 failing is
mentioned as part of the original bug report, I will take a look at this also rather than
splitting out a separate bug report.
[18 Jul 2005 21:20] Elliot Murphy 
After figuring out that timezone was not being set correctly, I wrote a new bug #12018 for
the timezone problem and will commit the fix for this bug after running tests.
[18 Jul 2005 22:04] Bugs System 
A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

  http://lists.mysql.com/internals/27256
[18 Jul 2005 23:47] Bugs System 
A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

  http://lists.mysql.com/internals/27267
[19 Jul 2005 7:48] Elliot Murphy 
Fix pushed to 5.0 tree, will be in 5.0.10.
[20 Jul 2005 17:20] Jon Stephens 
Thank you for your bug report. This issue has been committed to our
source repository of that product and will be incorporated into the
next release.

If necessary, you can access the source repository and build the latest
available version, including the bugfix, yourself. More information 
about accessing the source trees is available at
    http://www.mysql.com/doc/en/Installing_source_tree.html

Additional info:

Documented bugfix for 5.0.10.