An error occurred fetching the project authors.
  1. 23 Aug, 2004 1 commit
  2. 04 Aug, 2004 1 commit
  3. 21 Jul, 2004 1 commit
  4. 07 Jul, 2004 1 commit
  5. 29 Jun, 2004 1 commit
  6. 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
  7. 16 Jun, 2004 2 commits
  8. 15 Jun, 2004 1 commit
  9. 21 May, 2004 1 commit
  10. 13 May, 2004 1 commit
  11. 11 May, 2004 1 commit
  12. 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
  13. 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
  14. 15 Mar, 2004 1 commit
  15. 13 Mar, 2004 1 commit
  16. 07 Mar, 2004 1 commit
  17. 02 Mar, 2004 1 commit
  18. 29 Feb, 2004 1 commit
  19. 28 Feb, 2004 1 commit
  20. 22 Feb, 2004 1 commit
  21. 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
  22. 15 Feb, 2004 1 commit
  23. 26 Jan, 2004 1 commit
  24. 23 Jan, 2004 1 commit
  25. 04 Jan, 2004 1 commit
  26. 23 Dec, 2003 1 commit
  27. 19 Dec, 2003 1 commit
    • monty@mysql.com's avatar
      Fixes after merge with 4.0 · 031390a9
      monty@mysql.com authored
      Cleaned up embedded library access and query cache handling
      Changed min stack size to 128K (to allow longer MyISAM keys)
      Fixed wrong priority for XOR (should be less than NEG to get -1^1 to work)
      031390a9
  28. 17 Dec, 2003 1 commit
  29. 16 Dec, 2003 1 commit
    • guilhem@mysql.com's avatar
      Fix for BUG#2121 "Inadequate message "check permissions on master.info"": · b6e55207
      guilhem@mysql.com authored
      more general message when slave can't start because of incorrect
      replication information, the previous one was sometimes a misleading
      indication (i.e. sometimes the problem had nothing to do with
      system permissions).
      The perfect fix would be to report the exact error to the client
      (instead of pointing the client to the error log); this is a bit
      of work so it's more a development task:
      WL#1088 "Move all hardcoded messages of replication to share/errmsg.txt".
      I was not able to modify the errmsg.txt in these sql/ subdirectories:
      
      danish
      dutch
      german
      italian
      portuguese
      russian
      spanish
      swedish
      ukrainian
      b6e55207
  30. 10 Dec, 2003 1 commit
  31. 08 Dec, 2003 1 commit
  32. 02 Dec, 2003 1 commit
  33. 26 Nov, 2003 1 commit
    • hf@deer.(none)'s avatar
      SCRUM · 611096a7
      hf@deer.(none) authored
      WL#1284 (warnings about --skip-name-resolve)
      Messages corrected
      611096a7
  34. 20 Nov, 2003 1 commit
    • hf@deer.(none)'s avatar
      SCRUM · 72566c79
      hf@deer.(none) authored
      WL#1284 (warnings about --skip-name-resolve)
      Now MySQL will issue warnings during startup about entries in
      grant tables with hostnames that require resolve, and after
      GRANT commands with that kind of hostnames.
      72566c79
  35. 18 Nov, 2003 3 commits
  36. 04 Nov, 2003 1 commit
  37. 03 Nov, 2003 1 commit
    • monty@narttu.mysql.fi's avatar
      Simplified 'wrong xxx name' error messages by introducing 'general' ER_WRONG_NAME error · a444a344
      monty@narttu.mysql.fi authored
      Cleaned up (and disabled part of) date/time/datetime format patch. One can't anymore change default read/write date/time/formats.
      This is becasue the non standard datetime formats can't be compared as strings and MySQL does still a lot of datetime comparisons as strings
      Changed flag argument to str_to_TIME() and get_date() from bool to uint
      Removed THD from str_to_xxxx functions and Item class.
      Fixed core dump when doing --print-defaults
      Move some common string functions to strfunc.cc
      Dates as strings are now of type my_charset_bin instead of default_charset()
      Introduce IDENT_QUOTED to not have to create an extra copy of simple identifiers (all chars < 128)
      Removed xxx_FORMAT_TYPE enums and replaced them with the old TIMESTAMP_xxx enums
      Renamed some TIMESTAMP_xxx enums to more appropriate names
      Use defines instead of integers for date/time/datetime string lengths
      Added to build system and use the new my_strtoll10() function.
      a444a344