1. 23 Mar, 2006 8 commits
  2. 22 Mar, 2006 7 commits
  3. 21 Mar, 2006 6 commits
  4. 20 Mar, 2006 6 commits
    • unknown's avatar
      Merge neptunus.(none):/home/msvensson/mysql/mysql-5.0 · 6219f23b
      unknown authored
      into  neptunus.(none):/home/msvensson/mysql/bug11835/my50-bug11835
      
      
      client/mysqltest.c:
        Auto merged
      configure.in:
        Auto merged
      mysql-test/mysql-test-run.pl:
        Auto merged
      sql/item_func.cc:
        Auto merged
      sql/sql_udf.cc:
        Auto merged
      6219f23b
    • unknown's avatar
      Don't look for "dlopen" if server linked with -static or -all-static flag. Update after review · 680ba0b7
      unknown authored
      
      configure.in:
        Don't look for "dlopen" if server linked with -static or -all-static flag
      680ba0b7
    • unknown's avatar
      Bug#17374: select ... like 'A%' operator fails to find value on columuns with key · 83bc8c4e
      unknown authored
      Fixed that LIKE worked case insensitively for latin2_czech_cs,
      which was wrong for a case sensitive collation.
      
      
      include/m_ctype.h:
        Making my_wildcmp_bin public instead of static
      strings/ctype-bin.c:
        Making my_wildcmp_bin public instead of static
      strings/ctype-czech.c:
        Use my_wildcmp_bin instead of case insensitive my_wildcmp_8bit
      mysql-test/include/have_latin2_ch.inc:
        New BitKeeper file ``mysql-test/include/have_latin2_ch.inc''
      mysql-test/r/ctype_latin2_ch.result:
        New BitKeeper file ``mysql-test/r/ctype_latin2_ch.result''
      mysql-test/r/have_latin2_ch.require:
        New BitKeeper file ``mysql-test/r/have_latin2_ch.require''
      mysql-test/t/ctype_latin2_ch.test:
        New BitKeeper file ``mysql-test/t/ctype_latin2_ch.test''
      83bc8c4e
    • unknown's avatar
      Bug#18004 Connecting crashes server when default charset is UCS2 · 7913527e
      unknown authored
      table.cc:
        Fixing to use system_charset_info instead of default_charset_info.
        Crash happened because the "ctype" array is empty in UCS2,
        and thus cannot be used with my_isspace().
        The reason why UCS2 appeared in this context was because of
        of default_charset_info variable incorrectly substituted to my_isspace().
        As functions check_db_name(), check_table_name() and check_column_name()
        always get values in utf8, system_charset_info must be used instead.
      ctype_ucs2_def.test, ctype_ucs2_def-master.opt, ctype_ucs2_def.result:
        new file
      
      
      sql/table.cc:
        Bug#18004 Connecting crashes server when default charset is UCS2
        Use of default_charset_info was wrong.
        Functions check_db_name, check_table_name and check_column_name
        get values of system_charset_info character set (utf8).
      7913527e
    • unknown's avatar
      Fix for bug#18224 VIEW on information_schema crashes the server · 53862e60
      unknown authored
        additional check for subselect
      
      
      mysql-test/r/information_schema.result:
        Fix for bug#18224 VIEW on information_schema crashes the server
          test case
      mysql-test/t/information_schema.test:
        Fix for bug#18224 VIEW on information_schema crashes the server
          test case
      53862e60
    • unknown's avatar
      Fix for bug #18113 "SELECT * FROM information_schema.xxx crashes server" · ce39d294
      unknown authored
      Crash happened when one selected data from one of INFORMATION_SCHEMA
      tables and in order to build its contents server had to open view which
      used stored function and table or view on which one had not global or
      database-level privileges (e.g. had only table-level or had no
      privileges at all).
      
      The crash was caused by usage of check_grant() function, which assumes
      that either number of tables to be inspected by it is limited explicitly
      or table list used and thd->lex->query_tables_own_last value correspond
      to each other (the latter should be either 0 or point to next_global
      member of one of elements of this table list), in conditions when
      above assumptions were not true. This fix just explicitly limits
      number of tables to be inspected. Other negative effects which are
      caused by the fact that thd->lex->query_tables_own_last might not
      be set properly during processing of I_S tables are less disastrous
      and will be reported and fixed separetely.
      
      
      
      mysql-test/r/information_schema_db.result:
        Fix for bug #18113 "SELECT * FROM information_schema.xxx crashes server"
          test case
      mysql-test/t/information_schema_db.test:
        Fix for bug #18113 "SELECT * FROM information_schema.xxx crashes server"
          test case
      sql/sql_acl.cc:
          added note
      ce39d294
  5. 18 Mar, 2006 1 commit
    • unknown's avatar
      Merge · c560a5b1
      unknown authored
      
      sql/ha_innodb.cc:
        Auto merged
      c560a5b1
  6. 17 Mar, 2006 6 commits
    • unknown's avatar
      Merge bk-internal.mysql.com:/home/bk/mysql-5.0 · 1a78addd
      unknown authored
      into  calliope.local:/Volumes/Source/src/mysql-5.0__bug15846
      
      
      1a78addd
    • unknown's avatar
      No longer leak file descriptors in mysql_close. Fixes Bug#15846. · b835245e
      unknown authored
      
      vio/viosocket.c:
        ORs were wrong to begin with, but more importantly, we mustn't use 
        shortable-circuit logic.
        
        Also newly reap the connection-closed event handle.
      b835245e
    • unknown's avatar
      configure.in: · c0c6af35
      unknown authored
        NDB_VERSION_BUILD has to be numeric
      
      
      configure.in:
        NDB_VERSION_BUILD has to be numeric
      c0c6af35
    • unknown's avatar
      configure.in: · 3adad925
      unknown authored
        Changed release name to 5.0.19a
      ha_innodb.cc:
        InnoDB used table locks (not row locks) within stored functions. (Bug #18077)
      
      
      sql/ha_innodb.cc:
        InnoDB used table locks (not row locks) within stored functions. (Bug #18077)
      configure.in:
        Changed release name to 5.0.19a
      3adad925
    • unknown's avatar
      Merge mysql.com:/home/emurphy/src/mysql/bk-clean/mysql-4.1 · 2122a3f9
      unknown authored
      into  mysql.com:/home/emurphy/src/mysql/bk-clean/mysql-5.0
      
      
      sql/ha_innodb.cc:
        Auto merged
      2122a3f9
    • unknown's avatar
      BUG#18283 When InnoDB returns error 'lock table full', MySQL can write · 367442f7
      unknown authored
      to binlog too much.
      
      When InnoDB has to rollback a transaction because the lock table has
      filled up, it also needs to inform the upper layer that the transaction
      was rolled back so that the cached transaction is not written to the
      binary log.
      
      
      sql/ha_innodb.cc:
        When InnoDB rolls back a transaction in HA_ERR_LOCK_TABLE_FULL, it
        needs to inform the upper layer to rollback the transaction also.
      367442f7
  7. 16 Mar, 2006 6 commits