An error occurred fetching the project authors.
  1. 04 Oct, 2004 1 commit
  2. 01 Oct, 2004 1 commit
    • dlenev@brandersnatch.localdomain's avatar
      Support for TIMESTAMP columns holding NULL values. Unlike all other · 2511990c
      dlenev@brandersnatch.localdomain authored
      column types TIMESTAMP is NOT NULL by default, so in order to have 
      TIMESTAMP column holding NULL valaues you have to specify NULL as
      one of its attributes (this needed for backward compatibility).
      
      Main changes:
      Replaced TABLE::timestamp_default_now/on_update_now members with
      TABLE::timestamp_auto_set_type flag which is used everywhere
      for determining if we should auto-set value of TIMESTAMP field 
      during this operation or not. We are also use Field_timestamp::set_time()
      instead of handler::update_timestamp() in handlers.
      2511990c
  3. 16 Sep, 2004 1 commit
  4. 13 Sep, 2004 1 commit
  5. 10 Sep, 2004 1 commit
  6. 08 Sep, 2004 1 commit
  7. 04 Sep, 2004 1 commit
  8. 31 Aug, 2004 1 commit
  9. 27 Aug, 2004 1 commit
  10. 25 Aug, 2004 1 commit
  11. 24 Aug, 2004 1 commit
    • konstantin@mysql.com's avatar
      Fix for Bug#5034 "prepared "select 1 into @arg15", second · ae18dc3e
      konstantin@mysql.com authored
      execute crashes server": we were deleting lex->result
      after each execute, but prepared statements assumed that
      it's left intact.
      The fix adds cleanup() method to select_result hierarchy,
      so that result objects can be reused.
      Plus we now need to delete result objects more wisely.
      ae18dc3e
  12. 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
  13. 19 Aug, 2004 2 commits
  14. 18 Aug, 2004 1 commit
  15. 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
  16. 10 Aug, 2004 1 commit
  17. 06 Aug, 2004 1 commit
  18. 21 Jul, 2004 1 commit
  19. 12 Jul, 2004 1 commit
  20. 09 Jul, 2004 1 commit
  21. 08 Jul, 2004 1 commit
  22. 26 Jun, 2004 1 commit
  23. 24 Jun, 2004 1 commit
  24. 23 Jun, 2004 1 commit
  25. 21 Jun, 2004 1 commit
  26. 18 Jun, 2004 2 commits
    • guilhem@mysql.com's avatar
      API change: mysql_shutdown() now requires a 2nd argument, the shutdown level. · 19dbf58e
      guilhem@mysql.com authored
      mysqld >=4.1.3 will however understand shutdown requests sent by clients <4.1.3.
      And mysqld <4.1.3 will understand shutdown requests sent by clients >=4.1.3
      (it will ignore the level). Those shutdown level are just PLACEHOLDERS now.
      So this change is just to make the 4.1 API suitable before it is frozen. Later
      we will actually implement the shutdown levels.
      19dbf58e
    • 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. 17 Jun, 2004 2 commits
  28. 15 Jun, 2004 1 commit
    • guilhem@mysql.com's avatar
      API change: mysql_shutdown() now needs a 2nd parameter, the shutdown level. · f1fda638
      guilhem@mysql.com authored
      Server will however still accept shutdown without specified level; so that old
      mysqladmin can still shut server down.
      I would like your comments on the names of shutdown level which I chose. You
      are welcome to propose better names. Please however check WL#709 before.
      Reason for the names I propose is to be accurate, thus leaving possibility
      for other levels which we may imagine in the future; that's why I have rejected
      names like "fast", "smart", "graceful" so far. My position is that WAIT_ALL_BUFFERS
      or WAIT_CRITICAL_BUFFERS say what the shutdown does, whereas for "smart", "fast" you
      need to remember what it does.
      This should be pushed in 4.1.3 but only after your comments.
      f1fda638
  29. 13 Jun, 2004 1 commit
  30. 10 Jun, 2004 3 commits
  31. 09 Jun, 2004 2 commits
  32. 08 Jun, 2004 1 commit
  33. 07 Jun, 2004 1 commit