An error occurred fetching the project authors.
  1. 22 Oct, 2004 2 commits
  2. 21 Oct, 2004 2 commits
  3. 10 Oct, 2004 2 commits
  4. 07 Oct, 2004 1 commit
  5. 06 Oct, 2004 1 commit
  6. 02 Oct, 2004 1 commit
    • monty@mishka.local's avatar
      More fixes for strict mode: · be4ca46f
      monty@mishka.local authored
      More tests.
      Better error messages.
      Fixed bug when checking if we updated all needed columns for INSERT.
      Give an error if we encounter a wrong float value during parsing.
      Don't print DEFAULT for columns without a default value in SHOW CREATE/SHOW FIELDS.
      Fixed UPDATE IGNORE when using STRICT mode.
      be4ca46f
  7. 29 Sep, 2004 1 commit
  8. 28 Sep, 2004 1 commit
    • monty@mishka.local's avatar
      Strict mode & better warnings · f2941380
      monty@mishka.local authored
      Under strict mode MySQL will generate an error message if there was any conversion when assigning data to a field.
      Added checking of date/datetime fields.
      If strict mode, give error if we have not given value to field without a default value (for INSERT)
      f2941380
  9. 17 Sep, 2004 1 commit
  10. 15 Sep, 2004 1 commit
    • monty@mishka.local's avatar
      Added options --auto-increment-increment and --auto-increment-offset. · 91ff64e1
      monty@mishka.local authored
      This allows one to setup a master <-> master replication with non conflicting auto-increment series.
      Cleaned up binary log code to make it easyer to add new state variables.
      Added simpler 'upper level' logic for artificial events (events that should not cause cleanups on slave).
      Simplified binary log handling.
      Changed how auto_increment works together with to SET INSERT_ID=# to make it more predictable: Now the inserted rows in a multi-row statement are set independent of the existing rows in the table. (Before only InnoDB did this correctly)
      
      91ff64e1
  11. 13 Sep, 2004 1 commit
  12. 11 Sep, 2004 1 commit
  13. 09 Sep, 2004 2 commits
    • bell@sanja.is.com.ua's avatar
      post merge fixes · a23857e0
      bell@sanja.is.com.ua authored
      a23857e0
    • monty@mysql.com's avatar
      After merge fixes of merge with 4.1 that included the new arena code. · f2829d03
      monty@mysql.com authored
      Fixed (together with Guilhem) bugs in mysqlbinlog regarding --offset
      Prefix addresses with 0x for easier comparisons of debug logs
      Fixed problem where MySQL choosed index-read even if there would be a much better range on the same index
      This fix changed some 'index' queries to 'range' queries in the test suite
      Don't create 'dummy' WHERE clause for trivial WHERE clauses where we can remove the WHERE clause.
      This fix removed of a lot of 'Using where' notes in the test suite.
      Give NOTE instead of WARNING if table/function doesn't exists when using DROP IF EXISTS
      Give NOTE instead of WARNING for safe field-type conversions
      f2829d03
  14. 08 Sep, 2004 1 commit
  15. 07 Sep, 2004 2 commits
    • bell@sanja.is.com.ua's avatar
    • 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
  16. 06 Sep, 2004 1 commit
  17. 04 Sep, 2004 1 commit
  18. 03 Sep, 2004 1 commit
  19. 01 Sep, 2004 1 commit
  20. 31 Aug, 2004 3 commits
  21. 27 Aug, 2004 1 commit
  22. 25 Aug, 2004 1 commit
  23. 24 Aug, 2004 2 commits
  24. 20 Aug, 2004 2 commits
    • konstantin@mysql.com's avatar
      Fix for bug#4912 "mysqld crashs in case a statement is executed · 568c6e85
      konstantin@mysql.com authored
       a second time". The bug was caused by incompatibility of
      negations elimination algorithm and PS: during first statement 
      execute a subtree with negation was replaced with equivalent 
      subtree without NOTs.
      The problem was that although this transformation was permanent, 
      items of the new subtree were created in execute-local memory.
      The patch adds means to check if it is the first execute of a
      prepared statement, and if this is the case, to allocate items
      in memory of the prepared statement.
      The implementation:
      - backports Item_arena from 5.0
      - adds Item_arena::is_stmt_prepare(), 
        Item_arena::is_first_stmt_execute().
      - deletes THD::allocate_temporary_pool_for_ps_preparing(),
        THD::free_temporary_pool_for_ps_preparing(); they
        were redundant.
      and adds a few invariants:
      - thd->free_list never contains junk (= freed items)
      - thd->current_arena is never null. If there is no
        prepared statement, it points at the thd. 
      The rest of the patch contains mainly mechanical changes and
      cleanups.
      568c6e85
    • guilhem@mysql.com's avatar
      Making FLUSH TABLES WITH READ LOCK block COMMITs of existing transactions, · 5db56a10
      guilhem@mysql.com authored
      in a deadlock-free manner. This splits locking the global read lock in two steps.
      This fixes a consequence of this bug, known as:
      BUG#4953 'mysqldump --master-data may report incorrect binlog position if using InnoDB'
      And a test.
      5db56a10
  25. 19 Aug, 2004 2 commits
  26. 18 Aug, 2004 1 commit
  27. 13 Aug, 2004 1 commit
    • bar@mysql.com's avatar
      CSC issue # 3299 fix: · 1c8b328e
      bar@mysql.com authored
      ENUM and SET type didn't compute their length correctly.
      That showed up for example while converting into a CHAR column.
      1c8b328e
  28. 10 Aug, 2004 1 commit
  29. 06 Aug, 2004 1 commit
  30. 03 Aug, 2004 1 commit