1. 19 Oct, 2004 3 commits
  2. 18 Oct, 2004 9 commits
    • unknown's avatar
    • unknown's avatar
      srv0srv.c: · 2eda6618
      unknown authored
        If innodb_thread_concurrency would be exceeded, let a thread sleep 10 ms before entering the FIFO queue; previously, the value was 50 ms, which Peter Z considered too long
      
      
      innobase/srv/srv0srv.c:
        If innodb_thread_concurrency would be exceeded, let a thread sleep 10 ms before entering the FIFO queue; previously, the value was 50 ms, which Peter Z considered too long
      2eda6618
    • unknown's avatar
      CHARSET_INFO.txt: · 8dee7c7e
      unknown authored
        new file
      
      8dee7c7e
    • unknown's avatar
    • unknown's avatar
      Merge rkalimullin@bk-internal.mysql.com:/home/bk/mysql-4.1 · fce9ea55
      unknown authored
      into gw.mysql.r18.ru:/usr/home/ram/work/4.1.b6057
      
      fce9ea55
    • unknown's avatar
      ctype-mb.c: · 5580c3bb
      unknown authored
        Remove unnesessary code: use_mb is always TRUE for the multibyte charsets.
      
      
      strings/ctype-mb.c:
        Remove unnesessary code: use_mb is always TRUE for the multibyte charsets.
      5580c3bb
    • unknown's avatar
      Merge rkalimullin@bk-internal.mysql.com:/home/bk/mysql-4.1 · 8c7ef779
      unknown authored
      into gw.mysql.r18.ru:/usr/home/ram/work/4.1.b6057
      
      8c7ef779
    • unknown's avatar
      A fix (bug #6057: Data Type Problem in manager.c). · ce6cec90
      unknown authored
      
      libmysql/manager.c:
        Code clean-up: as my_net_read() returns ulong value we should use ulong here.
      ce6cec90
    • unknown's avatar
      Fix for broken --with-csv-storage-engine build. · 1a1298e4
      unknown authored
      Now we use TABLE::timestamp_field_type instead of
      TABLE::timestamp_default_now/on_update_now for determining
      if we should auto-set value of TIMESTAMP field during this operation.
      We are also use Field_timestamp::set_time() instead of
      handler::update_timestamp().
      
      
      sql/examples/ha_example.cc:
        Now we use TABLE::timestamp_field_type instead of
        TABLE::timestamp_default_now/on_update_now for determining
        if we should auto-set value of TIMESTAMP field during this operation.
        We are also use Field_timestamp::set_time() instead of
        handler::update_timestamp().
      sql/examples/ha_tina.cc:
        Now we use TABLE::timestamp_field_type instead of
        TABLE::timestamp_default_now/on_update_now for determining
        if we should auto-set value of TIMESTAMP field during this operation.
        We are also use Field_timestamp::set_time() instead of
        handler::update_timestamp().
      1a1298e4
  3. 16 Oct, 2004 1 commit
  4. 15 Oct, 2004 7 commits
  5. 14 Oct, 2004 17 commits
  6. 13 Oct, 2004 3 commits
    • unknown's avatar
      e82bcce7
    • unknown's avatar
      Merge bk-internal.mysql.com:/home/bk/mysql-4.1 · c45f9d12
      unknown authored
      into mysql.com:/media/sda1/mysql/mysql-4.1-5985
      
      
      sql/sql_class.h:
        Auto merged
      c45f9d12
    • unknown's avatar
      A fix and test case for Bug#5985 ""prepare stmt from "select rand(?)" · e7a0d543
      unknown authored
      crashes server." The fix makes Item_func_rand prepared-statements
      aware plus it fixes the case when RAND is used in prepared
      statements and replication is on (as well as several similar issues).
      Until now we did not reset THD before every execution of a prepared
      statement, so if some execution had set thd->time_zone_used
      or thd->rand_used they would not be reset until next mysql_parse.
      Some of post-review fixes done.
      
      
      mysql-test/r/ps.result:
        A test case for Bug#5985: test results fixed.
      mysql-test/t/ps.test:
        A test case for Bug#5985 "prepare stmt from "select rand(?)" crashes
        server."
      sql/item_func.cc:
        Actual fix for Bug#5985: Item_func_rand rewritten to be 
        prepared statements aware.
      sql/item_func.h:
        Actual fix for Bug#5985: Item_func_rand rewritten to be 
        prepared statements aware.
      sql/mysql_priv.h:
        We need a separate call to reset THD state before every execute of
        a prepared statement. Otherwise things like THD->user_var_events
        are never cleaned up and bloat binary log (as the list of events
        grows from execution to execution).
      sql/sql_class.cc:
        Statement::end_statement -> THD::end_statement()
        (a leftover from some design change which is not to pushed now, but the
        leftover is to be pushed).
      sql/sql_class.h:
        Statement::end_statement -> THD::end_statement()
        (a leftover from some design change which is not to pushed now, but the
        leftover is to be pushed).
      sql/sql_lex.cc:
        Move the part responsible for initializing LEX from mysql_init_query
        to lex_start.
      sql/sql_lex.h:
        All lex-related initialization is now in lex_start.
        Move thd->select_number to lex->select_number to be able to use it
        easily in lex_start.
      sql/sql_parse.cc:
        Split mysql_init_query into two functions: mysql_reset_thd_for_next_query,
        which is used in PS and conventional execution, and lex_start, used only
        when we want to parse something.
        Fix init_connect to use initialized THD.
      sql/sql_prepare.cc:
        Deploy mysql_reset_thd_for_next_query to reset THD state before
        execution of a prepared statement.
        Normally this should have been added to just one place, but
        we have to reset thd before assigning placeholders from variables,
        thus we can't do that in execute_stmt (yuck).
      e7a0d543