1. 07 Apr, 2006 3 commits
  2. 06 Apr, 2006 16 commits
    • unknown's avatar
      Merge mysql.com:/home/greenman/workspace-mysql/mysql/mysql-5.0 · 2639449a
      unknown authored
      into  mysql.com:/home/greenman/workspace-mysql/mysql/bug-5.0-16240
      
      2639449a
    • unknown's avatar
      Merge spetrunia@bk-internal.mysql.com:/home/bk/mysql-5.0 · 3593d257
      unknown authored
      into  mysql.com:/home/psergey/mysql-5.0-bug18237-review
      
      3593d257
    • unknown's avatar
      Remove redundant code in opt_sum_query() · 221e5e06
      unknown authored
      221e5e06
    • unknown's avatar
      Fix for Bug #16240 · ba54fa58
      unknown authored
      
      support-files/mysql.server.sh:
        Fixed so that if the datadir has been set via the command line,
        it won't be reset by specifing the basedir after.
      ba54fa58
    • unknown's avatar
      Merge svojtovich@bk-internal.mysql.com:/home/bk/mysql-5.0 · e147a4a2
      unknown authored
      into  april.(none):/home/svoj/devel/mysql/BUG14945/mysql-5.0
      
      e147a4a2
    • unknown's avatar
      Fix for bug#14945 "Truncate table doesn't reset the auto_increment · 0d373cdd
      unknown authored
      counter".
      
      When TRUNCATE TABLE was called within an stored procedure the
      auto_increment counter was not reset to 0 even if straight
      TRUNCATE for this table did this.
      
      This fix makes TRUNCATE in stored procedures to be handled exactly
      in the same way as straight TRUNCATE. We achieve this by rolling
      back the fix for bug 8850, which is no longer needed since stored
      procedures don't require prelocked mode anymore (and TRUNCATE is
      not allowed in stored functions or triggers).
      
      
      mysql-test/r/sp.result:
        Test case for BUG#14945.
      mysql-test/t/sp.test:
        Test case for BUG#14945.
      sql/sql_delete.cc:
        Handle TRUNCATE in stored procedures exactly in the same way as straight
        TRUNCATE (i.e. without falling back to DELETE if possible). We achieve
        this by rolling back the fix for bug 8850, which is no longer relevant
        since stored procedures don't require prelocked mode anymore
        (and TRUNCATE is not allowed in stored functions or triggers).
      sql/sql_parse.cc:
        Handle TRUNCATE in stored procedures exactly in the same way as straight
        TRUNCATE (i.e. without falling back to DELETE if possible). We achieve
        this by rolling back the fix for bug 8850, which is no longer relevant
        since stored procedures don't require prelocked mode anymore
        (and TRUNCATE is not allowed in stored functions or triggers).
      0d373cdd
    • unknown's avatar
      Merge bk-internal.mysql.com:/home/bk/mysql-5.0 · bf803371
      unknown authored
      into  shellback.(none):/home/msvensson/mysql/mysql-5.0
      
      bf803371
    • unknown's avatar
      Moving mysql_get_server_version() from libmysql.c to client.c, · ba49c29d
      unknown authored
      as it is now required by mysql_set_character_set()
      
      
      libmysql/libmysql.c:
        Removing mysql_get_server_version()
      sql-common/client.c:
        Adding mysql_get_server_version()
      ba49c29d
    • unknown's avatar
      client.c: · 1a6f7c6d
      unknown authored
        Bug#18830 incompatibility new libraries with old server
        Additional 5.0 fix:
        applying the same patch to client.c.
      
      
      sql-common/client.c:
        Bug#18830 incompatibility new libraries with old server
        Additional 5.0 fix:
        applying the same patch to client.c.
      1a6f7c6d
    • unknown's avatar
      Merge mysql.com:/usr/home/bar/mysql-4.1 · efff3c00
      unknown authored
      into  mysql.com:/usr/home/bar/mysql-5.0
      
      
      libmysql/libmysql.c:
        Bug#18830 incompatibility new libraries with old server
        Mergeing from 4.1
      efff3c00
    • unknown's avatar
      libmysql.c: · 82c1be05
      unknown authored
        Bug#18830: incompatibility new libraries with old server
        Don't execute SET NAMES with pre-4.1 server.
      
      
      libmysql/libmysql.c:
        Bug#18830: incompatibility new libraries with old server
        Don't execute SET NAMES with pre-4.1 server.
      82c1be05
    • unknown's avatar
      Merge mysql.com:/usr/home/bar/mysql-4.1 · e6ab763c
      unknown authored
      into  mysql.com:/usr/home/bar/mysql-5.0
      
      e6ab763c
    • unknown's avatar
      This problem has already been fixed by one of the previous changes. · 6423230d
      unknown authored
      Adding test case to cover queries which worked incorrectly earlier:
      Bug#18321: Can't store EuroSign with latin1_german1_ci and latin1_general_ci
      
      
      mysql-test/r/ctype_latin1.result:
        Adding test case for Bug#18321: Can't store EuroSign with latin1_german1_ci and latin1_general_ci
      mysql-test/t/ctype_latin1.test:
        Adding test case for Bug#18321: Can't store EuroSign with latin1_german1_ci and latin1_general_ci
      6423230d
    • unknown's avatar
      ctype-extra.c: · 07b5476b
      unknown authored
        Using local.
      
      
      strings/ctype-extra.c:
        Using local.
      07b5476b
    • unknown's avatar
      Merge mysql.com:/usr/home/bar/mysql-4.1 · 7bcff99e
      unknown authored
      into  mysql.com:/usr/home/bar/mysql-5.0
      
      
      strings/conf_to_src.c:
        Auto merged
      7bcff99e
    • unknown's avatar
      conf_to_src.c: · 56dba198
      unknown authored
        Backporting a 5.0 change:
        MAX_BUF was too small for Index.xml
        Changeing MAX_BUF and adding assert to easier
        catch the same problem in the future.
      ctype-extra.c:
        Regenerating ctype-extra.c with the fixed conf_to_src.
      
      
      strings/ctype-extra.c:
        Regenerating ctype-extra.c with the fixed conf_to_src.
      strings/conf_to_src.c:
        Backporting a 5.0 change:
        MAX_BUF was too small for Index.xml
        Changeing MAX_BUF and adding assert to easier
        catch the same problem in the future.
      56dba198
  3. 05 Apr, 2006 5 commits
    • unknown's avatar
      Merge rurik.mysql.com:/home/igor/mysql-5.0 · aa482ce8
      unknown authored
      into  rurik.mysql.com:/home/igor/dev/mysql-5.0-0
      
      aa482ce8
    • unknown's avatar
      conf_to_src.c: · 931b9694
      unknown authored
        Buffer was too small to load Index.xml.
        So some charsets were not gerenrated.
        Making the buffer bigger, and adding an DBUG_ASSERT,
        to easier catch the problem in the future.
      ctype-extra.c:
        Additional charsets were generated.
      
      
      strings/ctype-extra.c:
        Additional charsets were generated.
      strings/conf_to_src.c:
        Buffer was too small to load Index.xml.
        So some charsets were not gerenrated.
        Making the buffer bigger, and adding an DBUG_ASSERT,
        to easier catch the problem in the future.
      931b9694
    • unknown's avatar
      Merge epotemkin@bk-internal.mysql.com:/home/bk/mysql-5.0 · 78e2681f
      unknown authored
      into sunlight.local:/local_work/16281-bug-5.0-mysql
      
      
      sql/field.h:
        Auto merged
      78e2681f
    • unknown's avatar
      Fixed bug #16281: Multi-table update broken in 5.0 on tables imported from 4.1 · 6c191f7a
      unknown authored
      Mutli-table uses temporary table to store new values for fields. With the
      new values the rowid of the record to be updated is stored in a Field_string
      field. Table to be updated is set as source table of the rowid field.
      But when the temporary table creates the tmp field for the rowid field it
      converts it to a varstring field because the table to be updated was created by
      the v4.1. Due to this the stored rowids were broken and no records for 
      update were found.
      
      The flag can_alter_field_type is added to Field_string class. When it is set to
      0 the field won't be converted to varstring. The Field_string::type() function 
      now always returns MYSQL_TYPE_STRING if can_alter_field_type is set to 0.
      The multi_update::initialize_tables() function now sets can_alter_field_type
      flag to 0 for the rowid fields denying conversion of the field to a varstring
      field.
      
      
      
      sql/field.h:
        Fixed bug #16281: Multi-table update broken in 5.0 on tables imported from 4.1
        The flag can_alter_field_type is added to Field_string class. When it is set to
        0 the field won't be converted to varstring.
        The Field_string::type() function now always returns MYSQL_TYPE_STRING if 
        can_alter_field_type is set to 0.
      sql/sql_update.cc:
        Fixed bug #16281: Multi-table update broken in 5.0 on tables imported from 4.1
        The multi_update::initialize_tables() function now sets can_alter_field_type
        flag to 0 for the rowid fields denying conversion of the field to a varstring
        field.
      6c191f7a
    • unknown's avatar
      Merge bk-internal.mysql.com:/home/bk/mysql-5.0 · 4a7d5ac2
      unknown authored
      into  shellback.(none):/home/msvensson/mysql/mysql-5.0
      
      
      mysql-test/mysql-test-run.pl:
        Auto merged
      4a7d5ac2
  4. 04 Apr, 2006 10 commits
  5. 03 Apr, 2006 6 commits