From: kevin.lewis
Date: March 8 2011 3:09pm
Subject: bzr push into mysql-5.5-innodb branch (kevin.lewis:3343 to 3344)
List-Archive: http://lists.mysql.com/commits/132692
Message-Id: <20110308150913.2B4E9CA39AE@kevin-lewis-macbook.local>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit

 3344 kevin.lewis@stripped	2011-03-08
      Fix test failure on case-sensitive file systems.

    modified:
      mysql-test/suite/innodb/t/innodb_bug60196.test
 3343 kevin.lewis@stripped	2011-03-07
      Bug#60196 / Bug#11831040 
      Setting lowercase_table_names to 2 on Windows causing Foreign Key problems
      
      This problem was exposed by the fix for Bug#55222.  There was a codepath in dict0load.c,
      dict_load_foreigns() that made sure the table name matched case sensitive in order to
      load a referenced table into the dictionary as needed.  If an engine is rebooted which
      accesses a table with foreign keys, and lower_case_table_names=2, then the table with
      foreign keys will get an error when it is changed (insert/updated/delete).
      Once the referenced tables are loaded into the dictionary cache by a select statement
      on those tables, the same change would succeed because the affected code path would
      not get followed.

    added:
      mysql-test/suite/innodb/r/innodb_bug60196.result
      mysql-test/suite/innodb/t/innodb_bug60196-master.opt
      mysql-test/suite/innodb/t/innodb_bug60196.test
    modified:
      storage/innobase/dict/dict0load.c
=== modified file 'mysql-test/suite/innodb/t/innodb_bug60196.test'
--- a/mysql-test/suite/innodb/t/innodb_bug60196.test	revid:kevin.lewis@stripped
+++ b/mysql-test/suite/innodb/t/innodb_bug60196.test	revid:kevin.lewis@stripped
@@ -2,7 +2,9 @@
 # Foreign Key problems after an engine is restarted.
 
 # This test case needs InnoDB.
--- source include/have_innodb.inc
+--source include/have_innodb.inc
+--source include/have_lowercase2.inc
+--source include/have_case_insensitive_file_system.inc
 
 #
 # Precautionary clean up.

No bundle (reason: useless for push emails).