An error occurred fetching the project authors.
  1. 31 Aug, 2004 1 commit
  2. 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
    • dlenev@brandersnatch.localdomain's avatar
      Fix for bug#4302 "ambiguos order by when renamed column is identical to another in result" · c8882165
      dlenev@brandersnatch.localdomain authored
      When in find_item_in_list() we are looking for item we should take into account unaliased 
      names of the fields but only if item with such aliased name is not found.
      Also we should ignore aliases when looking for fully specified field.
      c8882165
  3. 10 Aug, 2004 1 commit
  4. 02 Aug, 2004 1 commit
  5. 30 Jul, 2004 1 commit
  6. 24 Jun, 2004 1 commit
  7. 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
  8. 10 Jun, 2004 1 commit
  9. 29 May, 2004 1 commit
  10. 17 May, 2004 1 commit
  11. 14 May, 2004 1 commit
  12. 05 May, 2004 1 commit
  13. 04 May, 2004 1 commit
  14. 15 Apr, 2004 1 commit
  15. 07 Apr, 2004 1 commit
  16. 06 Apr, 2004 2 commits
  17. 04 Apr, 2004 1 commit
  18. 03 Apr, 2004 2 commits
  19. 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
  20. 01 Apr, 2004 1 commit
  21. 31 Mar, 2004 3 commits
  22. 30 Mar, 2004 2 commits
    • ingo@mysql.com's avatar
      Worklog#1563 - Support of on-line CREATE/DROP INDEX. · 85ec87a0
      ingo@mysql.com authored
      This is to enable table handlers to implement online create/drop index.
      It consists of some parts:
      - New default handler methods in handler.h
      - Split of mysql_alter_table. It decides if only one kind of
        alteration is to be done (e.g. only create indexes or only drop
        indexes etc.) It then calls the specialized new handler method if
        the handler implements it. Otherwise it calls real_alter_table.
      - The parser sets flags for each alter operation detected in a
        command. These are used by mysql_alter_table for the decision.
      - mysql_prepare_table is pulled out of mysql_create_table. This is
        also used by mysql_create_index to prepare the key structure array
        for the handler. It is also used by mysql_create_index and
        mysql_drop_index to prepare a call to mysql_create_frm.
      - mysql_create_frm is pulled out of rea_create_table for use by
        mysql_create_index and mysql_drop_index after the index is
        created/dropped.
      Thanks to Antony who supplied most of the changes.
      85ec87a0
    • ram@gw.mysql.r18.ru's avatar
      An improvement of · fffe1e84
      ram@gw.mysql.r18.ru authored
      ChangeSet
        1.1707 04/03/19 12:36:55 ram@gw.mysql.r18.ru +4 -0
        Fix for the bug #2976: NATURAL JOIN produces duplicate columns.
      fffe1e84
  23. 29 Mar, 2004 1 commit
  24. 28 Mar, 2004 1 commit
    • dlenev@brandersnatch.localdomain's avatar
      "Fix" for BUG #2050 "10 to 1 performance drop with server 4.1.1". · 9e28b769
      dlenev@brandersnatch.localdomain authored
      Actually it is not a bug but right behavior observed as pefomance 
      degradation after we have forced Item_field::fix_fields() to 
      re-execute each time when we are executing prep stmt.
      
      This patch implements small optimization which heals this bad 
      behavior. We are caching field position in TABLE::field array in
      Item's member and are using this position for speeding up field
      lookups in fix_fields() in case of its re-execution.
      9e28b769
  25. 26 Mar, 2004 1 commit
  26. 25 Mar, 2004 1 commit
  27. 24 Mar, 2004 1 commit
  28. 20 Mar, 2004 2 commits
    • guilhem@mysql.com's avatar
      The automatic DROP TEMPORARY TABLE is now DROP TEMPORARY TABLE IF EXISTS, · d89f148d
      guilhem@mysql.com authored
      this is better in this case:
      - imagine user1 has created a temp table
      - imagine user2 does FLUSH TABLES WITH READ LOCK, then takes a backup,
      then RESET MASTER then UNLOCK TABLES, like mysqldump --first-slave
      - then in the binlog you will finally have the DROP TEMPORARY TABLE,
      but not the CREATE TEMPORARY TABLE, so when you later restore with
      mysqlbinlog|mysql, mysql will complain that table does not exist.
      Replication was already protected of this (it processes DROP TEMPORARY
      TABLE as if there was a IF EXISTS), now I add it directly to the query
      for mysqlbinlog|mysql to work.
      d89f148d
    • bell@sanja.is.com.ua's avatar
      after review changes · d095d475
      bell@sanja.is.com.ua authored
      d095d475
  29. 19 Mar, 2004 1 commit
  30. 18 Mar, 2004 1 commit
  31. 17 Mar, 2004 3 commits