An error occurred fetching the project authors.
  1. 10 Nov, 2004 1 commit
    • unknown's avatar
      1. When mixing NULL to a character string, · c5e6941e
      unknown authored
      the result takes its charset/collation
      attributes from the character string,
      e.g.  SELECT func(NULL, _latin2'string')
      now returns a latin2 result. This is
      done by introducing a new derivation
      (aka coercibility) level DERIVATION_IGNORABLE,
      which is used with Item_null.
      2. 'Pure' NULL is now BINARY(0), not CHAR(0).
      I.e. NULL is now more typeless.
      
      
      mysql-test/r/metadata.result:
        Fixing test results:
        CHAR(0) -> BINARY(0) for NULLs
      mysql-test/r/null.result:
        Testing mixing NULL with a character string with a number of functions.
      mysql-test/r/ps_2myisam.result:
        Fixing test results:
        CHAR(0) -> BINARY(0) for NULLs
      mysql-test/r/ps_3innodb.result:
        Fixing test results:
        CHAR(0) -> BINARY(0) for NULLs
      mysql-test/r/ps_4heap.result:
        Fixing test results:
        CHAR(0) -> BINARY(0) for NULLs
      mysql-test/r/ps_5merge.result:
        Fixing test results:
        CHAR(0) -> BINARY(0) for NULLs
      mysql-test/r/ps_6bdb.result:
        Fixing test results:
        CHAR(0) -> BINARY(0) for NULLs
      mysql-test/r/ps_7ndb.result:
        Fixing test results:
        CHAR(0) -> BINARY(0) for NULLs
      mysql-test/t/null.test:
        Testing mixing NULL with a character string with a number of functions.
      sql/item.cc:
        New derivation level.
      sql/item.h:
        New derivation level.
      c5e6941e
  2. 05 Nov, 2004 1 commit
    • unknown's avatar
      As it is wrong and confusing to associate any · aee1e78a
      unknown authored
      character set with NULL, @A should be latin2
      after this query sequence:
      
         SET @A=_latin2'string';
         SET @A=NULL;
      
      I.e. the second query should not change the charset
      to the current default value, but should keep the
      original value assigned during the first query.
      In order to do it, we don't copy charset
      from the argument if the argument is NULL
      and the variable has previously been initialized.
      
      
      mysql-test/r/ps_6bdb.result:
        t
      mysql-test/r/ps_5merge.result:
        t
      mysql-test/r/ps_3innodb.result:
        t
      mysql-test/r/ps_7ndb.result:
        t
      mysql-test/r/ps_4heap.result:
        t
      mysql-test/r/ps_2myisam.result:
        t
      sql/item_func.cc:
        t
      aee1e78a
  3. 30 Oct, 2004 1 commit
    • unknown's avatar
      Enable REPLACE ... SELECT in prepared statements. · d46c7366
      unknown authored
      mysql-test/include/ps_modify.inc:
        replace ... select now works.
      mysql-test/r/ps_2myisam.result:
        replace ... select now works.
      mysql-test/r/ps_3innodb.result:
        replace ... select now works.
      mysql-test/r/ps_4heap.result:
        replace ... select now works.
      mysql-test/r/ps_5merge.result:
        replace ... select now works.
      mysql-test/r/ps_6bdb.result:
        replace ... select now works.
      mysql-test/r/ps_7ndb.result:
        replace ... select now works.
      mysql-test/t/ps_7ndb.test:
        replace ... select now works.
      sql/sql_prepare.cc:
        Enable SQLCOM_REPLACE_SELECT: no need for any code changes but
        enable this SQLCOM in the switch.
      d46c7366
  4. 11 Oct, 2004 1 commit
  5. 07 Oct, 2004 3 commits
  6. 28 Sep, 2004 1 commit
    • unknown's avatar
      Some of the recently pushed prepared statements · 22cca358
      unknown authored
      tests were disabled due to failures caused by floating point conversion
      issues on optimized builds).
      
      
      mysql-test/include/ps_conv.inc:
        Disable some of the tests for the test suite to pass on an optimized 
        build (floating point issues...).
      mysql-test/include/ps_query.inc:
        Disable some of the tests for the test suite to pass on an optimized 
        build (floating point issues...).
      mysql-test/r/ps_2myisam.result:
        Fix test results.
      mysql-test/r/ps_3innodb.result:
        Fix test results.
      mysql-test/r/ps_4heap.result:
        Fix test results.
      mysql-test/r/ps_5merge.result:
        Fix test results.
      mysql-test/r/ps_6bdb.result:
        Fix test results.
      mysql-test/r/ps_7ndb.result:
        Fix test results.
      22cca358
  7. 25 Sep, 2004 1 commit
    • unknown's avatar
      Results of WL#1856 "Conversion of client_test.c tests cases to mysqltest · 9ff04fe5
      unknown authored
      if possible"
              - many new test cases
              - more and improved comments
            New files: t/ps_7ndb.test       test suite for NDB tables
                       r/ps_7ndb.result     expected results
                       include/ps_conv.inc  conversion test cases
      + review comments and fixes.
      
      
      mysql-test/include/ps_create.inc:
        Rename of t_many_col_types -> t9
      mysql-test/include/ps_modify.inc:
        WL#1856 Conversion of client_test.c tests cases to mysqltest if possible
        Rename: t_many_col_types -> t9
        Cleanups and comments.
        New test cases (derived from client_test.c)
      mysql-test/include/ps_modify1.inc:
        WL#1856 Conversion of client_test.c tests cases to mysqltest if possible
        Rename: t_many_col_types -> t9
        Cleanups and comments.
        New test cases (derived from client_test.c)
      mysql-test/include/ps_query.inc:
        WL#1856 Conversion of client_test.c tests cases to mysqltest if possible
        Rename: t_many_col_types -> t9
        Cleanups and comments.
        New test cases (derived from client_test.c)
      mysql-test/include/ps_renew.inc:
        WL#1856 Conversion of client_test.c tests cases to mysqltest if possible
        Rename: t_many_col_types -> t9
      mysql-test/r/ps_1general.result:
        Results updated.
      mysql-test/r/ps_2myisam.result:
        Resutls updated.
      mysql-test/r/ps_3innodb.result:
        Results updated.
      mysql-test/r/ps_4heap.result:
        Results updated.
      mysql-test/r/ps_5merge.result:
        Results updated.
      mysql-test/r/ps_6bdb.result:
        Results updated.
      mysql-test/t/ps_1general.test:
        WL#1856 "Conversion of client_test.c tests cases to mysqltest if
         possible": new test cases added.
      mysql-test/t/ps_2myisam.test:
        WL#1856 Conversion of client_test.c tests cases to mysqltest if possible
        Call of file include/ps_conv.inc (with new test cases) and 
        fulltext test case added.
      mysql-test/t/ps_3innodb.test:
        WL#1856 Conversion of client_test.c tests cases to mysqltest if possible
        Call of file include/ps_conv.inc (with new test cases) added.
      mysql-test/t/ps_4heap.test:
        WL#1856 Conversion of client_test.c tests cases to mysqltest if possible
        Call of file include/ps_conv.inc (with new test cases) added.
      mysql-test/t/ps_5merge.test:
        WL#1856 Conversion of client_test.c tests cases to mysqltest if possible
        Call of file include/ps_conv.inc (with new test cases) added.
      mysql-test/t/ps_6bdb.test:
        WL#1856 Conversion of client_test.c tests cases to mysqltest if possible.
        Call of file include/ps_conv.inc (with new test cases) added.
      9ff04fe5
  8. 20 Sep, 2004 1 commit
    • unknown's avatar
      These modifications were part of WL#1856 Conversion of client_test.c tests... · 5a53ee4f
      unknown authored
      These modifications were part of WL#1856 Conversion of client_test.c tests cases to mysqltest if possible
      
      They are separated from the other WL#1856 stuff, because they improve the behaviour of the current tests.  
      
      Make the result sets (order of rows) more predictable by using ORDER BY.
      
      
      mysql-test/include/ps_modify.inc:
        Make the result sets more predictable by using ORDER BY
      mysql-test/include/ps_modify1.inc:
        Make the result sets more predictable by using ORDER BY
      mysql-test/r/ps_2myisam.result:
        updated results
      mysql-test/r/ps_3innodb.result:
        updated results
      mysql-test/r/ps_4heap.result:
        updated results
      mysql-test/r/ps_5merge.result:
        updated results
      mysql-test/r/ps_6bdb.result:
        updated results
      BitKeeper/etc/logging_ok:
        Logging to logging@openlogging.org accepted
      5a53ee4f
  9. 17 Sep, 2004 1 commit
    • unknown's avatar
      A fix and test case for bug#5510 "inserting Null in AutoIncrement primary · 52683755
      unknown authored
      key Column Fails".
      
      
      mysql-test/r/ps.result:
        Test results updated: a test case for Bug#5510 "inserting Null in 
        AutoIncrement primary key Column Fails".
      mysql-test/r/ps_2myisam.result:
        Bug#5510: a different warning in case of NULL->default truncation.This is 
        OK, the new warning is the same as produced by conventional execution.
      mysql-test/r/ps_3innodb.result:
        Bug#5510: a different warning in case of NULL->default truncation.This is 
        OK, the new warning is the same as produced by conventional execution.
      mysql-test/r/ps_4heap.result:
        Bug#5510: a different warning in case of NULL->default truncation.This is 
        OK, the new warning is the same as produced by conventional execution.
      mysql-test/r/ps_5merge.result:
        Bug#5510: a different warning in case of NULL->default truncation.This is 
        OK, the new warning is the same as produced by conventional execution.
      mysql-test/r/ps_6bdb.result:
        Bug#5510: a different warning in case of NULL->default truncation.This is 
        OK, the new warning is the same as produced by conventional execution.
      mysql-test/t/ps.test:
        A test case for Bug#5510 "inserting Null in AutoIncrement primary key Column 
        Fails".
      sql/item.cc:
        A fix for bug#5510 "inserting Null in AutoIncrement primary key Column 
        Fails": use proper Field API function for NULL placholeders.
      52683755
  10. 16 Sep, 2004 1 commit
  11. 15 Sep, 2004 1 commit
    • unknown's avatar
      Fix the test case to make it more predictable (cause: 4.1.5 test failure · 3db7442e
      unknown authored
      on intelxeon3 (Solaris x86))
      
      
      mysql-test/r/ps_2myisam.result:
        Test results fixed (order by for a couple of statements in the PS test).
      mysql-test/r/ps_3innodb.result:
        Test results fixed (order by for a couple of statements in the PS test).
      mysql-test/r/ps_4heap.result:
        Test results fixed (order by for a couple of statements in the PS test).
      mysql-test/r/ps_5merge.result:
        Test results fixed (order by for a couple of statements in the PS test).
      mysql-test/r/ps_6bdb.result:
        Test results fixed (order by for a couple of statements in the PS test).
      3db7442e
  12. 28 Jul, 2004 1 commit
    • unknown's avatar
      Fix for bug #4492. · a5e453e6
      unknown authored
      TIMESTAMP columns should be unsigned to preserve compatibility with 4.0
      (Or else InnoDB will return different internal TIMESTAMP values when user upgrades to 4.1).
      
      Altough this fix will introduce problems with early 4.1 -> 4.1 upgrades (tables with 
      TIMESTAMP field should be reloaded using mysqldump) it will allow easy 4.0 -> 4.1 
      upgrade (which is more important since 4.1 is still beta).
      
      
      mysql-test/r/metadata.result:
        TIMESTAMP should be UNSIGNED as in 4.0.
      mysql-test/r/ps_2myisam.result:
        TIMESTAMP should be UNSIGNED as in 4.0.
      mysql-test/r/ps_3innodb.result:
        TIMESTAMP should be UNSIGNED as in 4.0.
      mysql-test/r/ps_4heap.result:
        TIMESTAMP should be UNSIGNED as in 4.0.
      mysql-test/r/ps_5merge.result:
        TIMESTAMP should be UNSIGNED as in 4.0.
      sql/field.cc:
        TIMESTAMP should be UNSIGNED to preserve compatiblity with 4.0.
        (Or else InnoDB will return different internal TIMESTAMP values when user upgrades to 4.1).
      a5e453e6
  13. 21 Jul, 2004 1 commit
    • unknown's avatar
      fixed ORDER BY ? · cb35648e
      unknown authored
      new tests to ensure that prepared statement *really* work
      (and that MySQL not picks up some number from arbitrary location
      that happens to match the parameter's value)
      
      
      mysql-test/include/ps_query.inc:
        new tests to ensure that prepared statement *really* work
        (and that MySQL not picks up some number from arbitrary location
        that happens to match the parameter's value)
      mysql-test/r/ps_2myisam.result:
        results updated
      mysql-test/r/ps_3innodb.result:
        results updated
      mysql-test/r/ps_4heap.result:
        results updated
      mysql-test/r/ps_5merge.result:
        results updated
      mysql-test/r/ps_6bdb.result:
        results updated
      sql/sql_select.cc:
        don't shortcut - it backfires!
        (in particular - when itemptr is Item_param :)
      cb35648e
  14. 04 Jul, 2004 1 commit
    • unknown's avatar
      do not assign values of left expression of IN/ANN/ANY subquery in case of PS preparation (BUG#4403) · ad165ad1
      unknown authored
      mysql-test/r/ps_2myisam.result:
        changes in results of select without order by
      mysql-test/r/ps_3innodb.result:
        changes in results of select without order by
      mysql-test/r/ps_5merge.result:
        changes in results of select without order by
      mysql-test/r/ps_6bdb.result:
        changes in results of select without order by
      sql/item_cmpfunc.cc:
        do not assign values of left expression of IN/ANN/ANY subquery in case of PS preparation
      ad165ad1
  15. 01 Jul, 2004 1 commit