1. 08 Apr, 2006 1 commit
  2. 07 Apr, 2006 21 commits
  3. 06 Apr, 2006 18 commits
    • unknown's avatar
      Implement --warning-mode in SETUP.sh. The value of the · 80cd9c14
      unknown authored
      argument can be either "pedantic" or "old" (actually, or anything
      else). In case of "pedantic" mode, use -ansi -pedantic compilation
      flags. Fix the build to compile in pedantic mode. (Version 3 of
      the patch, with after-review fixes)
      
      
      BUILD/SETUP.sh:
        Implement --warning-mode in SETUP.sh. The value of the
        argument can be either "pedantic" or "old" (actually, or anything
        else). In case of "pedantic" mode, use -ansi -pedantic compilation
        flags.
      BUILD/compile-pentium-debug-max-no-embedded:
        Rename base_max_configs to base_no_embedded_configs
      BUILD/compile-pentium-debug-max:
        Use double quotes around $@
      BUILD/compile-pentium-valgrind-max:
        Pass command line arguments to SETUP.sh. Allows calling
        compile-pentium-valgrind-max --warning-mode=pedantic
      include/my_global.h:
        Remove an unnecessary ifdef: -pedantic hides the system-wide
        definition of ulong on Linux. In case there is no -pedantic, 
        the system-wide definition is available and HAVE_ULONG is defined
        by configure.
      80cd9c14
    • unknown's avatar
      Merge bk-internal.mysql.com:/home/bk/mysql-5.1-new · 4a3072b0
      unknown authored
      into serg.mylan:/usr/home/serg/Abk/mysql-5.1
      
      4a3072b0
    • unknown's avatar
      Merge mysql.com:/home/greenman/workspace-mysql/mysql/mysql-5.0 · 2639449a
      unknown authored
      into  mysql.com:/home/greenman/workspace-mysql/mysql/bug-5.0-16240
      
      2639449a
    • unknown's avatar
      Merge spetrunia@bk-internal.mysql.com:/home/bk/mysql-5.0 · 3593d257
      unknown authored
      into  mysql.com:/home/psergey/mysql-5.0-bug18237-review
      
      3593d257
    • unknown's avatar
      Remove redundant code in opt_sum_query() · 221e5e06
      unknown authored
      221e5e06
    • unknown's avatar
      Merge spetrunia@bk-internal.mysql.com:/home/bk/mysql-5.1-new · 49130410
      unknown authored
      into mysql.com:/home/psergey/mysql-5.1-bug18558-pnd
      
      
      sql/opt_range.cc:
        Auto merged
      49130410
    • unknown's avatar
      BUG#18558 "Partition pruning results are incorrect for certain class of WHERE clauses" : · 898dc67f
      unknown authored
      * Produce right results for conditions that were transformed to "(partitioning_range) AND
        (list_of_subpartitioning_ranges)": make each partition id set iterator auto-reset itself
        after it has returned all partition ids in the sequence 
      * Fix "Range mapping" and "Range mapping" partitioning interval analysis functions to 
        correctly deal with NULL values. 
      
      
      mysql-test/r/partition_pruning.result:
        Testcase for BUG#18558
      mysql-test/t/partition_pruning.test:
        Testcase for BUG#18558
      sql/opt_range.cc:
        BUG#18558: Move partition set iterator initialization to sql_partition.cc, comment fixes
      sql/partition_info.h:
        BUG#18558: Make each partition set iterator auto-reset itself after it has returned all 
        partition ids in the set it enumerates.
      sql/sql_partition.cc:
        BUG#18558: 
        - Make each partition set iterator auto-reset itself after it has returned all 
          partition ids in the set it enumerates. 
        - Fix partition interval analysis to correctly handle intervals with one or both
          NULL bounds.
      sql/sql_partition.h:
        BUG#18558: 
         - Make each partition set iterator auto-reset itself after it has returned all 
           partition ids in the set it enumerates. 
         - Rename PARTITION_ITERATOR::has_null_value to ret_null_part
      898dc67f
    • unknown's avatar
      Fix for Bug #16240 · ba54fa58
      unknown authored
      
      support-files/mysql.server.sh:
        Fixed so that if the datadir has been set via the command line,
        it won't be reset by specifing the basedir after.
      ba54fa58
    • unknown's avatar
      Backport of 5.1 test options "--with-ndbcluster" and "--with-ndbcluster-only" as dummies (ignored). · 818138f1
      unknown authored
      
      mysql-test/mysql-test-run.sh:
        Make "mysql-test-run.sh" accept (and ignore) the options "--with-ndbcluster" 
        and "--with-ndbcluster-only".
        This is necessary because newer build tools will issue them, and the test 
        script should tolerate that.
        Backport from 5.1 (Tomas Ulin, 2006-01-17)
      818138f1
    • unknown's avatar
      b9b9f40f
    • unknown's avatar
      changes to make plugin_example useful as a template: · 567c0cee
      unknown authored
      force pkglibdir to be in "mysql" package, template files:
      AUTHORS, ChangeLog, NEWS, README, configure.in
      
      
      plugin/fulltext/Makefile.am:
        changes to make plugin_example useful as a template:
        force pkglibdir to be in "mysql" package
      567c0cee
    • unknown's avatar
      Bug#18836 - fulltext parser plugin is called recursively. · 80aebe22
      unknown authored
      Don't use the same param in recursive call.
      Also, the fix makes it safe for a plugin to replace param->mysql_add_word
      
      
      storage/myisam/ft_nlq_search.c:
        Bug#18836 - fulltext parser plugin is called recursively.
        Don't use the same param in recursive call.
      storage/myisam/ft_update.c:
        Bug#18836 - fulltext parser plugin is called recursively.
        Don't use the same param in recursive call.
      storage/myisam/ftdefs.h:
        Bug#18836 - fulltext parser plugin is called recursively.
        Don't use the same param in recursive call.
      80aebe22
    • unknown's avatar
      fixed reading of free'd memory when opening a table with non-existing plugin · 41b42530
      unknown authored
      
      sql/table.cc:
        fixed reading of free'd memory
      41b42530
    • unknown's avatar
      Bug#17112 - SHOW PLUGIN should be SHOW PLUGINS · 95051ce6
      unknown authored
      
      sql/lex.h:
        SHOW PLUGINS - BUG#17112
      sql/sql_yacc.yy:
        SHOW PLUGINS - BUG#17112
      95051ce6
    • unknown's avatar
      Merge april.(none):/home/svoj/devel/mysql/BUG14945/mysql-5.0 · a955cc20
      unknown authored
      into  april.(none):/home/svoj/devel/mysql/BUG14945/mysql-5.1-new
      
      
      mysql-test/mysql-test-run.pl:
        Auto merged
      mysql-test/r/sp.result:
        Auto merged
      mysql-test/t/sp.test:
        Auto merged
      sql/sql_parse.cc:
        Auto merged
      sql/sql_delete.cc:
        Manual merge
      a955cc20
    • unknown's avatar
      Merge abarkov@bk-internal.mysql.com:/home/bk/mysql-5.1-new · 1e59d9c8
      unknown authored
      into  mysql.com:/usr/home/bar/mysql-5.1-new
      
      1e59d9c8
    • unknown's avatar
      Merge svojtovich@bk-internal.mysql.com:/home/bk/mysql-5.0 · e147a4a2
      unknown authored
      into  april.(none):/home/svoj/devel/mysql/BUG14945/mysql-5.0
      
      e147a4a2
    • unknown's avatar
      Fix for bug#14945 "Truncate table doesn't reset the auto_increment · 0d373cdd
      unknown authored
      counter".
      
      When TRUNCATE TABLE was called within an stored procedure the
      auto_increment counter was not reset to 0 even if straight
      TRUNCATE for this table did this.
      
      This fix makes TRUNCATE in stored procedures to be handled exactly
      in the same way as straight TRUNCATE. We achieve this by rolling
      back the fix for bug 8850, which is no longer needed since stored
      procedures don't require prelocked mode anymore (and TRUNCATE is
      not allowed in stored functions or triggers).
      
      
      mysql-test/r/sp.result:
        Test case for BUG#14945.
      mysql-test/t/sp.test:
        Test case for BUG#14945.
      sql/sql_delete.cc:
        Handle TRUNCATE in stored procedures exactly in the same way as straight
        TRUNCATE (i.e. without falling back to DELETE if possible). We achieve
        this by rolling back the fix for bug 8850, which is no longer relevant
        since stored procedures don't require prelocked mode anymore
        (and TRUNCATE is not allowed in stored functions or triggers).
      sql/sql_parse.cc:
        Handle TRUNCATE in stored procedures exactly in the same way as straight
        TRUNCATE (i.e. without falling back to DELETE if possible). We achieve
        this by rolling back the fix for bug 8850, which is no longer relevant
        since stored procedures don't require prelocked mode anymore
        (and TRUNCATE is not allowed in stored functions or triggers).
      0d373cdd