1. 24 Jan, 2008 5 commits
    • unknown's avatar
      Merge ramayana.hindu.god:/home/tsmith/m/bk/build/50 · 66361a80
      unknown authored
      into  ramayana.hindu.god:/home/tsmith/m/bk/build/51
      
      
      BitKeeper/triggers/triggers-lib.pl:
        Auto merged
      66361a80
    • unknown's avatar
      Fix bug in BK trigger for sending changes to InnoDB devs. · e09b41cf
      unknown authored
      
      BitKeeper/triggers/triggers-lib.pl:
        Fix bug in innodb_send_changes_mail() that always displayed
        details for the most recent changeset (-r+) instead of the
        $cset function argument.
      e09b41cf
    • unknown's avatar
      Merge ramayana.hindu.god:/home/tsmith/m/bk/build/50 · bd126eae
      unknown authored
      into  ramayana.hindu.god:/home/tsmith/m/bk/build/51
      
      
      storage/innobase/handler/ha_innodb.cc:
        use local (null merge)
      bd126eae
    • unknown's avatar
      Merge ramayana.hindu.god:/home/tsmith/m/inno/jan23/50 · b5e3c1f8
      unknown authored
      into  ramayana.hindu.god:/home/tsmith/m/bk/build/50
      
      
      b5e3c1f8
    • unknown's avatar
      Applied innodb-5.0-ss2223 snapshot · 8bfec4b2
      unknown authored
      Fixes:
      
      Bug #32083: server crashes on show status when InnoDB is not initialized
        innodb_export_status(): Check that InnoDB has been initialized
        before invoking srv_export_innodb_status().  (Bug #32083)
        This bug does not exist in MySQL/InnoDB 5.1.
      
      
      sql/ha_innodb.cc:
        Applied innodb-5.0-ss2223 snapshot
        
        Revision r2223:
        branches/5.0: innodb_export_status(): Check that InnoDB has been initialized
        before invoking srv_export_innodb_status().  (Bug #32083)
        
        This bug does not exist in MySQL/InnoDB 5.1.
      8bfec4b2
  2. 23 Jan, 2008 13 commits
  3. 22 Jan, 2008 2 commits
  4. 21 Jan, 2008 6 commits
    • unknown's avatar
      Merge trift2.:/MySQL/M50/push-5.0 · 77fc8ad5
      unknown authored
      into  trift2.:/MySQL/M51/push-5.1
      
      
      77fc8ad5
    • unknown's avatar
      Merge trift2.:/MySQL/M41/push-4.1 · 09be3816
      unknown authored
      into  trift2.:/MySQL/M50/push-5.0
      
      
      09be3816
    • unknown's avatar
      Merge trift2.:/MySQL/M51/mysql-5.1 · dd2317f9
      unknown authored
      into  trift2.:/MySQL/M51/push-5.1
      
      
      dd2317f9
    • unknown's avatar
      Merge trift2.:/MySQL/M50/mysql-5.0 · dfe7b382
      unknown authored
      into  trift2.:/MySQL/M50/push-5.0
      
      
      dfe7b382
    • unknown's avatar
      Merge trift2.:/MySQL/M41/mysql-4.1 · b7b1bd62
      unknown authored
      into  trift2.:/MySQL/M41/push-4.1
      
      
      b7b1bd62
    • unknown's avatar
      New tests added for Bug#33558 - Test "stress.ddl_csv needs nullable columns... · 63c73b52
      unknown authored
      New tests added for Bug#33558 - Test "stress.ddl_csv needs nullable columns which CSV does not support
      Added new tests and corrected existing tests
      
      
      mysql-test/suite/stress/include/ddl3.inc:
        New tests added for Bug#33558 - Test "stress.ddl_csv needs nullable columns which CSV does not support
        
        Had to change CREATE TABLE statements to include NOT NULL due to CSV engine constraints
      mysql-test/suite/stress/r/ddl_archive.result:
        New tests added for Bug#33558 - Test "stress.ddl_csv needs nullable columns which CSV does not support
        
        Reproduced .result files due to changes in ddl3.inc
      mysql-test/suite/stress/r/ddl_csv.result:
        New tests added for Bug#33558 - Test "stress.ddl_csv needs nullable columns which CSV does not support
        
        Reproduced .result files due to changes in ddl3.inc
      mysql-test/suite/stress/r/ddl_innodb.result:
        New tests added for Bug#33558 - Test "stress.ddl_csv needs nullable columns which CSV does not support
        
        Reproduced .result files due to changes in ddl3.inc
      mysql-test/suite/stress/r/ddl_memory.result:
        New tests added for Bug#33558 - Test "stress.ddl_csv needs nullable columns which CSV does not support
        
        Reproduced .result files due to changes in ddl3.inc
      mysql-test/suite/stress/r/ddl_myisam.result:
        New tests added for Bug#33558 - Test "stress.ddl_csv needs nullable columns which CSV does not support
        
        Reproduced .result files due to changes in ddl3.inc
      mysql-test/suite/stress/r/ddl_ndb.result:
        New tests added for Bug#33558 - Test "stress.ddl_csv needs nullable columns which CSV does not support
        
        Reproduced .result files due to changes in ddl3.inc
      BitKeeper/etc/ignore:
        Added mysql-test/.DS_Store .DS_Store to the ignore list
      mysql-test/t/disabled.def:
        Disabled new test - csv_alter_table.test file due to Bug#33696.
        
        Cannot generate a .result file due to the Bug.  These tests can be enabled to test the bug fix without needing new tests unless the developer feels the need to add more.
      mysql-test/r/csv_not_null.result:
        New tests added for Bug#33558 - Test "stress.ddl_csv needs nullable columns which CSV does not support
      mysql-test/t/csv_alter_table.test:
        New tests added for Bug#33558 - Test "stress.ddl_csv needs nullable columns which CSV does not support
        
        Designed to test fixes for Bug#33696 - CSV Engine allows nullable columns via ALTER TABLE statements
      mysql-test/t/csv_not_null.test:
        New tests added for Bug#33558 - Test "stress.ddl_csv needs nullable columns which CSV does not support
      63c73b52
  5. 19 Jan, 2008 1 commit
  6. 15 Jan, 2008 1 commit
    • unknown's avatar
      Apply innodb-5.1-ss2146 and innodb-5.1-ss2178 snapshots. · d39f2048
      unknown authored
      Fixes:
      
      Bug #18942: DROP DATABASE does not drop an orphan FOREIGN KEY constraint
        Fix Bug#18942 by dropping all foreign key constraints at the end of
        DROP DATABASE. Usually, by then, there are no foreign constraints
        left because all of them are dropped when the relevant tables are
        dropped. This code is to ensure that any orphaned FKs are wiped too.
      
      Bug #29157: UPDATE, changed rows incorrect
        Return HA_ERR_RECORD_IS_THE_SAME from ha_innobase::update_row() if no
        columns were updated.
      
      Bug #32440: InnoDB free space info does not appear in SHOW TABLE STATUS or I_S
        Put information about the free space in a tablespace in
        INFORMATION_SCHEMA.TABLES.DATA_FREE. This information was previously
        available in INFORMATION_SCHEMA.TABLES.TABLE_COMMENT, but MySQL has
        removed it from there recently.
        The stored value is in kilobytes.
        This can be considered as a permanent workaround to
        http://bugs.mysql.com/32440. "Workaround" becasue that bug is about the
        data missing from TABLE_COMMENT and this is actually not solved.
      
      
      mysql-test/r/innodb.result:
        New tests for bugs fixed as part of snapshots innodb-5.1-ss2146 and innodb-5.1-ss2178
      mysql-test/r/partition_innodb.result:
        Update results - InnoDB now sets Data_length (show table status)
      mysql-test/t/innodb.test:
        New tests for bugs fixed as part of snapshots innodb-5.1-ss2146 and innodb-5.1-ss2178
      mysql-test/t/partition_innodb.test:
        Mask out Data_Free in show table status, because it varies depending on
        which tests have been run.
      storage/innobase/handler/ha_innodb.cc:
        Apply innodb-5.1-ss2146 and innodb-5.1-ss2178 snapshots.
        
        
        Revision r2178:
        branches/5.1:
        
        Merge r2177 from trunk/:
        
        Fix Bug#29157 "UPDATE, changed rows incorrect":
        
        Return HA_ERR_RECORD_IS_THE_SAME from ha_innobase::update_row() if no
        columns were updated.
        
        
        Revision r2169:
        branches/5.1:
        
        Bug#32440:
        
        Put information about the free space in a tablespace in
        INFORMATION_SCHEMA.TABLES.DATA_FREE. This information was previously
        available in INFORMATION_SCHEMA.TABLES.TABLE_COMMENT, but MySQL has
        removed it from there recently.
        
        The stored value is in kilobytes.
        
        This can be considered as a permanent workaround to
        http://bugs.mysql.com/32440. "Workaround" becasue that bug is about the
        data missing from TABLE_COMMENT and this is actually not solved.
      storage/innobase/row/row0mysql.c:
        Apply innodb-5.1-ss2146 and innodb-5.1-ss2178 snapshots.
        
        
        Revision r2161:
        branches/5.1:
        
        Merge r2160 from trunk/:
        
        Fix Bug#18942 by dropping all foreign key constraints at the end of
        DROP DATABASE. Usually, by then, there are no foreign constraints
        left because all of them are dropped when the relevant tables are
        dropped. This code is to ensure that any orphaned FKs are wiped too.
      storage/innobase/trx/trx0trx.c:
        Apply innodb-5.1-ss2146 and innodb-5.1-ss2178 snapshots.
      d39f2048
  7. 11 Jan, 2008 3 commits
  8. 10 Jan, 2008 9 commits