An error occurred fetching the project authors.
  1. 25 Nov, 2004 1 commit
  2. 21 Nov, 2004 1 commit
  3. 13 Nov, 2004 1 commit
  4. 12 Nov, 2004 1 commit
  5. 10 Nov, 2004 2 commits
    • guilhem@mysql.com's avatar
      no new message in 4.1 (causes merge issues with 5.0). Using ER_UNKNOW_ERROR... · 09da8533
      guilhem@mysql.com authored
      no new message in 4.1 (causes merge issues with 5.0). Using ER_UNKNOW_ERROR and hardcoded message string instead.
      09da8533
    • 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
  6. 22 Oct, 2004 1 commit
  7. 20 Oct, 2004 1 commit
  8. 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
  9. 29 Sep, 2004 1 commit
  10. 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
  11. 15 Sep, 2004 1 commit
  12. 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
  13. 03 Sep, 2004 1 commit
  14. 02 Sep, 2004 2 commits
  15. 31 Aug, 2004 1 commit
  16. 27 Aug, 2004 1 commit
  17. 26 Aug, 2004 1 commit
  18. 23 Aug, 2004 1 commit
  19. 10 Aug, 2004 1 commit
  20. 04 Aug, 2004 1 commit
  21. 29 Jul, 2004 1 commit
  22. 21 Jul, 2004 2 commits
  23. 15 Jul, 2004 1 commit
  24. 07 Jul, 2004 1 commit
  25. 29 Jun, 2004 1 commit
  26. 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
  27. 16 Jun, 2004 5 commits
  28. 15 Jun, 2004 1 commit
  29. 21 May, 2004 1 commit
  30. 13 May, 2004 1 commit
  31. 11 May, 2004 2 commits
  32. 07 Apr, 2004 1 commit
    • bell@sanja.is.com.ua's avatar
      new error for unsupported command in PS · 5e37c41f
      bell@sanja.is.com.ua authored
      fixed IN subselect with basic constant left expression
      SQLCOM_CREATE_TABLE, SQLCOM_UPDATE_MULTI, SQLCOM_REPLACE_SELECT, SQLCOM_INSERT_SELECT, QLCOM_DELETE_MULTI fixed to be compatible with PS (BUG#3398, BUG#3406)
      fixed multiupdate privelege check (BUG#3408)
      fixed multiupdate tables check (BUG#3411)
      unchecked commands now is rejected by PS protocol to avoid serever crash
      fixed cleunup procedure to be compatible sith DO/SET (BUG#3393)
      5e37c41f