An error occurred fetching the project authors.
  1. 03 May, 2006 2 commits
  2. 18 Apr, 2006 1 commit
    • pem@mysql.com's avatar
      Fixed BUG#18949: Test case sp-goto is disabled · a6fbde9d
      pem@mysql.com authored
        Removed sp-goto.test, sp-goto.result and all (disabled) GOTO code.
        Also removed some related code that's not needed any more (no possible
        unresolved label references any more, so no need to check for them).
        NB: Keeping the ER_SP_GOTO_IN_HNDLR in errmsg.txt; it might become useful
            in the future, and removing it (and thus re-enumerating error codes)
            might upset things. (Anything referring to explicit error codes.)
      a6fbde9d
  3. 10 Apr, 2006 1 commit
  4. 06 Apr, 2006 1 commit
  5. 20 Mar, 2006 1 commit
  6. 17 Feb, 2006 1 commit
  7. 12 Feb, 2006 1 commit
  8. 24 Jan, 2006 1 commit
  9. 17 Jan, 2006 1 commit
  10. 11 Jan, 2006 1 commit
  11. 28 Dec, 2005 1 commit
  12. 21 Dec, 2005 1 commit
    • bar@mysql.com's avatar
      Adding XPath support: ExtractValue and UpdateXML functions. · 519f9d62
      bar@mysql.com authored
      libmysqld/Makefile.am:
      sql/Makefile.am:
        Adding new source files.
        Adding new file into build process.
      include/my_xml.h:
      strings/xml.c:
        Adding new XML parse flags to skip text normalization and 
        to use relative tag names. Adding enum for XML token types.
      sql/lex.h:
        Making parser aware of new SQL functions.
      sqll/item_create.h, sql/item_create.cc:
        Adding creators for ExtractValue and UpdateXML.
      sql/item.h:
        Adding new Item types: nodeset and nodeset comparator.
      sql/item_xmlfunc.h
      sql/item_xmlfunc.cc
        Adding new classes implementing XPath functions.
      mysql-test/t/xml.test, mysql-test/r/xml.result:
        New files: adding test case
      519f9d62
  13. 02 Dec, 2005 1 commit
  14. 17 Nov, 2005 1 commit
    • pem@mysql.com's avatar
      Background: · c518a240
      pem@mysql.com authored
      Since long, the compiled code of stored routines has been printed in the trace file
      when starting mysqld with the "--debug" flag. (At creation time only, and only in
      debug builds of course.) This has been helpful when debugging stored procedure
      execution, but it's a bit awkward to use. Also, the printing of some of the
      instructions is a bit terse, in particular for sp_instr_stmt where only the command
      code was printed.
      
      This improves the printout of several of the instructions, and adds the debugging-
      only commands "show procedure code <name>" and "show function code <name>".
      (In non-debug builds they are not available.)
      c518a240
  15. 10 Nov, 2005 1 commit
  16. 07 Nov, 2005 1 commit
  17. 06 Nov, 2005 1 commit
  18. 25 Aug, 2005 1 commit
  19. 24 Aug, 2005 1 commit
  20. 19 Aug, 2005 1 commit
  21. 12 Aug, 2005 1 commit
  22. 19 Jul, 2005 1 commit
  23. 18 Jul, 2005 1 commit
  24. 01 Jul, 2005 1 commit
  25. 25 Feb, 2005 1 commit
  26. 01 Feb, 2005 1 commit
  27. 16 Jan, 2005 1 commit
  28. 07 Jan, 2005 1 commit
  29. 29 Dec, 2004 1 commit
  30. 24 Dec, 2004 2 commits
    • vtkachenko@intelp4d.mysql.com's avatar
      Many files: · f1dfafe7
      vtkachenko@intelp4d.mysql.com authored
        tabs replaced
      ha_innodb.cc:
        Comments removed
      f1dfafe7
    • vtkachenko@intelp4d.mysql.com's avatar
      logging_ok: · 78846b29
      vtkachenko@intelp4d.mysql.com authored
        Logging to logging@openlogging.org accepted
      sql_yacc.yy, sql_parse.cc, sql_lex.h, lex.h:
        Implements the SHOW MUTEX STATUS command
      set_var.cc, mysqld.cc, mysql_priv.h:
        Added new GLOBAL variable timed_mutexes
      ha_innodb.h:
        New function innodb_mutex_show_status
      ha_innodb.cc:
        Added new innodb variables in SHOW STATUS
        Implements the SHOW MUTEX STATUS command
      innodb.test, innodb.result:
        Added new row_lock_waits status variables tests.
      variables.test, variables.result:
        test new variable timed_mutexes
      ut0ut.c:
        New function ut_usectime.
      sync0sync.c:
        Mutex counting.
      sync0rw.c:
        New mutex parameters initialization.
      srv0srv.c:
        Counting row lock waits
      row0sel.c, row0mysql.c:
        Setting row_lock or table_lock state to thd.
      que0que.c:
        Added default no_lock_state to thd.
      univ.i:
        Added UNIV_SRV_PRINT_LATCH_WAITS debug define
      sync0sync.ic:
        Count mutex using.
      sync0sync.h:
        Added new parameters to mutex structure for counting.
      sync0rw.h:
        Added new parameters to rw_create_func.
      srv0srv.h:
        Added new innodb varuables to SHOW STATUS.
      que0que.h:
        Added thread lock states.
      78846b29
  31. 23 Dec, 2004 1 commit
  32. 17 Nov, 2004 1 commit
  33. 12 Nov, 2004 1 commit
  34. 10 Nov, 2004 1 commit
    • guilhem@mysql.com's avatar
      WL#1596 "make mysqldump --master-data --single-transaction able to do online... · 6cd218cc
      guilhem@mysql.com authored
      WL#1596 "make mysqldump --master-data --single-transaction able to do online dump of InnoDB AND report reliable
      binlog coordinates corresponding to the dump".
      The good news is that now mysqldump can be used to get an online backup of InnoDB *which works for
      point-in-time recovery and replication slave creation*. Formerly, mysqldump --master-data --single-transaction
      used to call in fact mysqldump --master-data, so the dump was not an online dump (took big lock all time of dump).
      The only lock which is now taken in this patch is at the beginning of the dump: mysqldump does:
      FLUSH TABLES WITH READ LOCK; START TRANSACTION WITH CONSISTENT SNAPSHOT; SHOW MASTER STATUS; UNLOCK TABLES;
      so the lock time is in fact the time FLUSH TABLES WITH READ LOCK takes to return (can be 0 or very long, if
      a table is undergoing a huge update).
      I have done some more minor changes listed in the paragraph of mysqldump.c.
      WL#2237 "WITH CONSISTENT SNAPSHOT clause for START TRANSACTION":
      it's a START TRANSACTION which additionally starts a consistent read on all
      capable storage engine (i.e. InnoDB). So, can serve as a replacement for
      BEGIN; SELECT * FROM some_innodb_table LIMIT 1; which starts a consistent read too. 
      6cd218cc
  35. 14 Oct, 2004 1 commit
  36. 07 Oct, 2004 1 commit
  37. 01 Oct, 2004 1 commit
  38. 07 Sep, 2004 1 commit
    • dlenev@brandersnatch.localdomain's avatar
      WL#1218 "Triggers". Some very preliminary version of patch. · 9ed038dd
      dlenev@brandersnatch.localdomain authored
      Mostly needed for Monty for him getting notion what needed for triggers 
      from new .FRM format. 
      
      Things to be done:
      - Right placement of trigger's invocations
      - Right handling of errors in triggers (including transaction rollback)
      - Support for priviliges
      - Right handling of DROP/RENAME table (hope that it will be handled automatically
        with merging of .TRG into .FRM file)
      - Saving/restoring some information critical for trigger creation and replication
        with their definitions (e.g. sql_mode, creator, ...)
      - Replication
      
      Already has some known bugs so probably not for general review.
      9ed038dd