An error occurred fetching the project authors.
  1. 19 Jul, 2005 1 commit
  2. 01 Jul, 2005 1 commit
  3. 25 Feb, 2005 1 commit
  4. 01 Feb, 2005 1 commit
  5. 16 Jan, 2005 1 commit
  6. 07 Jan, 2005 1 commit
  7. 29 Dec, 2004 1 commit
  8. 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
  9. 23 Dec, 2004 1 commit
  10. 17 Nov, 2004 1 commit
  11. 12 Nov, 2004 1 commit
  12. 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
  13. 14 Oct, 2004 1 commit
  14. 07 Oct, 2004 1 commit
  15. 01 Oct, 2004 1 commit
  16. 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
  17. 17 Aug, 2004 1 commit
  18. 10 Aug, 2004 1 commit
  19. 15 Jul, 2004 1 commit
  20. 23 Jun, 2004 1 commit
    • serg@serg.mylan's avatar
      handler interface cleanups: · 3f1c4ba7
      serg@serg.mylan authored
        more logical table/index_flags
        return  HA_ERR_WRONG_COMMAND instead of abstract methods where appropriate
        max_keys and other limits renamed to max_supported_keys/etc
        max_keys/etc are now wrappers to max_supported_keys/etc 
        ha_index_init/ha_rnd_init/ha_index_end/ha_rnd_end are now wrappers to real {index,rnd}_{init,end} to enforce strict pairing
      3f1c4ba7
  21. 18 Jun, 2004 1 commit
    • dlenev@brandersnatch.localdomain's avatar
      WL#1264 "Per-thread time zone support infrastructure". · 09ba29e5
      dlenev@brandersnatch.localdomain authored
      Added basic per-thread time zone functionality (based on public
      domain elsie-code). Now user can select current time zone
      (from the list of time zones described in system tables).
      All NOW-like functions honor this time zone, values of TIMESTAMP
      type are interpreted as values in this time zone, so now
      our TIMESTAMP type behaves similar to Oracle's TIMESTAMP WITH
      LOCAL TIME ZONE (or proper PostgresSQL type).
        
      WL#1266 "CONVERT_TZ() - basic time with time zone conversion 
      function".
        
      Fixed problems described in Bug #2336 (Different number of warnings 
      when inserting bad datetime as string or as number). This required
      reworking of datetime realted warning hadling (they now generated 
      at Field object level not in conversion functions).
        
      Optimization: Now Field class descendants use table->in_use member
      instead of current_thd macro.
      09ba29e5
  22. 03 Jun, 2004 1 commit
    • guilhem@mysql.com's avatar
      Implementation of WL#1824 "Add replication of character set variables in 4.1", · 86e8ecc9
      guilhem@mysql.com authored
      by binlogging some SET ONE_SHOT CHARACTER_SETetc,
      which will be enough until we have it more compact and more complete in 5.0. With the present patch,
      replication will work ok between 4.1.3 master and slaves, as long as:
      - master and slave have the same GLOBAL.COLLATION_SERVER
      - COLLATION_DATABASE and CHARACTER_SET_DATABASE are not used
      - application does not use the fact that table is created with charset of the USEd db (BUG#2326).
      all of which are not too hard to fulfill. 
      ONE_SHOT is reserved for internal use of mysqlbinlog|mysql and works only for charsets,
      so we give error if used for non-charset vars.
      Fix for BUG#3875 "mysqlbinlog produces wrong ouput  if query uses
       variables containing quotes" and BUG#3943 "Queries with non-ASCII literals are not replicated
       properly after SET NAMES".
      Detecting that master and slave have different global charsets or server ids.
      86e8ecc9
  23. 04 May, 2004 1 commit
  24. 15 Apr, 2004 1 commit
  25. 05 Apr, 2004 2 commits
    • sergefp@mysql.com's avatar
      Many files: · a8386d01
      sergefp@mysql.com authored
        SQL Syntax for Prepared Statements (WL#1622)
      ps.test, ps.result:
        new file
      a8386d01
    • gluh@gluh.mysql.r18.ru's avatar
      WL1368: SHOW GRANTS FOR CURRENT USER · 8a4e6c64
      gluh@gluh.mysql.r18.ru authored
        'SHOW GRANTS' syntax is added 
        'SHOW GRANTS FOR CURRENT_USER' syntax is added
        'SHOW GRANTS FOR CURRENT_USER()' syntax is added
       CURRENT_USER without parens in expressions(SELECT CURRENT_USER;) 
      8a4e6c64
  26. 30 Mar, 2004 1 commit
  27. 04 Mar, 2004 1 commit
  28. 27 Feb, 2004 1 commit
  29. 11 Feb, 2004 1 commit
  30. 23 Jan, 2004 2 commits
  31. 15 Jan, 2004 1 commit
    • hf@deer.(none)'s avatar
      SCRUM: · 6dcda515
      hf@deer.(none) authored
      WL#1163 (Making spatial code optional)
      Pack of changes to do in sql/ code.
      6dcda515
  32. 17 Dec, 2003 1 commit
  33. 16 Dec, 2003 2 commits
  34. 10 Dec, 2003 2 commits
  35. 08 Dec, 2003 1 commit
    • gluh@gluh.mysql.r18.ru's avatar
      WL#530&531: TIMESTAMPADD, TIMESTAMPDIFF functions · ec874924
      gluh@gluh.mysql.r18.ru authored
      Syntax for TIMESTAMPADD:
      
      TIMESTAMPADD(interval, integer_expression, datetime_expression)
      
      interval:= FRAC_SECOND | SECOND | MINUTE | HOUR | DAY | WEEK | MONTH | 
      QUARTER | YEAR
      
      Supported SQL_TSI_  prefix  (like SQL_TSI_SECOND)
      
      Syntax for TIMESTAMPDIFF:
      
      TIMESTAMPDIFF(interval, datetime_expression1, datetime_expression2)
      
      interval:= FRAC_SECOND | SECOND | MINUTE | HOUR | DAY | WEEK | MONTH | 
      QUARTER | YEAR
      
      Supported SQL_TSI_  prefix  (like SQL_TSI_SECOND)
      ec874924