An error occurred fetching the project authors.
  1. 20 Sep, 2004 1 commit
    • unknown's avatar
      These modifications were part of WL#1856 Conversion of client_test.c tests... · 40d6c6e2
      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
      40d6c6e2
  2. 17 Sep, 2004 1 commit
    • unknown's avatar
      A fix and test case for bug#5510 "inserting Null in AutoIncrement primary · 4148c9f9
      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.
      4148c9f9
  3. 16 Sep, 2004 1 commit
  4. 15 Sep, 2004 1 commit
    • unknown's avatar
      Fix the test case to make it more predictable (cause: 4.1.5 test failure · 057f6b6f
      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).
      057f6b6f
  5. 30 Jul, 2004 1 commit
  6. 21 Jul, 2004 1 commit
    • unknown's avatar
      fixed ORDER BY ? · bfaf9b0c
      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 :)
      bfaf9b0c
  7. 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) · 3a36d587
      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
      3a36d587
  8. 01 Jul, 2004 1 commit