1. 13 Jul, 2006 7 commits
    • unknown's avatar
      Merge tnurnberg@bk-internal.mysql.com:/home/bk/mysql-5.0 · f7bbf78a
      unknown authored
      into  mysql.com:/home/tnurnberg/work/mysql-5.0-21014
      
      f7bbf78a
    • unknown's avatar
      Bug#21014: Segmentation fault of mysqldump on view · 3b714a08
      unknown authored
      mysqldump did not select the correct database before trying to dump
      views from it. this resulted in an empty result set, which in turn
      startled mysql-dump into a core-dump.  this only happened for views,
      not for tables, and was only visible with multiple databases that
      weren't by sheer luck in the order mysqldump required, anyway. this
      fixes by selecting the correct database before dumping views; it also
      catches the empty set-condition if it should occur for other reasons.
      
      
      client/mysqldump.c:
        Bug#21014: Segmentation fault of mysqldump on view
        
        failsafe: if "select ... from information_schema.views" returns an
        empty set, don't deref NULL; throw an error instead.
        
        fix: select the correct database not only before dumping tables, but
        before dumping views, as well.
      mysql-test/r/mysqldump.result:
        Bug#21014: Segmentation fault of mysqldump on view
        
        show that mysqldump selects the correct database before trying to dump
        views from it.
      mysql-test/t/mysqldump.test:
        Bug#21014: Segmentation fault of mysqldump on view
        
        show that mysqldump selects the correct database before trying to dump
        views from it.
      3b714a08
    • unknown's avatar
      Merge bk-internal.mysql.com:/home/bk/mysql-5.0 · 3630e829
      unknown authored
      into  zippy.(none):/home/cmiller/work/mysql/m50--07C2P
      
      3630e829
    • unknown's avatar
      Merge bk-internal.mysql.com:/home/bk/mysql-5.0-maint · d1b58f55
      unknown authored
      into  zippy.(none):/home/cmiller/work/mysql/m50-maint--07C2P
      
      d1b58f55
    • unknown's avatar
      Merge zippy.(none):/home/cmiller/work/mysql/merge/mysql-5.0 · 2bb833ae
      unknown authored
      into  zippy.(none):/home/cmiller/work/mysql/m50-maint--07C2P
      
      
      configure.in:
        Auto merged
      mysql-test/mysql-test-run.pl:
        Auto merged
      tests/mysql_client_test.c:
        manual merge
      2bb833ae
    • unknown's avatar
      Bug #19779: mysql_explain_log documentation is outdated. · 38c5a0e2
      unknown authored
      
      scripts/mysql_explain_log.sh:
        Changed explain_log.pl to mysql_explain_log.  Added usage information for printerror. Minor cleanup.
      38c5a0e2
    • unknown's avatar
      Merge bk@192.168.21.1:mysql-5.0-kt · e495aade
      unknown authored
      into  mysql.com:/home/hf/work/mysql-5.0.clean
      
      
      sql-common/client.c:
        Auto merged
      sql/item_strfunc.cc:
        Auto merged
      e495aade
  2. 12 Jul, 2006 4 commits
    • unknown's avatar
      Merge zippy.(none):/home/cmiller/mysql-4.1_bug18470 · 8cef0498
      unknown authored
      into  zippy.(none):/home/cmiller/work/mysql/m50-maint--07C2P
      
      
      configure.in:
        Auto merged
      8cef0498
    • unknown's avatar
      Fix a valgrind warning in type_date test. · b3180c89
      unknown authored
      
      sql/item_timefunc.cc:
        Fix a valgrind warning in type_date test.	
      b3180c89
    • unknown's avatar
      Bug#18470: Compile Failure: strings.s fails make with unknown pseudo-ops · 0daad2ff
      unknown authored
      The bug is thqt we use some nonstandard assembly codes in our strings
      source, and some assemblers don't know what to do with them:  Specifically,
      Sun's Solaris assembler and Apple's Darwin assembler balk at them.
      
      This patch, rather than trying to test for properties of the assembler, 
      which Autoconf doesn't have any decent facilites for, instead tries to
      compile the code in question and disables assembly if it fails.
      
      There's still the problem of unportable assembly, but I'll leave that 
      to someone who feels like rewriting and debugging it.
      
      
      configure.in:
        Actually try to compile the code in question, since a test for the CPU
        type is insufficient to determine whether our code will compile.
      0daad2ff
    • unknown's avatar
      Merge dl145k.mysql.com:/data0/mkindahl/bkroot/mysql-5.0 · 4136cfc3
      unknown authored
      into  dl145k.mysql.com:/data0/mkindahl/bk/mysql-5.0-rpl
      
      
      ndb/include/kernel/GlobalSignalNumbers.h:
        Auto merged
      ndb/src/kernel/blocks/dbdict/Dbdict.cpp:
        Auto merged
      ndb/src/kernel/blocks/dbdict/Dbdict.hpp:
        Auto merged
      ndb/src/kernel/blocks/dbdih/DbdihMain.cpp:
        Auto merged
      ndb/src/ndbapi/ndberror.c:
        Auto merged
      sql/ha_ndbcluster.cc:
        Auto merged
      sql/handler.h:
        Auto merged
      sql/sql_base.cc:
        Auto merged
      sql/sql_insert.cc:
        Auto merged
      4136cfc3
  3. 11 Jul, 2006 6 commits
  4. 10 Jul, 2006 22 commits
  5. 09 Jul, 2006 1 commit
    • unknown's avatar
      BUG#20919 temp tables closing fails when binlog is off · 259ab342
      unknown authored
      closing temp tables through end_thread
      had a flaw in binlog-off branch of close_temporary_tables where
      next table to close was reset via table->next
       for (table= thd->temporary_tables; table; table= table->next)
      which was wrong since the current table instance got destoyed at
      	close_temporary(table, 1);
      
      The fix adapts binlog-on branch method to engage the loop's internal 'next' variable which holds table->next prior table's destoying.
      
      
      
      sql/sql_base.cc:
        no-binlog branch is fixed: scanning across temporary_tables must be careful to save next table since the current is being destroyed inside of close_temporary. 
        binlog-is-open case is ok.
      259ab342