1. 25 Dec, 2006 1 commit
  2. 14 Dec, 2006 3 commits
  3. 12 Dec, 2006 1 commit
    • unknown's avatar
      Fixed bug #24670: optimizations that are legal only for subqueries without tables · 33446269
      unknown authored
      and no WHERE condition were applied for any subquery without tables.
      
      
      
      mysql-test/r/subselect.result:
        Added a test case for bug #24670.
      mysql-test/t/subselect.test:
        Added a test case for bug #24670.
      sql/item_subselect.cc:
        Fixed bug #24670: optimizations that are legal only for subqueries without tables
        and no WHERE condition were applied for any subquery without tables.
        
        Removed an assertion that caused an abort for subqueries without tables and no 
        WHERE condition. 
        Blocked substitution of a single-row subquery without tables for the constant 
        row from its select list when the subquery contained a WHERE condition.
        This optimization is valid only for subquries without tables with no conditions.
        Any subquery without tables with WHERE clause returns NULL if the WHERE condition
        is FALSE. Erroneously it was always considered as non-nullable that could trigger 
        another optimization concerning IS NULL predicates which is applicable only for 
        non-nullable expressions and ultimately led to a wrong result returned by the outer
        query.
        Added a proper implementation of the virtual method may_be_null for class 
        subselect_single_select_engine.
      sql/item_subselect.h:
        Fixed bug #24670: optimizations that are legal only for subqueries without tables
        and no WHERE condition were applied for any subquery without tables.
        Made method may_by_null for class subselect_engine vvirtual.
      33446269
  4. 11 Dec, 2006 2 commits
  5. 07 Dec, 2006 2 commits
  6. 06 Dec, 2006 2 commits
    • unknown's avatar
      bug #22372 · 63fce3a2
      unknown authored
      datafile added to be used in gis.test
      
      
      mysql-test/std_data/bad_gis_data.dat:
        New BitKeeper file ``mysql-test/std_data/bad_gis_data.dat''
      63fce3a2
    • unknown's avatar
      bug #22372 (LOAD DATA crashes the table with the geometry field) · fa115a0f
      unknown authored
      The problem is that the GEOMETRY NOT NULL can't automatically set
      any value as a default one. We always tried to complete LOAD DATA
      command even if there's not enough data in file. That doesn't work
      for GEOMETRY NOT NULL. Now Field_*::reset() returns an error sign
      and it's checked in mysql_load()
      
      
      mysql-test/r/gis.result:
        test result
      mysql-test/t/gis.test:
        testcase
      sql/field.cc:
        reset() now returns error sign
      sql/field.h:
        Field_*::reset() now returns error sign if the field can't be reset
      sql/sql_load.cc:
        check if field can't be reset and return error if it's so
      fa115a0f
  7. 05 Dec, 2006 6 commits
  8. 04 Dec, 2006 4 commits
  9. 01 Dec, 2006 2 commits
  10. 30 Nov, 2006 4 commits
  11. 29 Nov, 2006 9 commits
  12. 28 Nov, 2006 4 commits
    • unknown's avatar
      Merge bk-internal.mysql.com:/home/bk/mysql-4.1 · 760bd9d1
      unknown authored
      into  bodhi.local:/opt/local/work/mysql-4.1-runtime
      
      
      libmysql/libmysql.c:
        Auto merged
      libmysqld/lib_sql.cc:
        Auto merged
      sql/item_sum.cc:
        Auto merged
      760bd9d1
    • unknown's avatar
      Bug#20836 Selecting into variables results in wrong results being returned · b4aab152
      unknown authored
      This error is displayed anytime the SELECT statement needs a temp table to
      return correct results because the object (select_dumpvar) that represents
      variables named in the INTO clause stored the results before the temp
      table was considered.  The problem was fixed by creating the necessary
      Item_func_set_user_var objects once the correct data is ready.
      
      
      mysql-test/r/distinct.result:
        Bug#20836 Selecting into variables results in wrong results being returned
        - Added results
      mysql-test/t/distinct.test:
        Bug#20836 Selecting into variables results in wrong results being returned
        - Added various Selects that use the INTO statement and a temp table.
        - Added Select Into Outfile variant tests also.
      sql/sql_class.cc:
        Bug#20836 Selecting into variables results in wrong results being returned
        - The select_dumpvar variable created a Item_func_set_user_var too early
        and once set, it was not possible to change.  The Item_func_set_user_var
        is now created once the final results are available.
      sql/sql_class.h:
        Bug#20836 Selecting into variables results in wrong results being returned
        - Removed unnecessary object members.
      b4aab152
    • unknown's avatar
      Move the check that $opt_vardir could be created and was writable to the function · b3273629
      unknown authored
      where we know how to creat the vardir 
      Remove unused variable
      
      
      b3273629
    • unknown's avatar
      Merge neptunus.(none):/home/msvensson/mysql/work/my41-work · 6e36d3c5
      unknown authored
      into  neptunus.(none):/home/msvensson/mysql/mysql-4.1-maint
      
      
      mysql-test/mysql-test-run.pl:
        Auto merged
      6e36d3c5