1. 02 Oct, 2006 1 commit
    • unknown's avatar
      Bug#21811 Odd casting with date + INTERVAL arithmetic · 5e71afcb
      unknown authored
      - Type casting was not consequent, thus when adding a DATE type with
        a WEEK interval the result type was DATETIME and not DATE as is the
        norm.
      - By changing the order of the date internal enumerations the deviant
        type casting is resolved (Item_date_add_interval::fix_length_and_dec()
        which determines result type for this operation assumes that addition
        of any interval with value <= INTERVAL_DAY to date value will result
        in date). There are two independant places to change:
        interval_names[] and interval_type.
      
      
      mysql-test/r/func_date_add.result:
        Updated result file for type casting test
      mysql-test/r/func_time.result:
        Updated result file for type casting test
      mysql-test/t/func_date_add.test:
        Added test for type casting when adding intervals to date.
      sql/item_timefunc.cc:
        Changed order of "week" key word to match the date interval enumeration.
      sql/item_timefunc.h:
        Changed the order of the enumeration to better follow interval sizes.
      5e71afcb
  2. 19 Sep, 2006 4 commits
  3. 18 Sep, 2006 2 commits
  4. 15 Sep, 2006 8 commits
  5. 14 Sep, 2006 1 commit
    • unknown's avatar
      Bug#21424 mysqldump failing to export/import views. ... · 0aa344f3
      unknown authored
      Bug#21424 mysqldump failing to export/import views.                                                                                                                                                                  
      
      Dumps are created for the tables in each specified database then for the views in each specified database. This bug occurs when any database's views depend on the mysql database's table data while being restored. 
      Added command line option --flush-privileges to the mysqldump utility which causes a FLUSH PRIVILIGES statement to be written to the dump after the mysql database.
      
      
      client/mysqldump.c:
        When the flush-privileges command line option is specified, make sure to FLUSH PRIVILEGES after only the mysql database's tables' data is restored so that grant tables are current.
      mysql-test/r/mysqldump.result:
        Added Results.
      mysql-test/t/mysqldump.test:
        Expanded existing test case for bug 21527 to also test for bug 21424. 
        Exercises new --flush-priviliges command line option.
        Test ignores log tables.
      0aa344f3
  6. 12 Sep, 2006 3 commits
    • unknown's avatar
      Bug#14862 undefined reference to `isinf' on SOLARIS - strings/strtod.c · acd9f1bd
      unknown authored
       - Change the configure test looking for 'isinf' so the value returned from isinf is used. That avoids the call to isinf being optimized away. 
      
      
      configure.in:
        Use the value returned from isinf so it's not optimized away by the compiler(i.e gcc 4.1)
      acd9f1bd
    • unknown's avatar
      Merge neptunus.(none):/home/msvensson/mysql/tmp_merge · 2214e282
      unknown authored
      into  neptunus.(none):/home/msvensson/mysql/mysql-5.0-maint
      
      
      mysql-test/mysql-test-run.pl:
        Null merge backported changes
      mysql-test/lib/mtr_cases.pl:
        Null merge backported changes
      mysql-test/lib/mtr_match.pl:
        Auto merged
      mysql-test/lib/mtr_misc.pl:
        Null merge backported changes
      mysql-test/r/ctype_ucs.result:
        SCCS merged
      mysql-test/t/ctype_ucs.test:
        Null merge, fixed in 5.0 already
      BUILD/SETUP.sh:
        Merge
      mysql-test/r/myisam.result:
        Merge
      mysql-test/t/myisam.test:
        Merge
      support-files/mysql.spec.sh:
        Merge
      tests/mysql_client_test.c:
        Merge
      2214e282
    • unknown's avatar
      Merge neptunus.(none):/home/msvensson/mysql/mysql-5.0 · c4812a0a
      unknown authored
      into  neptunus.(none):/home/msvensson/mysql/mysql-5.0-maint
      
      
      c4812a0a
  7. 08 Sep, 2006 2 commits
    • unknown's avatar
      Merge sgluhov@bk-internal.mysql.com:/home/bk/mysql-5.0 · 3fa0f96b
      unknown authored
      into  mysql.com:/home/gluh/MySQL/Merge/5.0
      
      
      3fa0f96b
    • unknown's avatar
      after merge fix · 4ef211ee
      unknown authored
      
      sql/mysql_priv.h:
        after merge fix
        added charset parameter to check_string_length() function
      sql/slave.h:
        after merge fix
        USERNAME_LENGTH const is changed to USERNAME_BYTE_LENGTH
      sql/sql_parse.cc:
        after merge fix
        added charset parameter to check_string_length() function
      sql/sql_yacc.yy:
        after merge fix
        added charset parameter to check_string_length() function
      4ef211ee
  8. 07 Sep, 2006 5 commits
    • unknown's avatar
      configure.in : NDB version and general version must be (kept) in sync - do that. · e1a70926
      unknown authored
      
      configure.in:
        NDB version and general version must be (kept) in sync - do that.
      e1a70926
    • unknown's avatar
      Merge trift2.:/M50/clone-5.0 · 2d35bd61
      unknown authored
      into  trift2.:/M50/push-5.0
      
      
      configure.in:
        Auto merged
      2d35bd61
    • unknown's avatar
      Fix a change to "configure.in" that broke building commercial sources. · b179cf8f
      unknown authored
      To be pushed to both the cloned 5.0.25 and the general 5.0 tree.
      
      
      configure.in:
        When creating "commercial" sources, this file gets modified by "mysql-copyright".
        For this, it is essential that the string 'cmd-line-utils/readline/Makefile'
        be alone on its line ...
      b179cf8f
    • unknown's avatar
      after merge fix · dc6243e5
      unknown authored
      
      include/mysql_com.h:
        USERNAME_LENGTH is changed to USERNAME_BYTE_LENGTH
      mysql-test/r/ctype_utf8.result:
        result fix
      mysql-test/t/ctype_utf8.test:
        test fix
      sql/sp.cc:
        NAME_LEN constant is changed to NAME_BYTE_LEN for database name buffer
        USERNAME_LENGTH constant is changed to USERNAME_BYTE_LENGTH for user name buffer
      sql/sp_head.cc:
        NAME_LEN constant is changed to NAME_BYTE_LEN for database name buffer
        USERNAME_LENGTH constant is changed to USERNAME_BYTE_LENGTH for user name buffer
      sql/sql_acl.cc:
        NAME_LEN constant is changed to NAME_BYTE_LEN for database name buffer
        USERNAME_LENGTH constant is changed to USERNAME_BYTE_LENGTH for user name buffer
      sql/sql_class.h:
        NAME_LEN constant is changed to NAME_BYTE_LEN for database name buffer
      sql/sql_parse.cc:
        NAME_LEN constant is changed to NAME_BYTE_LEN for database name buffer
        Function check_string_length() is fixed, now it check string lenght in symbols
      sql/sql_repl.h:
        NAME_LEN constant is changed to NAME_BYTE_LEN for database name buffer
        USERNAME_LENGTH constant is changed to USERNAME_BYTE_LENGTH for user name buffer
      dc6243e5
    • unknown's avatar
      Merge mysql.com:/home/gluh/MySQL/Merge/4.1-merge · 146049d2
      unknown authored
      into  mysql.com:/home/gluh/MySQL/Merge/5.0
      
      
      include/mysql_com.h:
        Auto merged
      mysql-test/t/ctype_utf8.test:
        Auto merged
      sql/item_func.h:
        Auto merged
      sql/item_strfunc.cc:
        Auto merged
      sql/item_strfunc.h:
        Auto merged
      sql/slave.cc:
        Auto merged
      sql/sql_parse.cc:
        Auto merged
      sql-common/client.c:
        Auto merged
      sql/sql_select.cc:
        Auto merged
      sql/table.cc:
        Auto merged
      mysql-test/r/ctype_utf8.result:
        manual merge
      sql/sql_acl.cc:
        manual merge
      146049d2
  9. 06 Sep, 2006 8 commits
  10. 05 Sep, 2006 1 commit
    • unknown's avatar
      Fix for BUG#11151 "LOAD DATA INFILE commits transaction in 5.0". · a0b7b242
      unknown authored
      In 5.0 we made LOAD DATA INFILE autocommit in all engines, while
      only NDB wanted that. Users and trainers complained that it affected
      InnoDB and was a change compared to 4.1 where only NDB autocommitted.
      To revert to the behaviour of 4.1, we move the autocommit logic out of mysql_load() into
      ha_ndbcluster::external_lock().
      The result is that LOAD DATA INFILE commits all uncommitted changes
      of NDB if this is an NDB table, its own changes if this is an NDB
      table, but does not affect other engines.
      Note: even though there is no "commit the full transaction at end"
      anymore, LOAD DATA INFILE stays disabled in routines (re-entrency
      problems per a comment of Pem).
      Note: ha_ndbcluster::has_transactions() does not give reliable results
      because it says "yes" even if transactions are disabled in this engine...
      
      
      sql/ha_ndbcluster.cc:
        NDB wants to do autocommit if this is LOAD DATA INFILE.
        For this to not affect all other engines, we move the logic
        inside ha_ndbcluster.
      sql/sql_load.cc:
        This ha_enable_transaction() in mysql_load() forced an autocommit
        in all engines, while only NDB wants to do that.
        So we move the logic inside ha_ndbcluster.cc.
      mysql-test/include/loaddata_autocom.inc:
        test for engines to see if they autocommit or not in LOAD DATA INFILE
      mysql-test/r/loaddata_autocom_innodb.result:
        result for InnoDB (no autocommit)
      mysql-test/r/loaddata_autocom_ndb.result:
        result for NDB (autocommit)
      mysql-test/r/rpl_ndb_innodb_trans.result:
        result for InnoDB+NDB transactions. Observe that when ROLLBACK
        cannot rollback the LOAD DATA INFILE in NDB it issues warning 1196
        as appropriate.
      mysql-test/t/loaddata_autocom_innodb.test:
        test that InnoDB does not autocommit in LOAD DATA INFILE.
      mysql-test/t/loaddata_autocom_ndb.test:
        test that NDB does autocommit in LOAD DATA INFIL
      mysql-test/t/rpl_ndb_innodb_trans-slave.opt:
        need to tell the slave to use innodb
      mysql-test/t/rpl_ndb_innodb_trans.test:
        test of transactions mixing NDB and InnoDB. To see if ROLLBACK
        rolls back in both engines, with the exception of LOAD DATA INFILE
        which does not roll back NDB: we see that a LOAD DATA INFILE in NDB
        commits all what has been done in NDB so far, commits its changes,
        but does not commit in other engines.
      a0b7b242
  11. 04 Sep, 2006 5 commits