An error occurred fetching the project authors.
  1. 10 Dec, 2007 1 commit
  2. 23 Nov, 2007 1 commit
  3. 30 Oct, 2007 1 commit
  4. 11 Oct, 2007 1 commit
    • mats@kindahl-laptop.dnsalias.net's avatar
      BUG#29549 (Endians: test failures on Solaris): · c4298a3f
      mats@kindahl-laptop.dnsalias.net authored
      Refactoring code to add parameter to pack() and unpack() functions with
      purpose of indicating if data should be packed in little-endian or
      native order. Using new functions to always pack data for binary log
      in little-endian order. The purpose of this refactoring is to allow
      proper implementation of endian-agnostic pack() and unpack() functions.
      
      Eliminating several versions of virtual pack() and unpack() functions
      in favor for one single virtual function which is overridden in
      subclasses.
      
      Implementing pack() and unpack() functions for some field types that
      packed data in native format regardless of the value of the
      st_table_share::db_low_byte_first flag.
      
      The field types that were packed in native format regardless are:
      Field_real, Field_decimal, Field_tiny, Field_short, Field_medium,
      Field_long, Field_longlong, and Field_blob.
      
      Before the patch, row-based logging wrote the rows incorrectly on
      big-endian machines where the storage engine defined its own
      low_byte_first() to be FALSE on big-endian machines (the default
      is TRUE), while little-endian machines wrote the fields in correct
      order. The only known storage engine that does this is NDB. In effect,
      this means that row-based replication from or to a big-endian
      machine where the table was using NDB as storage engine failed if the
      other engine was either non-NDB or on a little-endian machine.
      
      With this patch, row-based logging is now always done in little-endian
      order, while ORDER BY uses the native order if the storage engine
      defines low_byte_first() to return FALSE for big-endian machines.
      
      In addition, the max_data_length() function available in Field_blob
      was generalized to the entire Field hierarchy to give the maximum
      number of bytes that Field::pack() will write.
      c4298a3f
  5. 10 Oct, 2007 1 commit
    • jmiller/ndbdev@mysql.com/ndb15.mysql.com's avatar
      .del-rpl_stm_extraColmaster_ndb.test~5ac81fa1ec366ba: · 44352e16
        Delete: mysql-test/suite/rpl/t/rpl_stm_extraColmaster_ndb.test
      .del-rpl_row_extraColmaster_ndb.result~a2c64bae75b49d2:
        Delete: mysql-test/suite/rpl/r/rpl_row_extraColmaster_ndb.result
      .del-rpl_row_extraColmaster_ndb.test~523b0954869c4423:
        Delete: mysql-test/suite/rpl/t/rpl_row_extraColmaster_ndb.test
      Many files:
        merged and cleanup of test cases
      44352e16
  6. 30 Jul, 2007 1 commit
  7. 29 Jul, 2007 1 commit
    • cbell/Chuck@mysql_cab_desk.'s avatar
      WL#3228 (NDB) : RBR using different table defs on slave/master · 537c23e8
      cbell/Chuck@mysql_cab_desk. authored
      This patch adds the ability to store extra field metadata in the table
      map event. This data can include pack_length() or field_lenght() for
      fields such as CHAR or VARCHAR enabling developers to add code that
      can check for compatibilty between master and slave columns. More 
      importantly, the extra field metadata can be used to store data from the
      master correctly should a VARCHAR field on the master be <= 255 bytes 
      while the same field on the slave is > 255 bytes. 
      
      The patch also includes the needed changes to unpack to ensure that data
      which is smaller on the master can be unpacked correctly on the slave.
      
      WL#3915 : (NDB) master's cols > slave
      
      Slave starts accepting and handling rows of master's tables which have more columns.
      The most important part of implementation is how to caclulate the amount of bytes to
      skip for unknown by slave column.
      537c23e8