An error occurred fetching the project authors.
  1. 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
  2. 02 Sep, 2004 2 commits
  3. 31 Aug, 2004 1 commit
  4. 27 Aug, 2004 1 commit
  5. 26 Aug, 2004 1 commit
  6. 23 Aug, 2004 1 commit
  7. 10 Aug, 2004 1 commit
  8. 04 Aug, 2004 1 commit
  9. 29 Jul, 2004 1 commit
  10. 21 Jul, 2004 2 commits
  11. 15 Jul, 2004 1 commit
  12. 07 Jul, 2004 1 commit
  13. 29 Jun, 2004 1 commit
  14. 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
  15. 16 Jun, 2004 5 commits
  16. 21 May, 2004 1 commit
  17. 13 May, 2004 1 commit
  18. 11 May, 2004 2 commits
  19. 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
  20. 03 Apr, 2004 1 commit
  21. 02 Apr, 2004 1 commit
    • dlenev@jabberwock.localdomain's avatar
      WL#1266 "Separate auto-set logic from TIMESTAMP type." · f6bff2e6
      dlenev@jabberwock.localdomain authored
      Final version of patch.
      
      Adds support for specifying of DEFAULT NOW() and/or ON UPDATE NOW()
      clauses for TIMESTAMP field definition.
      Current implementation allows only one such field per table and
      uses several unireg types for storing info about this properties of
      field. It should be replaced with better implementation when new
      .frm format is introduced.
      f6bff2e6
  22. 29 Mar, 2004 2 commits
  23. 15 Mar, 2004 1 commit
  24. 13 Mar, 2004 1 commit
  25. 11 Mar, 2004 1 commit
  26. 07 Mar, 2004 1 commit
  27. 02 Mar, 2004 1 commit
  28. 29 Feb, 2004 1 commit
  29. 28 Feb, 2004 1 commit
  30. 22 Feb, 2004 1 commit
  31. 21 Feb, 2004 1 commit
    • guilhem@mysql.com's avatar
      Fix for BUG#2757 · 8bfb87ce
      guilhem@mysql.com authored
      "--read-only gives weird error on update".
      It is not fixable in 4.0 because it requires modifying
      the sql/share/*/errmsg.txt files. So it is fixed in 4.1 like this:
      the ER_SKIP_GRANT_TABLES is replaced by a more generic
      ER_OPTION_PREVENTS_STATEMENT which can be used both for
      "can't do this because of --skip-grant-tables" and
      "can't do this because of --read-only" (for this we don't use
      ER_CANT_UPDATE_WITH_READLOCK anymore).
      So now the message for --read-only is:
      "The MySQL server is running with the --read-only option so
      cannot execute this statement".
      8bfb87ce
  32. 15 Feb, 2004 1 commit