An error occurred fetching the project authors.
  1. 01 Oct, 2006 1 commit
  2. 30 Sep, 2006 1 commit
    • brian@zim.(none)'s avatar
      This patch adds handlerton passing to functions. NDB and Innodb still require... · 46ae2113
      brian@zim.(none) authored
      This patch adds handlerton passing to functions. NDB and Innodb still require a global hanlderton in the main code due to the nature of the sql_cache call back function (should be solveable... another patch).
      Partitioning now has a flag to allow disabling of engines from being compatible with partitioning. Cleaned up heap naming convention on panic call. 
      46ae2113
  3. 15 Sep, 2006 2 commits
  4. 13 Sep, 2006 2 commits
  5. 07 Sep, 2006 1 commit
  6. 06 Sep, 2006 1 commit
  7. 05 Sep, 2006 1 commit
  8. 01 Sep, 2006 1 commit
    • andrey@example.com's avatar
      WL#3337 (Event scheduler new architecture) · ca39997c
      andrey@example.com authored
      This is a post-review patch.
      
      Fixes the typelib implementation, available only in 5.1.11.
      
      --event-scheduler cmdline : DISABLED | ON | OFF | 0 | 1
      DISABLED - makes the scheduler unavailable during the server run
      (ON|1)-  When the server is started the scheduler will be started. It can
               be stopped and restarted by setting appropriate values to
               GLOBAL event_scheduler
      (OFF|0)- When the server is started, the scheduler won't be started. It
               can be started and again stopped by setting appropriate values to
               GLOBAL event_scheduler. _DEFAULT_ value
      
      The GLOBAL variable event_scheduler can have the following values:
      OFF | ON | 0 | 1
      DISABLED is not possible and every attempt will end with an error that
      it's not a valid value for the variable.
      OFF | 0 - This is the pre-5.1.11 behavior - The scheduler stops, if not
                already stopped, and can be started again  by setting
                the value of the variable to ON|1.
      ON | 1  - This is the pre-5.1.11 behavior - The scheduler starts, if not
                already started, and can be stopped again by setting the value
                of the variable to OFF|0.
      ca39997c
  9. 30 Aug, 2006 1 commit
    • aelkin/elkin@andrepl.dsl.inet.fi's avatar
      Changes made according to HLD/LLD. · 7be4bc4e
      aelkin/elkin@andrepl.dsl.inet.fi authored
         The following is an excerption from the WL.
            
         1. Change so that MIXED is default format
            1.1 to change the default for command line --binlog-format
            1.2 to alter global_system_variables.binlog_format calculation
                basing on command line --binlog-format parameter and 
                its default.
         2. Change test suite so that more testing is done by MIXED format.
            2.1 to check if there are test cases requiring --binlog-foramt=statement via
                `source include/have_binlog_format_statement.inc' and affected by 
                altering the latter to be "mixed".
            2.2 to check the content of such vulnerable cases to find if
                extending to the mixed does not modify results. In that case simply
                substitute source arguments as explained.
            2.3 if a test in mixed mode deals with features triggering
                row-binlogging then if necessary we can switch explicitly
                to statement mode or create another test to run with 
                non-recommended STATEMENT mode
         
                Particullarily, extracting INSERT DELAYED 
                binlogging subtest for statement mode is performed, and 
                the snippet is moved into a separate test file.
                Note that since now all three modes verify this use case
                through 3 different tests.
         
         No changes in item 3 of HLD appeared to be needed.
      7be4bc4e
  10. 29 Aug, 2006 1 commit
  11. 25 Aug, 2006 1 commit
    • brian@zim.(none)'s avatar
      Cleanup of unused variables. · baa914e6
      brian@zim.(none) authored
      Fixed "discover" in the handler API.
      
      Fixed problem where handlerton was not zero'ed. I need to look around, I suspect this problem is more widespread. 
      baa914e6
  12. 22 Aug, 2006 1 commit
    • brian@zim.(none)'s avatar
      This changest: · b5187637
      brian@zim.(none) authored
      Plugins now when compiled or not compiled work correctly with status variables. 
      Status variables from plugins now set their own names (removed bit where plugin name was pre-appended this broke Innodb and Cluster)
      A few Makefile cleanups. 
      b5187637
  13. 21 Aug, 2006 1 commit
  14. 20 Aug, 2006 1 commit
  15. 17 Aug, 2006 1 commit
  16. 11 Aug, 2006 2 commits
    • cmiller@zippy.cornsilk.net's avatar
      Bug#18875: Default value of tmp_table_size is meaningless · 6e2c8bac
      cmiller@zippy.cornsilk.net authored
      It makes no sense to have a default tmp_table_size larger than the 
      max_heap_table_size .  In usage, the tmp is ever limited to the max value, 
      so I lowered the default tmp to the default max value.
      
      A great idea would be to emit a warning when the tmp_table_size is set to 
      greater than max_heap_table_size .
      6e2c8bac
    • bar@mysql.com/bar.intranet.mysql.r18.ru's avatar
      mysqld --collation-server=xxx --character-set-server=yyy · 4a63a64f
      didn't work as expected: collation_server was set not to xxx,
      but to the default collation of character set "yyy".
          
      With different argument order it worked as expected:
      mysqld --character-set-server=yyy --collation-server=yyy 
          
      Fix:
      initializate default_collation_name to 0
      when processing --character-set-server
      only if --collation-server has not been specified
      in command line.
      4a63a64f
  17. 10 Aug, 2006 1 commit
  18. 04 Aug, 2006 1 commit
  19. 03 Aug, 2006 3 commits
    • iggy@rolltop.ignatz42.dyndns.org's avatar
    • msvensson@neptunus.(none)'s avatar
      Bug#21419 test case lowercase_fs_off fails on Windows · 5fc215e2
      msvensson@neptunus.(none) authored
       - Backport patch from 5.0
      5fc215e2
    • malff/marcsql@weblab.(none)'s avatar
      Bug#8153 (Stored procedure with subquery and continue handler, wrong result) · 21f00113
      malff/marcsql@weblab.(none) authored
      Before this fix,
      - a runtime error in a statement in a stored procedure with no error handlers
      was properly detected (as expected)
      - a runtime error in a statement with an error handler inherited from a non
      local runtime context (i.e., proc a with a handler, calling proc b) was
      properly detected (as expected)
      - a runtime error in a statement with a *local* error handler was executed
      as follows :
      a) the statement would succeed, regardless of the error condition, (bug)
      b) the error handler would be called (as expected).
      
      The root cause is that functions like my_messqge_sql would "forget" to set
      the thread flag thd->net.report_error to 1, because of the check involving
      sp_rcontext::found_handler_here().
      Failure to set this flag would cause, later in the call stack,
      in Item_func::fix_fields() at line 190, the code to return FALSE and consider
      that executing the statement was successful.
      
      With this fix :
      - error handling code, that was duplicated in different places in the code,
      is now implemented in sp_rcontext::handle_error(),
      - handle_error() correctly sets thd->net.report_error when a handler is
      present, regardless of the handler location (local, or in the call stack).
      
      A test case, bug8153_subselect, has been written to demonstrate the change
      of behavior before and after the fix.
      
      Another test case, bug8153_function_a, as also been writen.
      This test has the same behavior before and after the fix.
      This test has been written to demonstrate that the previous expected
      result of procedure bug18787, was incorrect, since select no_such_function()
      should fail and therefore not produce a result.
      
      The incorrect result for bug18787 has the same root cause as Bug#8153,
      and the expected result has been adjusted.
      21f00113
  20. 31 Jul, 2006 1 commit
  21. 29 Jul, 2006 1 commit
  22. 28 Jul, 2006 1 commit
  23. 21 Jul, 2006 1 commit
  24. 20 Jul, 2006 2 commits
  25. 14 Jul, 2006 1 commit
  26. 13 Jul, 2006 1 commit
  27. 04 Jul, 2006 1 commit
    • andrey@lmy004.'s avatar
      WL #3337 (Event scheduler new architecture) · 2bdd872e
      andrey@lmy004. authored
      Cut Nr. 8.
      
      All tests pass.
      
      Separated Event_scheduler into Event_queue and Event_scheduler.
      Added new Event_scheduler_ng which is the new scheduler and is used
      system-wide. Will be moved to the event_scheduler.cc in the future.
      Using Event_timed in Event_queue as well as cloned during execution.
      Next step is to have Event_worker_data which will be used during execution
      and will take ::compile()/::execute() out of Event_timed.
      2bdd872e
  28. 28 Jun, 2006 2 commits
  29. 27 Jun, 2006 1 commit
    • andrey@lmy004.'s avatar
      WL#3337 (Events new architecture) · 9309fae9
      andrey@lmy004. authored
      5th cut, moved DB related code to Event_db_repository and
      updated accordingly the remanining code.
      Moved change/restore_security_context() to class THD
      Removed events_priv.h
      Next step is to reorganize create/update_event() and parsing for them.
      But probably some other refactoring could be done in the meanwhile.
      The changes so far pass the test suite.
      9309fae9
  30. 23 Jun, 2006 1 commit
    • bar@mysql.com's avatar
      Bug#15276: MySQL ignores collation-server · ee8fd1e3
      bar@mysql.com authored
          Problem:
          mysqld --collation-server=xxx --character-set-server=yyy
          didn't work as expected: collation_server was set not to xxx,
          but to the default collation of character set "yyy".
          
          With different argument order it worked as expected:
          mysqld --character-set-server=yyy --collation-server=yyy 
          
          Fix:
          initializate default_collation_name to 0
          when processing --character-set-server
          only if --collation-server has not been specified
          in command line.
      ee8fd1e3
  31. 22 Jun, 2006 1 commit
  32. 21 Jun, 2006 2 commits