An error occurred fetching the project authors.
  1. 21 Oct, 2008 1 commit
    • vasil's avatar
      branches/zip: · 3df06e71
      vasil authored
      Merge 2744:2837 from branches/5.1 (skipping r2782 and r2826):
      
        ------------------------------------------------------------------------
        r2832 | vasil | 2008-10-21 10:08:30 +0300 (Tue, 21 Oct 2008) | 10 lines
        Changed paths:
           M /branches/5.1/handler/ha_innodb.cc
        
        branches/5.1:
        
        In ha_innobase::info():
        
        Replace sql_print_warning() which prints to mysqld error log with
        push_warning_printf() which sends the error message to the client.
        
        Suggested by:	Marko, Sunny, Michael
        Objected by:	Inaam
        
        ------------------------------------------------------------------------
        r2837 | vasil | 2008-10-21 12:07:44 +0300 (Tue, 21 Oct 2008) | 32 lines
        Changed paths:
           M /branches/5.1/mysql-test/innodb-semi-consistent.result
           M /branches/5.1/mysql-test/innodb-semi-consistent.test
           M /branches/5.1/mysql-test/innodb.result
           M /branches/5.1/mysql-test/innodb.test
        
        branches/5.1:
        
        Merge a change from MySQL (this fixes the failing innodb and
        innodb-semi-consistent tests):
        
          revno: 2757
          committer: Georgi Kodinov <kgeorge@mysql.com>
          branch nick: B39812-5.1-5.1.29-rc
          timestamp: Fri 2008-10-03 15:24:19 +0300
          message:
            Bug #39812: Make statement replication default for 5.1 (to match 5.0)
            
            Make STMT replication default for 5.1.
            Add a default of MIXED into the config files
            Fix the tests that needed MIXED replication mode.
          modified:
            mysql-test/include/mix1.inc
            mysql-test/r/innodb-semi-consistent.result
            mysql-test/r/innodb.result
            mysql-test/r/innodb_mysql.result
            mysql-test/r/tx_isolation_func.result
            mysql-test/t/innodb-semi-consistent.test
            mysql-test/t/innodb.test
            mysql-test/t/tx_isolation_func.test
            sql/mysqld.cc
            support-files/my-huge.cnf.sh
            support-files/my-innodb-heavy-4G.cnf.sh
            support-files/my-large.cnf.sh
            support-files/my-medium.cnf.sh
            support-files/my-small.cnf.sh
        
        
        ------------------------------------------------------------------------
      3df06e71
  2. 18 Sep, 2008 1 commit
    • marko's avatar
      branches/zip: When creating an index in innodb_strict_mode, check that · 3b2f5c05
      marko authored
      the maximum record size will never exceed the B-tree page size limit.
      For uncompressed tables, there should always be enough space for two
      records in an empty B-tree page.  For compressed tables, there should
      be enough space for storing two node pointer records or one data
      record in an empty page in uncompressed format.
      
      dict_build_table_def_step(): Remove the inaccurate check for table row
      size.
      
      dict_index_too_big_for_tree(): New function: check if the index
      records would be too big for a B-tree page.
      
      dict_index_add_to_cache(): Add the parameter "strict".  Invoke
      dict_index_too_big_for_tree() if it is set.
      
      trx_is_strict(), thd_is_strict(): New functions, for determining if
      innodb_strict_mode is enabled for the current transaction.
      
      dict_create_index_step(): Pass the new parameter strict of
      dict_index_add_to_cache() as trx_is_strict(trx).  All other callers
      pass it as FALSE.
      
      innodb.test: Enable innodb_strict_mode before attempting to create a
      table with a too big record size.
      
      innodb-zip.test: Remove the test of inserting random data.  Add tests
      for checking that the maximum record lengths are enforced at table
      creation time.
      3b2f5c05
  3. 30 Apr, 2008 1 commit
    • vasil's avatar
      branches/zip: Merge 2384:2423 from branches/5.1: · 22cd31a6
      vasil authored
        ------------------------------------------------------------------------
        r2386 | vasil | 2008-03-27 07:45:02 +0200 (Thu, 27 Mar 2008) | 22 lines
        
        branches/5.1:
        
        Merge change from MySQL (this fixes the failing innodb test):
        
        ChangeSet@1.1810.3601.4, 2008-02-07 02:33:21+04:00, gshchepa@host.loc +9 -0
          Fixed bug#30059.
          Server handles truncation for assignment of too-long values
          into CHAR/VARCHAR/TEXT columns in a different ways when the
          truncated characters are spaces:
          1. CHAR(N) columns silently ignore end-space truncation;
          2. TEXT columns post a truncation warning/error in the
             non-strict/strict mode.
          3. VARCHAR columns always post a truncation note in
             any mode.
        
          Space truncation processing has been synchronised over
          CHAR/VARCHAR/TEXT columns: current behavior of VARCHAR
          columns has been propagated as standard.
        
          Binary-encoded string/BLOB columns are not affected.
        
        
        ------------------------------------------------------------------------
        r2387 | vasil | 2008-03-27 08:49:05 +0200 (Thu, 27 Mar 2008) | 8 lines
        
        branches/5.1:
        
        Check whether *trx->mysql_query_str is != NULL in addition to
        trx->mysql_query_str. This adds more safety.
        
        This may or may not fix Bug#35226 RBR event crashes slave.
        
        
        ------------------------------------------------------------------------
        r2388 | vasil | 2008-03-27 14:02:34 +0200 (Thu, 27 Mar 2008) | 7 lines
        
        branches/5.1:
        
        Swap the order in which mysql_thd, mysql_query_str and *mysql_query_str
        are checked for non-NULL.
        
        Suggested by:	Marko
        
        ------------------------------------------------------------------------
        r2419 | vasil | 2008-04-23 19:08:06 +0300 (Wed, 23 Apr 2008) | 9 lines
        
        branches/5.1:
        
        Change the fix for Bug#32440 to show bytes instead of kilobytes in
        INFORMATION_SCHEMA.TABLES.DATA_FREE.
        
        Suggested by:	Domas Mituzas <domas@mysql.com>
        Approved by:	Heikki
        
        
        ------------------------------------------------------------------------
        r2420 | calvin | 2008-04-24 15:25:30 +0300 (Thu, 24 Apr 2008) | 4 lines
        
        branches/5.1: Fix bug#29507 TRUNCATE shows to many rows effected
        
        In InnoDB, the row count is only a rough estimate used by SQL
        optimization. InnoDB is now return row count 0 for TRUNCATE operation.
        ------------------------------------------------------------------------
        r2421 | calvin | 2008-04-24 15:32:30 +0300 (Thu, 24 Apr 2008) | 6 lines
        
        branches/5.1: Fix bug#35537 - Innodb doesn't increment handler_update
        and handler_delete
        
        Add the calls to ha_statistic_increment() in ha_innobase::delete_row()
        and ha_innobase::update_row().
        
        ------------------------------------------------------------------------
        r2422 | vasil | 2008-04-24 16:00:30 +0300 (Thu, 24 Apr 2008) | 11 lines
        
        branches/5.1:
        
        Fix Bug#36169 create innodb compressed table with too large row size crashed
        
        Sometimes it is possible that
        row_drop_table_for_mysql(index->table_name, trx, FALSE); is invoked in
        row_create_index_for_mysql() when the index object is freed so copy the
        table name to a safe place beforehand and use the copy.
        
        Approved by:	Sunny
        
        ------------------------------------------------------------------------
      22cd31a6
  4. 17 Mar, 2008 1 commit
  5. 28 Jan, 2008 1 commit
  6. 07 Jan, 2008 1 commit
  7. 04 Dec, 2007 1 commit
    • marko's avatar
      branches/zip: Merge r2154 from trunk: · 244c9eed
      marko authored
      innodb.result, innodb.test: Revert the changes in r2145.
      
      The tests that were removed by MySQL
      
      ChangeSet@1.2598.2.6  2007-11-06 15:42:58-07:00  tsmith@hindu.god
      
      were moved to a new test, innodb_autoinc_lock_mode_zero, which is
      kept in the MySQL BitKeeper tree.
      244c9eed
  8. 30 Nov, 2007 1 commit
  9. 16 Nov, 2007 1 commit
  10. 18 Oct, 2007 1 commit
  11. 20 Sep, 2007 1 commit
  12. 30 Aug, 2007 1 commit
  13. 01 Aug, 2007 2 commits
  14. 14 May, 2007 1 commit
  15. 04 Apr, 2007 2 commits
    • marko's avatar
      branches/zip: Fix the merge of branches/fast-index-creation -r1413 in r1414. · 1ac0e7f0
      marko authored
      innodb.test: The error code 1540 has been renumbered to 1542.
      innodb.result: Adjust the expected value of Innodb_buffer_pool_pages_total.
      Something may have changed in the BLOB handling in branches/zip.
      
      ha_innodb.cc: Add ha_innobase:: prefix to some DBUG_ENTER macros.
      
      row_merge_create_temporary_table(): Free the heap only after invoking
      row_create_table_for_mysql().  The table->col_names points to the heap
      until the system columns are added by row_create_table_for_mysql().
      
      TODO: use the filename-safe encoding in temporary table names.  Test
      extensively under Valgrind and fix all errors found.  Eliminate
      merge_rec_t and rewrite row0merge.c to write the records directly to
      the merge blocks.
      1ac0e7f0
    • marko's avatar
      branches/zip: Merge branches/fast-index-creation -r1413. · fc65b08f
      marko authored
      Fix some bugs.  The tests innodb and innodb-index fail, but that might
      be due to an old MySQL source tree being used.
      fc65b08f
  16. 02 Apr, 2007 1 commit
  17. 01 Mar, 2007 1 commit
  18. 18 Jan, 2007 1 commit
  19. 11 Aug, 2006 1 commit
  20. 08 May, 2006 1 commit
  21. 12 Apr, 2006 1 commit
  22. 17 Feb, 2006 1 commit
  23. 29 Nov, 2005 1 commit
  24. 27 Oct, 2005 1 commit