1. 23 Mar, 2009 10 commits
  2. 20 Mar, 2009 12 commits
  3. 19 Mar, 2009 1 commit
    • marko's avatar
      branches/zip: Merge revisions 4400:4481 from branches/5.1: · b0b24206
      marko authored
        ------------------------------------------------------------------------
        r4481 | marko | 2009-03-19 15:01:48 +0200 (Thu, 19 Mar 2009) | 6 lines
      
        branches/5.1: row_unlock_for_mysql(): Do not unlock records that were
        modified by the current transaction.  This bug was introduced or unmasked
        in r4400.
      
        rb://97 approved by Heikki Tuuri
        ------------------------------------------------------------------------
      b0b24206
  4. 18 Mar, 2009 3 commits
  5. 17 Mar, 2009 3 commits
  6. 16 Mar, 2009 3 commits
  7. 12 Mar, 2009 3 commits
    • marko's avatar
      branches/zip: Merge revisions 4359:4400 from branches/5.1: · 74013e36
      marko authored
        ------------------------------------------------------------------------
        r4399 | marko | 2009-03-12 09:38:05 +0200 (Thu, 12 Mar 2009) | 2 lines
      
        branches/5.1: row_sel_get_clust_rec_for_mysql(): Store the cursor position
        also for unlock_row().  (Bug #39320)
        ------------------------------------------------------------------------
        r4400 | marko | 2009-03-12 10:06:44 +0200 (Thu, 12 Mar 2009) | 5 lines
      
        branches/5.1: Fix a bug in multi-table semi-consistent reads.
        Remember the acquired record locks per table handle (row_prebuilt_t)
        rather than per transaction (trx_t), so that unlock_row should successfully
        unlock all non-matching rows in multi-table operations.
        This deficiency was found while investigating Bug #39320.
        ------------------------------------------------------------------------
      
      These were submitted as rb://94 and rb://96 and approved by Heikki Tuuri.
      74013e36
    • marko's avatar
      branches/zip: trx_sys_create_doublewrite_buf(): As the dummy change, · 64083dd3
      marko authored
      initialize FIL_PAGE_TYPE.  This will make it easier to write the debug
      assertions for ibbackup --apply-log.
      64083dd3
    • marko's avatar
      branches/zip: btr_store_big_rec_extern_fields(): Initialize FIL_PAGE_TYPE · 27f859ce
      marko authored
      in a separate redo log entry.  This will make ibbackup --apply-log
      debugging easier.
      27f859ce
  8. 09 Mar, 2009 1 commit
    • calvin's avatar
      branches/zip: remove compile flag MYSQL_SERVER for dynamic plugin · 63600738
      calvin authored
      The dynamic plugin on Windows used to be built with MYSQL_SERVER
      compile flag, while it is not the case for other platforms.
      r3797 assumed MYSQL_SERVER was not defined for dynamic plugin,
      which introduced the engine crash during dropping a database.
      63600738
  9. 05 Mar, 2009 4 commits
    • vasil's avatar
      branches/zip: · a295841e
      vasil authored
      Add ChangeLog entry for the bugfix in c4360.
      a295841e
    • vasil's avatar
      branches/zip: Merge revision 4359 from branches/5.1: · 45f0e3ee
      vasil authored
        ------------------------------------------------------------------------
        r4359 | vasil | 2009-03-05 21:42:01 +0200 (Thu, 05 Mar 2009) | 14 lines
        Changed paths:
           M /branches/5.1/handler/ha_innodb.cc
        
        branches/5.1:
        
        Merge a change from MySQL:
        
          ------------------------------------------------------------
          revno: 2747
          committer: Timothy Smith <timothy.smith@sun.com>
          branch nick: 51
          timestamp: Fri 2009-01-16 17:49:07 +0100
          message:
            Add another cast to ignore int/ulong difference in error types, silence warning on Win64
          modified:
            storage/innobase/handler/ha_innodb.cc
        
        ------------------------------------------------------------------------
      45f0e3ee
    • vasil's avatar
      branches/zip: Merge revision 4358 from branches/5.1 (resolving a conflict): · 86fab45a
      vasil authored
        ------------------------------------------------------------------------
        r4358 | vasil | 2009-03-05 21:21:10 +0200 (Thu, 05 Mar 2009) | 21 lines
        Changed paths:
           M /branches/5.1/handler/ha_innodb.cc
        
        branches/5.1:
        
        Merge a change from MySQL:
        
          ------------------------------------------------------------
          revno: 2728.19.1
          committer: Alfranio Correia <alfranio.correia@sun.com>
          branch nick: mysql-5.1-bugteam
          timestamp: Tue 2009-02-03 11:36:46 +0000
          message:
            BUG#42445 Warning messages in innobase/handler/ha_innodb.cc
                  
            There was a type casting problem in the storage/innobase/handler/ha_innodb.cc,
            (int ha_innobase::write_row(...)). Innobase uses has an internal error variable
            of type 'ulint' while mysql uses an 'int'. 
                  
            To fix the problem the function manipulates an error variable of
            type 'ulint' and only casts it into 'int' when needs to return the value.
          modified:
            storage/innobase/handler/ha_innodb.cc
        
        ------------------------------------------------------------------------
      86fab45a
    • vasil's avatar
      branches/zip: Merge revisions 4287:4357 from branches/5.1: · db2dc146
      vasil authored
        ------------------------------------------------------------------------
        r4325 | sunny | 2009-03-02 02:28:52 +0200 (Mon, 02 Mar 2009) | 10 lines
        Changed paths:
           M /branches/5.1/handler/ha_innodb.cc
           M /branches/5.1/mysql-test/innodb-autoinc.result
           M /branches/5.1/mysql-test/innodb-autoinc.test
        
        branches/5.1: Bug#43203: Overflow from auto incrementing causes server segv
        It was not a SIGSEGV but an assertion failure. The assertion was checking
        the invariant that *first_value passed in by MySQL doesn't contain a value
        that is greater than the max value for that type. The assertion has been
        changed to a check and if the value is greater than the max we report a
        generic AUTOINC failure.
        
        rb://93
        Approved by Heikki
        
        ------------------------------------------------------------------------
      db2dc146