mariadb/mysql-test
unknown 33446269e1 Fixed bug #24670: optimizations that are legal only for subqueries without tables
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.
2006-12-11 18:57:23 -08:00
..
include add --report-features to mysql-test-run.pl 2006-11-10 13:12:08 +01:00
lib Merge neptunus.(none):/home/msvensson/mysql/mysql-4.1 2006-12-04 19:06:42 +01:00
misc
ndb reintroduce --no-defaults to ndb_mgmd 2006-01-20 00:08:26 +11:00
r Fixed bug #24670: optimizations that are legal only for subqueries without tables 2006-12-11 18:57:23 -08:00
std_data bug #22372 2006-12-06 21:47:29 +04:00
suite/jp
t Fixed bug #24670: optimizations that are legal only for subqueries without tables 2006-12-11 18:57:23 -08:00
create-test-result
fix-result
init_db.sql
install_test_db.sh mysql-test/install_test_db.sh 2006-11-09 17:43:31 +01:00
Makefile.am Merge neptunus.(none):/home/msvensson/mysql/mysql-4.1 2006-11-24 12:12:25 +01:00
my_create_tables.c
my_manage.c Some fixes to avoid compiler warnings. 2005-10-18 18:03:26 +03:00
my_manage.h
mysql-test-run-shell.sh Merge neptunus.(none):/home/msvensson/mysql/mysql-4.1 2006-11-24 12:12:25 +01:00
mysql-test-run.pl Merge neptunus.(none):/home/msvensson/mysql/mysql-4.1 2006-12-04 19:06:42 +01:00
mysql_test_run_new.c Some fixes to avoid compiler warnings. 2005-10-18 18:03:26 +03:00
README README: 2006-03-01 18:37:41 -06:00
README.gcov README.gcov: 2006-03-01 17:55:10 -06:00
resolve-stack
suppress.purify

This directory contains a test suite for the MySQL daemon. To run
the currently existing test cases, simply execute ./mysql-test-run in
this directory. It will fire up the newly built mysqld and test it.

Note that you do not have to have to do "make install", and you could
actually have a co-existing MySQL installation. The tests will not
conflict with it.

All tests must pass. If one or more of them fail on your system, please
read the following manual section for instructions on how to report the
problem:

http://dev.mysql.com/doc/mysql/en/mysql-test-suite.html

If you want to use an already running MySQL server for specific tests,
use the --extern option to mysql-test-run. Please note that in this mode,
the test suite expects you to provide the names of the tests to run.
For example, here is the command to run the "alias" and "analyze" tests
with an external server:

mysql-test-run --extern alias analyze

To match your setup, you might also need to provide --socket, --user, and
other relevant options.

With no test cases named on the command line, mysql-test-run falls back
to the normal "non-extern" behavior. The reason for this is that some
tests cannot run with an external server.


You can create your own test cases. To create a test case, create a new
file in the t subdirectory using a text editor. The file should have a .test
extension. For example:

 xemacs t/test_case_name.test

 In the file, put a set of SQL statements that create some tables,
 load test data, and run some queries to manipulate it.

 We would appreciate it if you name your test tables t1, t2, t3 ... (to not
 conflict too much with existing tables).

 Your test should begin by dropping the tables you are going to create and
 end by dropping them again.  This ensures that you can run the test over
 and over again.
 
 If you are using mysqltest commands (like result file names) in your
 test case, you should create the result file as follows:

 mysql-test-run --record test_case_name

 or

 mysqltest --record < t/test_case_name.test

 If you only have a simple test cases consisting of SQL statements and
 comments, you can create the test case in one of the following ways:

 mysql-test-run --record test_case_name

 mysql test < t/test_case_name.test > r/test_case_name.result

 mysqltest --record --record-file=r/test_case_name.result < t/test_case_name.test

 When this is done, take a look at r/test_case_name.result
 - If the result is incorrect, you have found a bug. In this case, you should
   edit the test result to the correct results so that we can verify
   that the bug is corrected in future releases.

To submit your test case, put your .test file and .result file(s) into
a tar.gz archive, add a README that explains the problem, ftp the 
archive to ftp://support.mysql.com/pub/mysql/secret/ and send a mail
to bugs@lists.mysql.com