1. 06 May, 2011 3 commits
  2. 05 May, 2011 6 commits
    • Luis Soares's avatar
      BUG#12354268 · 37568891
      Luis Soares authored
      Automerge from mysql-5.1 into mysql-5.5.
      37568891
    • Luis Soares's avatar
      BUG#12354268 · ac00a021
      Luis Soares authored
      Automerged bzr bundle from bug report:
      luis.soares@oracle.com-20110505224815-6ob90n7suxsoizvs.bundle
      ac00a021
    • Luis Soares's avatar
      BUG#11762616: BUG#55229: 'POSTION' · 445e52a5
      Luis Soares authored
      Manual merge from mysql-5.1 into mysql-5.5.
      
      Conflicts
      =========
      Text conflict in mysql-test/suite/rpl/t/rpl_row_until.test
      Text conflict in sql/handler.h
      Text conflict in storage/archive/ha_archive.cc
      445e52a5
    • Luis Soares's avatar
      BUG#11762616: BUG#55229: 'POSTION' · d9398200
      Luis Soares authored
                  
      Fix for all "postion" in Oracle files (s/postion/position). 
      Updated the copyright notices where needed.
      d9398200
    • Luis Soares's avatar
      BUG#12425924 · 2e39cdcc
      Luis Soares authored
      Automerging cset into latest mysql-5.5.
      2e39cdcc
    • Luis Soares's avatar
      BUG#12354268: MYSQLBINLOG --BASE64-OUTPUT=DECODE-ROWS DOES NOT · 9edcb769
      Luis Soares authored
      WORK WITH --START-POSITION
            
      If setting --start-position to start after the FD event, mysqlbinlog
      will output an error stating that it has not found an FD event.
      However, its not that mysqlbinlog does not find it but rather that it
      does not processes it in the regular way (i.e., it does not print it).
      Given that one is using --base64-output=DECODE-ROWS then not printing
      it is actually fine.
            
      To fix this, we make mysqlbinlog not to complain when it has not
      printed the FD event, is outputing in base64, but is decoding the
      rows.
      9edcb769
  3. 04 May, 2011 5 commits
    • Luis Soares's avatar
      BUG#12425924: SEMI-SYNC RELATED VALGRIND WARNINGS IN 5.5 CODEBASE · 6aa569e8
      Luis Soares authored
      There are a couple of valgrind warnings in 5.5 codebase, that
      do not exist in 5.6. The root cause was found and fixed in 5.6
      codebase before (BUG#11763880 and BUG#11763879), but the patches
      were only pushed to 5.6.
      
      To fix it in 5.5, we cherrypicked the csets from 5.6 and merged 
      them in 5.5.
      6aa569e8
    • Alexander Nozdrin's avatar
      Manual merge from mysql-5.1. · 86b20196
      Alexander Nozdrin authored
      86b20196
    • Luis Soares's avatar
      Automerged (cherrypicked) cset from 5.6: · ca10c2d2
      Luis Soares authored
      zhenxing.he@sun.com-20101117085902-n9gfvlkmm44t38y0
        
      This takes care of valgrind warnings in 5.5 that exhibit
      the same trace as in BUG#11763879 (BUG#56649).
      ca10c2d2
    • Luis Soares's avatar
      Automerged (cherrypicked) cset from 5.6: · 7b27523b
      Luis Soares authored
      zhenxing.he@sun.com-20101202073812-iel8lvhmulyagtsv
      
      This takes care of valgrind warnings in 5.5 that exhibit
      the same trace as in BUG#11763880 (BUG#56650).
      7b27523b
    • Alexander Nozdrin's avatar
      Patch for Bug#12394306: the sever may crash if mysql.event is corrupted. · f5dde273
      Alexander Nozdrin authored
      The problem was that wrong structure of mysql.event was not detected and
      the server continued to use wrongly-structured data.
      
      The fix is to check the structure of mysql.event after opening before
      any use. That makes operations with events more strict -- some operations
      that might work before throw errors now. That seems to be Ok.
      
      Another side-effect of the patch is that if mysql.event is corrupted,
      unrelated DROP DATABASE statements issue an SQL warning about inability
      to open mysql.event table. 
      f5dde273
  4. 03 May, 2011 2 commits
  5. 02 May, 2011 5 commits
  6. 30 Apr, 2011 1 commit
  7. 29 Apr, 2011 15 commits
  8. 28 Apr, 2011 2 commits
    • Rafal Somla's avatar
      BUG#11879051: FIRST REPLY LENGTH LIMIT (255) CAN BE VIOLATED · 32cc7d19
      Rafal Somla authored
      BEFORE: First packet sent by client-side plugin (generated by Windows
      function InitializeSecurityContext()) could be longer than 255 bytes 
      violating the limitation imposed by authentication protocol.
      
      AFTER: Handshake protocol is  changed so that if first client's reply is 
      longer than 254 bytes then  it is be sent in 2 parts. However, for replies
      shorter than 255 bytes nothing changes.
      
      ADDITIONAL CHANGES: 
      - The generic packet processing loop  (Handshake::packet_processing_loop) 
      has been refactored. Communication with the peer has been abstracted
      into virtual methods read/write_packet() which are implemented in client 
      and server and transparently do the required splitting and gluing of packets.
      - Make it possible to optionally use dbug library in the plugin.
      - Add code for testing splitting of long first client reply.
      32cc7d19
    • Rafal Somla's avatar
      Bug#11766631 (59780) - Move the client authentication_windows plugin · c50c571f
      Rafal Somla authored
      into the server repository
      
      This patch adds client windows authentication plugin code to the client 
      library libmysql (only on Windows platform). The plugin is compiled into 
      the library and added to the list of built-in plugins. This way clients 
      should be able to connect to a server which uses windows authentication 
      plugin even as an SQL user which uses such authentication.
      
      Note: this makes the client library to depend on Secur32 Windows system
      library. When building clients, they must be linked against Secur32. 
      Command mysql_config --libs correctly lists Secur32 as a required 
      dependency.
      c50c571f
  9. 29 Apr, 2011 1 commit