mirror/mariadb
1
0
Fork 0
mirror of https://github.com/MariaDB/server.git synced 2025-02-01 03:21:53 +01:00
Code Issues Projects Releases Packages Wiki Activity Actions
mariadb/mysql-test
History
unknown d945033292 WL#1724 "Min/Max Optimization for Queries with Group By Clause" 
- after-review changes
- merged with the source tree from 204-08-27


mysql-test/r/distinct.result:
  Different plans due to group-by optimization.
sql/ha_myisam.cc:
  More general interface to key_copy.
sql/handler.cc:
  More general interface to key_copy.
sql/item.cc:
  New method to collect all Item_field objects. Used by Item::walk.
sql/item.h:
  Several methods to collect different kinds of items from expression trees.
  Used by Item::walk.
sql/item_sum.cc:
  Added helper to collect Item_sum objects.
sql/item_sum.h:
  Methods to collect and test Item_sum objects.
sql/key.cc:
  More general interface to key_copy and key_restore.
sql/mysql_priv.h:
  More general interface to key_copy and key_restore.
sql/opt_range.cc:
  Complete implementaion of WL#1724 "Min/Max Optimization for Queries with Group By Clause".
sql/opt_range.h:
  Complete implementaion of WL#1724 "Min/Max Optimization for Queries with Group By Clause".
sql/opt_sum.cc:
  simple_pred is re-used in opt_range.cc
sql/sql_acl.cc:
  More general interface to key_copy and key_restore.
sql/sql_handler.cc:
  More general interface to key_copy.
sql/sql_insert.cc:
  More general interface to key_copy.
sql/sql_select.cc:
  Changes to hook the new QUICK_GROUP_MIN_MAX_SELECT due to two differences from all other
  quick selects:
  1)
  This quick select may be created (and used) even if there is no WHERE clause.
  Several places assumed that a QUICK_SELECT is constructed only if there is a WHERE clause,
  which had to be changed so that QUICK_GROUP_MIN_MAX can be used.
  2)
  Unlike all other quick selects, this QUICK_GROUP_MIN_MAX_SELECT operates for GROUP BY queries.
  Since for the caller the quick select already produces one result tuple per group, there is
  no need to call end_send_group, instead we have to call end_send as for a regular quick select.
sql/sql_select.h:
  simple_pred is re-used in opt_range.cc
2004-08-27 16:37:13 +03:00
..
include Followup2 (new commands are supported in prepared statements): test files 2004-08-03 04:07:19 -07:00
misc WL#1717 "binlog/innodb consistency". 2004-06-23 23:51:40 +02:00
ndb - fixed typo in mysql-test/ndb/ndbcluster.sh that caused a 2004-07-05 07:48:09 +02:00
r WL#1724 "Min/Max Optimization for Queries with Group By Clause" 2004-08-27 16:37:13 +03:00
std_data symlink, not hardlink 2004-04-21 14:55:39 -05:00
t WL#1724 "Min/Max Optimization for Queries with Group By Clause" 2004-08-27 16:37:13 +03:00
create-test-result fixed problem spoted by Vladimir V. Kolpakov 2004-08-16 17:09:57 +03:00
fix-result
install_test_db.sh allow --skip-ndbcluster if server is not compiled 2004-04-16 08:32:10 +03:00
Makefile.am Fix for 'make dist' 'make distclean' goals work even if ./configure 2004-06-25 23:21:14 +04:00
mysql-test-run.sh After merge fixes 2004-07-15 04:19:07 +03:00
README Merge with 4.0 to get fixes for netware 2004-06-02 00:09:14 +03:00
README.gcov
resolve-stack

README 

This directory contains a test suite for 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.

If you want to run the test with a running MySQL server use the --external
option to mysql-test-run.

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 of how to report the problem:

http://dev.mysql.com/doc/mysql/en/MySQL_test_suite.html


You can create your own test cases. To create a test case:

 xeamacs t/test_case_name.test

 in the file, put a set of SQL commands that will create some tables,
 load test data, run some queries to manipulate it.

 We would appreciate if the test tables were called 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 will ensure that one can run the test
 over and over again.
 
 If you are using mysqltest commands (like result file names) in your
 test case you should do 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 consistent of SQL commands and comments
 you can create the test case 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 wrong, 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