1. 09 Jun, 2005 27 commits
  2. 08 Jun, 2005 13 commits
    • unknown's avatar
      Merge bk-internal.mysql.com:/home/bk/mysql-5.0 · 2e43fc33
      unknown authored
      into mysql.com:/home/dlenev/src/mysql-5.0-bgmd
      
      
      sql/sql_yacc.yy:
        Auto merged
      2e43fc33
    • unknown's avatar
      Disable dynamic SQL in stored routines. · 3fbdaf36
      unknown authored
      This is to close Bug#10975, Bug#7115, Bug#10605 
      This feature will be implemented in a future release.
      
      
      mysql-test/r/sp-error.result:
        Test results fixed (test coverage for disabled Dynamic SQL in SP).
      mysql-test/t/sp-error.test:
        Test coverage to disable Dynamic SQL in stored routines.
      sql/sql_yacc.yy:
        Disable dynamic SQL in stored routines.
      3fbdaf36
    • unknown's avatar
      Manual merge · c6c49859
      unknown authored
      
      sql/mysql_priv.h:
        Auto merged
      sql/sql_lex.h:
        Auto merged
      sql/sql_parse.cc:
        Auto merged
      sql/sql_yacc.yy:
        Auto merged
      c6c49859
    • unknown's avatar
      Fix for bug #11158 "Can't perform multi-delete in stored procedure". · 4e0bbc1b
      unknown authored
      In order to make multi-delete SP friendly we need to have all table 
      locks for the elements of main statement table list properly set 
      at the end of parsing.
      
      Also performed small cleanup: We don't need relink_tables_for_multidelete()
      any longer since the only case now when TABLE_LIST::correspondent_table
      is non-zero are tables in auxilary table list of multi-delete and these
      tables are handled specially in mysql_multi_delete_prepare().
      
      
      mysql-test/r/sp-threads.result:
        Added test case for bug #11158 "Can't perform multi-delete in stored
        procedure".
      mysql-test/t/sp-threads.test:
        Added test case for bug #11158 "Can't perform multi-delete in stored
        procedure".
      sql/mysql_priv.h:
        - Removed third argument from the declaration of multi_delete_precheck()
          as nowdays we calculate number of tables in multi-delete from which
          we are going to delete rows right at the end of statement parsing.
        - Introduced definition of multi_delete_set_locks_and_link_aux_tables()
          which is responsible for propagation of proper table locks from
          multi-delete's auxilary table list to the main list and binding
          corresponding tables in these two lists.
      sql/sql_base.cc:
        Removed relink_tables_for_multidelete() routine and its invocations.
        We don't need them in 5.0 since the only case now when
        TABLE_LIST::correspondent_table is non-zero are tables in auxilary table
        list of multi-delete and these tables are handled specially in
        mysql_multi_delete_prepare().
      sql/sql_lex.h:
        LEX::table_count
          Added description of new role of this LEX member for multi-delete. 
          Now for this statement we store number of tables from which we should
          delete records there.
      sql/sql_parse.cc:
        multi_delete_precheck():
          Moved code which is responsible for iterating through auxilary table
          list and binding its elements with corresponding elements of main
          table list, and properly updating locks in it to separate function -
          multi_delete_set_locks_and_link_aux_tables(). This is because in order
          to make multi-delete SP friendly we need to have all locks set properly
          at the end of statement parsing. So we are introducing new function
          which will be called from parser.
          We also calculate number of tables from which we are going to perform
          deletions there and store this number for later usage in
          LEX::table_count.
          Also removed some no longer needed code.
      sql/sql_prepare.cc:
        mysql_test_multidelete():
          Now multi_delete_precheck() takes only two arguments, so we don't
          need to pass fake third parameter.
      sql/sql_yacc.yy:
        delete:
          In order to make multi-delete SP friendly we need to have all table 
          locks for the elements of main statement table list properly set 
          at the end of parsing.
      4e0bbc1b
    • unknown's avatar
      WL#2286 - Compile MySQL w/YASSL support · fca6c2fe
      unknown authored
      Fix for yaSSL compilation failure on ia64 platform.
      
      
      extra/yassl/taocrypt/include/types.hpp:
        Do not use assembler when yaSSL compiled with icc on ia64 platform.
      fca6c2fe
    • unknown's avatar
      Merge abotchkov@bk-internal.mysql.com:/home/bk/mysql-5.0 · 0537106b
      unknown authored
      into deer.(none):/home/hf/work/mysql-5.0.9764
      
      
      0537106b
    • unknown's avatar
      Fix for bug #10896 (0.00 > -0.00) · 1c5c678c
      unknown authored
      
      mysql-test/r/type_newdecimal.result:
        test result fixed
      mysql-test/t/type_newdecimal.test:
        test case added
      sql/my_decimal.h:
        we neede to check for zero here not to get -0.00
      1c5c678c
    • unknown's avatar
      Trim trailing spaces. · 8aba6f29
      unknown authored
      8aba6f29
    • unknown's avatar
      Merge abotchkov@bk-internal.mysql.com:/home/bk/mysql-5.0 · 60a5939f
      unknown authored
      into deer.(none):/home/hf/work/mysql-5.0.9764
      
      
      60a5939f
    • unknown's avatar
      Fix for bug #9764 (DISTINCT IFNULL truncates data) · 2fded7d5
      unknown authored
      
      mysql-test/r/create.result:
        test result fixed
      mysql-test/r/distinct.result:
        test result fixed
      mysql-test/t/distinct.test:
        test case added
      sql/item_cmpfunc.cc:
        max_length should be calculated differently for DECIMAL_RESULT and others
      2fded7d5
    • unknown's avatar
      Cleanup sql_prepare.cc · 70c0f310
      unknown authored
      
      sql/sql_prepare.cc:
        Cleanup mysql_test_* family of calls: now we don't send error message
        from mysql_stmt_prepare, so no need to support -1 return code 
        (meaning error is not sent to client) in these functions.
        Move unit->cleanup() to mysql_stmt_prepare() as it's done in most
        of the mysql_test_ functions, and is a no-op for those which don't
        call unit->prepare(). This should make fixing of Bug#10729 (cursors)
        easier.
      70c0f310
    • unknown's avatar
      Merge mysql.com:/home/jonas/src/mysql-4.1 · dbfce2a5
      unknown authored
      into mysql.com:/home/jonas/src/mysql-5.0
      
      
      ndb/src/kernel/blocks/backup/Backup.cpp:
        Auto merged
      ndb/src/kernel/blocks/dbacc/DbaccMain.cpp:
        Auto merged
      ndb/src/kernel/blocks/dblqh/DblqhMain.cpp:
        Auto merged
      ndb/test/ndbapi/testNdbApi.cpp:
        Auto merged
      ndb/test/run-test/daily-basic-tests.txt:
        Auto merged
      ndb/tools/restore/Restore.cpp:
        Auto merged
      ndb/tools/restore/consumer_restore.cpp:
        Auto merged
      dbfce2a5
    • unknown's avatar
      bug#11166 - ndb · a7917b1e
      unknown authored
        Fix potential inconsistency when running ndb_restore due to faulty parsing
          of backup log wrt inserts
      
      
      ndb/src/kernel/blocks/backup/Backup.cpp:
        Make sure that entire stopGCP is in log
      ndb/tools/restore/Restore.cpp:
        
          Notice: this will not group and commit the deltas listed below
          into a ChangeSet, because there are no ChangeSet comments.
          Click [Checkin] again to check in only the commented deltas,
          or type Control-l to go back and provide ChangeSet comments.
      ndb/tools/restore/Restore.hpp:
        Keep track of last gci to next iteration
      ndb/tools/restore/consumer_restore.cpp:
        Handle insert in log
        Only allow certain errors
      a7917b1e