ChangeSet@1.2615, 2008-04-28 21:53:52+02:00, kent@mysql.com +1 -0
  make_binary_distribution.sh:
    Copy all of the "std_data" directory

  scripts/make_binary_distribution.sh@1.133, 2008-04-25 19:09:00+02:00, kent@mysql.com +3 -9
    Copy all of the "std_data" directory

ChangeSet@1.2608.1.2, 2008-04-28 14:58:32-04:00, iggy@amd64.(none) +1 -0
  Correct failing build.

  include/my_global.h@1.151, 2008-04-28 14:58:30-04:00, iggy@amd64.(none) +6 -2
    Correct failing build.

ChangeSet@1.2608.1.1, 2008-04-28 13:41:12-04:00, iggy@amd64.(none) +1 -0
  Avoid compilation problem on AIX.

  mysys/thr_alarm.c@1.56, 2008-04-28 13:41:11-04:00, iggy@amd64.(none) +1 -2
    Avoid compilation problem on AIX.

ChangeSet@1.2612, 2008-04-24 17:13:35+02:00, mleich@five.local.lan +18 -0
  Fix for funcs_1 tests which fail in 5.0.60
  This is basically a backport of changes (only a few were missing)
  which were already pushed to 5.0-build and upmerged to
  5.1-build, 6.0-build

  mysql-test/Makefile.am@1.98, 2008-04-24 17:13:20+02:00, mleich@five.local.lan +2 -2
    Correction for location of loadfiles

  mysql-test/std_data/funcs_1/innodb_tb1.txt@1.2, 2008-04-24 16:37:35+02:00, mleich@five.local.lan +0 -0
    Rename: mysql-test/suite/funcs_1/data/innodb_tb1.txt -> mysql-test/std_data/funcs_1/innodb_tb1.txt

  mysql-test/std_data/funcs_1/innodb_tb2.txt@1.2, 2008-04-24 16:37:35+02:00, mleich@five.local.lan +0 -0
    Rename: mysql-test/suite/funcs_1/data/innodb_tb2.txt -> mysql-test/std_data/funcs_1/innodb_tb2.txt

  mysql-test/std_data/funcs_1/innodb_tb3.txt@1.2, 2008-04-24 16:37:35+02:00, mleich@five.local.lan +0 -0
    Rename: mysql-test/suite/funcs_1/data/innodb_tb3.txt -> mysql-test/std_data/funcs_1/innodb_tb3.txt

  mysql-test/std_data/funcs_1/innodb_tb4.txt@1.2, 2008-04-24 16:37:35+02:00, mleich@five.local.lan +0 -0
    Rename: mysql-test/suite/funcs_1/data/innodb_tb4.txt -> mysql-test/std_data/funcs_1/innodb_tb4.txt

  mysql-test/std_data/funcs_1/load_file.txt@1.1, 2008-04-24 17:13:20+02:00, mleich@five.local.lan +1 -0
    Missing file

  mysql-test/std_data/funcs_1/load_file.txt@1.0, 2008-04-24 17:13:20+02:00, mleich@five.local.lan +0 -0

  mysql-test/std_data/funcs_1/memory_tb1.txt@1.2, 2008-04-24 16:37:35+02:00, mleich@five.local.lan +0 -0
    Rename: mysql-test/suite/funcs_1/data/memory_tb1.txt -> mysql-test/std_data/funcs_1/memory_tb1.txt

  mysql-test/std_data/funcs_1/memory_tb2.txt@1.2, 2008-04-24 16:37:35+02:00, mleich@five.local.lan +0 -0
    Rename: mysql-test/suite/funcs_1/data/memory_tb2.txt -> mysql-test/std_data/funcs_1/memory_tb2.txt

  mysql-test/std_data/funcs_1/memory_tb3.txt@1.2, 2008-04-24 16:37:35+02:00, mleich@five.local.lan +0 -0
    Rename: mysql-test/suite/funcs_1/data/memory_tb3.txt -> mysql-test/std_data/funcs_1/memory_tb3.txt

  mysql-test/std_data/funcs_1/memory_tb4.txt@1.2, 2008-04-24 16:37:35+02:00, mleich@five.local.lan +0 -0
    Rename: mysql-test/suite/funcs_1/data/memory_tb4.txt -> mysql-test/std_data/funcs_1/memory_tb4.txt

  mysql-test/std_data/funcs_1/myisam_tb1.txt@1.2, 2008-04-24 16:37:35+02:00, mleich@five.local.lan +0 -0
    Rename: mysql-test/suite/funcs_1/data/myisam_tb1.txt -> mysql-test/std_data/funcs_1/myisam_tb1.txt

  mysql-test/std_data/funcs_1/myisam_tb2.txt@1.2, 2008-04-24 16:37:35+02:00, mleich@five.local.lan +0 -0
    Rename: mysql-test/suite/funcs_1/data/myisam_tb2.txt -> mysql-test/std_data/funcs_1/myisam_tb2.txt

  mysql-test/std_data/funcs_1/myisam_tb3.txt@1.2, 2008-04-24 16:37:35+02:00, mleich@five.local.lan +0 -0
    Rename: mysql-test/suite/funcs_1/data/myisam_tb3.txt -> mysql-test/std_data/funcs_1/myisam_tb3.txt

  mysql-test/std_data/funcs_1/myisam_tb4.txt@1.2, 2008-04-24 16:37:35+02:00, mleich@five.local.lan +0 -0
    Rename: mysql-test/suite/funcs_1/data/myisam_tb4.txt -> mysql-test/std_data/funcs_1/myisam_tb4.txt

  mysql-test/std_data/funcs_1/t3.txt@1.2, 2008-04-24 16:37:35+02:00, mleich@five.local.lan +0 -0
    Rename: mysql-test/suite/funcs_1/data/t3.txt -> mysql-test/std_data/funcs_1/t3.txt

  mysql-test/std_data/funcs_1/t4.txt@1.2, 2008-04-24 16:37:35+02:00, mleich@five.local.lan +0 -0
    Rename: mysql-test/suite/funcs_1/data/t4.txt -> mysql-test/std_data/funcs_1/t4.txt

  mysql-test/std_data/funcs_1/t7.txt@1.2, 2008-04-24 16:37:35+02:00, mleich@five.local.lan +0 -0
    Rename: mysql-test/suite/funcs_1/data/t7.txt -> mysql-test/std_data/funcs_1/t7.txt

  mysql-test/std_data/funcs_1/t9.txt@1.2, 2008-04-24 16:37:35+02:00, mleich@five.local.lan +0 -0
    Rename: mysql-test/suite/funcs_1/data/t9.txt -> mysql-test/std_data/funcs_1/t9.txt

ChangeSet@1.2611, 2008-04-24 00:06:46+02:00, kent@mysql.com +99 -0
  Many files: [Changes done by mleich]
    Fix for
       Bug#35335 funcs_1: Some tests fail within load_file during
                          pushbuild runs
       Solution: 1. Move files with input data used in load_file,
                    load data etc.
                    from suite/funcs_1/<whatever>
                    to std_data
                 2. Use for testsuite funcs_1 the server option
                    --secure-file-priv=<MYSQLTEST_VARDIR>
                 3. Outfiles have to be stored under MYSQLTEST_VARDIR
    + changes according to WL#4304 Cleanup in funcs_1 tests
      - backport of fixes/improvements made in 5.1 to 5.0
        The differences between scripts in 5.0 and 5.1 cause
        much additional and annoying work during any upmerge.
      - replace error numbers with names
      - improved comments
      - improved formatting
      - Unify storage engine names so that result files for
        storage engine variants do not differ (some tests)
      - remove a script no more used (tests are done in other scripts)

  BUILD/Makefile.am@1.14, 2008-04-24 00:02:51+02:00, kent@mysql.com +8 -0
    Test case adjustments

  mysql-test/Makefile.am@1.97, 2008-04-24 00:02:51+02:00, kent@mysql.com +6 -2
    Test case adjustments

  mysql-test/mysql-test-run.pl@1.256, 2008-04-24 00:02:51+02:00, kent@mysql.com +2 -2
    Test case adjustments

  mysql-test/suite/funcs_1/README.txt@1.4, 2008-04-24 00:02:51+02:00, kent@mysql.com +9 -1
    Test case adjustments

  mysql-test/suite/funcs_1/datadict/datadict_bug_12777.inc@1.2, 2008-04-24 00:02:51+02:00, kent@mysql.com +6 -6
    Test case adjustments

  mysql-test/suite/funcs_1/datadict/datadict_load.inc@1.4, 2008-04-24 00:02:51+02:00, kent@mysql.com +8 -8
    Test case adjustments

  mysql-test/suite/funcs_1/include/innodb_tb1.inc@1.2, 2008-04-24 00:02:51+02:00, kent@mysql.com +60 -59
    Test case adjustments

  mysql-test/suite/funcs_1/include/innodb_tb2.inc@1.2, 2008-04-24 00:02:51+02:00, kent@mysql.com +54 -52
    Test case adjustments

  mysql-test/suite/funcs_1/include/innodb_tb3.inc@1.2, 2008-04-24 00:02:51+02:00, kent@mysql.com +62 -60
    Test case adjustments

  mysql-test/suite/funcs_1/include/innodb_tb4.inc@1.2, 2008-04-24 00:02:51+02:00, kent@mysql.com +54 -52
    Test case adjustments

  mysql-test/suite/funcs_1/include/memory_tb1.inc@1.3, 2008-04-24 00:02:51+02:00, kent@mysql.com +53 -51
    Test case adjustments

  mysql-test/suite/funcs_1/include/memory_tb2.inc@1.3, 2008-04-24 00:02:51+02:00, kent@mysql.com +54 -52
    Test case adjustments

  mysql-test/suite/funcs_1/include/memory_tb3.inc@1.3, 2008-04-24 00:02:51+02:00, kent@mysql.com +56 -55
    Test case adjustments

  mysql-test/suite/funcs_1/include/memory_tb4.inc@1.3, 2008-04-24 00:02:51+02:00, kent@mysql.com +54 -52
    Test case adjustments

  mysql-test/suite/funcs_1/include/myisam_tb1.inc@1.2, 2008-04-24 00:02:51+02:00, kent@mysql.com +60 -58
    Test case adjustments

  mysql-test/suite/funcs_1/include/myisam_tb2.inc@1.2, 2008-04-24 00:02:51+02:00, kent@mysql.com +70 -68
    Test case adjustments

  mysql-test/suite/funcs_1/include/myisam_tb3.inc@1.2, 2008-04-24 00:02:51+02:00, kent@mysql.com +62 -60
    Test case adjustments

  mysql-test/suite/funcs_1/include/myisam_tb4.inc@1.2, 2008-04-24 00:02:51+02:00, kent@mysql.com +69 -67
    Test case adjustments

  mysql-test/suite/funcs_1/include/sp_tb.inc@1.3, 2008-04-24 00:02:51+02:00, kent@mysql.com +54 -29
    Test case adjustments

  mysql-test/suite/funcs_1/r/innodb_func_view.result@1.4, 2008-04-24 00:02:52+02:00, kent@mysql.com +4600 -4374
    Test case adjustments

  mysql-test/suite/funcs_1/r/innodb_storedproc_02.result@1.4, 2008-04-24 00:02:52+02:00, kent@mysql.com +46 -33
    Test case adjustments

  mysql-test/suite/funcs_1/r/innodb_storedproc_03.result@1.4, 2008-04-24 00:02:52+02:00, kent@mysql.com +28 -20
    Test case adjustments

  mysql-test/suite/funcs_1/r/innodb_storedproc_06.result@1.3, 2008-04-24 00:02:52+02:00, kent@mysql.com +31 -20
    Test case adjustments

  mysql-test/suite/funcs_1/r/innodb_storedproc_07.result@1.4, 2008-04-24 00:02:52+02:00, kent@mysql.com +28 -20
    Test case adjustments

  mysql-test/suite/funcs_1/r/innodb_storedproc_08.result@1.4, 2008-04-24 00:02:52+02:00, kent@mysql.com +28 -20
    Test case adjustments

  mysql-test/suite/funcs_1/r/innodb_storedproc_10.result@1.4, 2008-04-24 00:02:52+02:00, kent@mysql.com +121 -36
    Test case adjustments

  mysql-test/suite/funcs_1/r/innodb_trig_0102.result@1.4, 2008-04-24 00:02:52+02:00, kent@mysql.com +93 -92
    Test case adjustments

  mysql-test/suite/funcs_1/r/innodb_trig_03.result@1.3, 2008-04-24 00:02:52+02:00, kent@mysql.com +133 -182
    Test case adjustments

  mysql-test/suite/funcs_1/r/innodb_trig_0407.result@1.3, 2008-04-24 00:02:52+02:00, kent@mysql.com +84 -83
    Test case adjustments

  mysql-test/suite/funcs_1/r/innodb_trig_08.result@1.5, 2008-04-24 00:02:52+02:00, kent@mysql.com +180 -142
    Test case adjustments

  mysql-test/suite/funcs_1/r/innodb_trig_09.result@1.4, 2008-04-24 00:02:52+02:00, kent@mysql.com +81 -79
    Test case adjustments

  mysql-test/suite/funcs_1/r/innodb_trig_1011ext.result@1.3, 2008-04-24 00:02:52+02:00, kent@mysql.com +75 -74
    Test case adjustments

  mysql-test/suite/funcs_1/r/innodb_trig_frkey.result@1.3, 2008-04-24 00:02:52+02:00, kent@mysql.com +60 -59
    Test case adjustments

  mysql-test/suite/funcs_1/r/innodb_views.result@1.7, 2008-04-24 00:02:52+02:00, kent@mysql.com +104 -102
    Test case adjustments

  mysql-test/suite/funcs_1/r/is_columns_innodb.result@1.3, 2008-04-24 00:02:52+02:00, kent@mysql.com +298 -287
    Test case adjustments

  mysql-test/suite/funcs_1/r/is_columns_memory.result@1.3, 2008-04-24 00:02:52+02:00, kent@mysql.com +285 -274
    Test case adjustments

  mysql-test/suite/funcs_1/r/is_columns_myisam.result@1.3, 2008-04-24 00:02:52+02:00, kent@mysql.com +322 -311
    Test case adjustments

  mysql-test/suite/funcs_1/r/is_columns_ndb.result@1.3, 2008-04-24 00:02:52+02:00, kent@mysql.com +24 -18
    Test case adjustments

  mysql-test/suite/funcs_1/r/is_tables_innodb.result@1.3, 2008-04-24 00:02:52+02:00, kent@mysql.com +298 -287
    Test case adjustments

  mysql-test/suite/funcs_1/r/is_tables_memory.result@1.3, 2008-04-24 00:02:52+02:00, kent@mysql.com +285 -274
    Test case adjustments

  mysql-test/suite/funcs_1/r/is_tables_myisam.result@1.3, 2008-04-24 00:02:52+02:00, kent@mysql.com +322 -311
    Test case adjustments

  mysql-test/suite/funcs_1/r/is_tables_ndb.result@1.3, 2008-04-24 00:02:52+02:00, kent@mysql.com +24 -18
    Test case adjustments

  mysql-test/suite/funcs_1/r/memory_func_view.result@1.4, 2008-04-24 00:02:52+02:00, kent@mysql.com +4600 -4374
    Test case adjustments

  mysql-test/suite/funcs_1/r/memory_storedproc_02.result@1.4, 2008-04-24 00:02:52+02:00, kent@mysql.com +46 -33
    Test case adjustments

  mysql-test/suite/funcs_1/r/memory_storedproc_03.result@1.4, 2008-04-24 00:02:52+02:00, kent@mysql.com +28 -20
    Test case adjustments

  mysql-test/suite/funcs_1/r/memory_storedproc_06.result@1.3, 2008-04-24 00:02:52+02:00, kent@mysql.com +31 -20
    Test case adjustments

  mysql-test/suite/funcs_1/r/memory_storedproc_07.result@1.4, 2008-04-24 00:02:52+02:00, kent@mysql.com +28 -20
    Test case adjustments

  mysql-test/suite/funcs_1/r/memory_storedproc_08.result@1.4, 2008-04-24 00:02:52+02:00, kent@mysql.com +28 -20
    Test case adjustments

  mysql-test/suite/funcs_1/r/memory_storedproc_10.result@1.4, 2008-04-24 00:02:52+02:00, kent@mysql.com +121 -36
    Test case adjustments

  mysql-test/suite/funcs_1/r/memory_trig_0102.result@1.4, 2008-04-24 00:02:52+02:00, kent@mysql.com +87 -86
    Test case adjustments

  mysql-test/suite/funcs_1/r/memory_trig_03.result@1.3, 2008-04-24 00:02:52+02:00, kent@mysql.com +127 -176
    Test case adjustments

  mysql-test/suite/funcs_1/r/memory_trig_0407.result@1.3, 2008-04-24 00:02:52+02:00, kent@mysql.com +78 -77
    Test case adjustments

  mysql-test/suite/funcs_1/r/memory_trig_08.result@1.5, 2008-04-24 00:02:52+02:00, kent@mysql.com +174 -136
    Test case adjustments

  mysql-test/suite/funcs_1/r/memory_trig_09.result@1.4, 2008-04-24 00:02:52+02:00, kent@mysql.com +75 -73
    Test case adjustments

  mysql-test/suite/funcs_1/r/memory_trig_1011ext.result@1.3, 2008-04-24 00:02:52+02:00, kent@mysql.com +69 -68
    Test case adjustments

  mysql-test/suite/funcs_1/r/memory_views.result@1.7, 2008-04-24 00:02:52+02:00, kent@mysql.com +104 -102
    Test case adjustments

  mysql-test/suite/funcs_1/r/myisam_func_view.result@1.4, 2008-04-24 00:02:52+02:00, kent@mysql.com +4600 -4374
    Test case adjustments

  mysql-test/suite/funcs_1/r/myisam_storedproc_02.result@1.4, 2008-04-24 00:02:52+02:00, kent@mysql.com +46 -33
    Test case adjustments

  mysql-test/suite/funcs_1/r/myisam_storedproc_03.result@1.4, 2008-04-24 00:02:52+02:00, kent@mysql.com +28 -20
    Test case adjustments

  mysql-test/suite/funcs_1/r/myisam_storedproc_06.result@1.3, 2008-04-24 00:02:52+02:00, kent@mysql.com +31 -20
    Test case adjustments

  mysql-test/suite/funcs_1/r/myisam_storedproc_07.result@1.4, 2008-04-24 00:02:52+02:00, kent@mysql.com +28 -20
    Test case adjustments

  mysql-test/suite/funcs_1/r/myisam_storedproc_08.result@1.4, 2008-04-24 00:02:52+02:00, kent@mysql.com +28 -20
    Test case adjustments

  mysql-test/suite/funcs_1/r/myisam_storedproc_10.result@1.4, 2008-04-24 00:02:52+02:00, kent@mysql.com +121 -36
    Test case adjustments

  mysql-test/suite/funcs_1/r/myisam_trig_0102.result@1.4, 2008-04-24 00:02:52+02:00, kent@mysql.com +93 -92
    Test case adjustments

  mysql-test/suite/funcs_1/r/myisam_trig_03.result@1.3, 2008-04-24 00:02:52+02:00, kent@mysql.com +133 -182
    Test case adjustments

  mysql-test/suite/funcs_1/r/myisam_trig_0407.result@1.3, 2008-04-24 00:02:52+02:00, kent@mysql.com +84 -83
    Test case adjustments

  mysql-test/suite/funcs_1/r/myisam_trig_08.result@1.5, 2008-04-24 00:02:52+02:00, kent@mysql.com +180 -142
    Test case adjustments

  mysql-test/suite/funcs_1/r/myisam_trig_09.result@1.4, 2008-04-24 00:02:52+02:00, kent@mysql.com +81 -79
    Test case adjustments

  mysql-test/suite/funcs_1/r/myisam_trig_1011ext.result@1.3, 2008-04-24 00:02:52+02:00, kent@mysql.com +75 -74
    Test case adjustments

  mysql-test/suite/funcs_1/r/myisam_views.result@1.7, 2008-04-24 00:02:53+02:00, kent@mysql.com +11403 -11406
    Test case adjustments

  mysql-test/suite/funcs_1/storedproc/cleanup_sp_tb.inc@1.2, 2008-04-24 00:02:53+02:00, kent@mysql.com +3 -2
    Test case adjustments

  mysql-test/suite/funcs_1/storedproc/load_sp_tb.inc@1.3, 2008-04-24 00:02:53+02:00, kent@mysql.com +80 -41
    Test case adjustments

  mysql-test/suite/funcs_1/storedproc/storedproc_02.inc@1.3, 2008-04-24 00:02:53+02:00, kent@mysql.com +236 -112
    Test case adjustments

  mysql-test/suite/funcs_1/storedproc/storedproc_03.inc@1.3, 2008-04-24 00:02:53+02:00, kent@mysql.com +59 -27
    Test case adjustments

  mysql-test/suite/funcs_1/storedproc/storedproc_06.inc@1.3, 2008-04-24 00:02:53+02:00, kent@mysql.com +41 -28
    Test case adjustments

  mysql-test/suite/funcs_1/storedproc/storedproc_10.inc@1.3, 2008-04-24 00:02:53+02:00, kent@mysql.com +76 -33
    Test case adjustments

  mysql-test/suite/funcs_1/t/innodb_trig_0407.test@1.3, 2008-04-24 00:02:53+02:00, kent@mysql.com +1 -1
    Test case adjustments

  mysql-test/suite/funcs_1/t/is_basics_mixed.test@1.2, 2008-04-24 00:02:53+02:00, kent@mysql.com +1 -1
    Test case adjustments

  mysql-test/suite/funcs_1/t/memory_storedproc_02.test@1.3, 2008-04-24 00:02:53+02:00, kent@mysql.com +2 -2
    Test case adjustments

  mysql-test/suite/funcs_1/t/memory_storedproc_03.test@1.3, 2008-04-24 00:02:53+02:00, kent@mysql.com +2 -2
    Test case adjustments

  mysql-test/suite/funcs_1/t/memory_storedproc_06.test@1.3, 2008-04-24 00:02:53+02:00, kent@mysql.com +2 -2
    Test case adjustments

  mysql-test/suite/funcs_1/t/memory_storedproc_07.test@1.3, 2008-04-24 00:02:53+02:00, kent@mysql.com +2 -2
    Test case adjustments

  mysql-test/suite/funcs_1/t/memory_storedproc_08.test@1.3, 2008-04-24 00:02:53+02:00, kent@mysql.com +2 -2
    Test case adjustments

  mysql-test/suite/funcs_1/t/memory_storedproc_10.test@1.3, 2008-04-24 00:02:53+02:00, kent@mysql.com +2 -2
    Test case adjustments

  mysql-test/suite/funcs_1/t/myisam_storedproc_02.test@1.3, 2008-04-24 00:02:53+02:00, kent@mysql.com +2 -2
    Test case adjustments

  mysql-test/suite/funcs_1/t/myisam_storedproc_03.test@1.3, 2008-04-24 00:02:53+02:00, kent@mysql.com +2 -2
    Test case adjustments

  mysql-test/suite/funcs_1/t/myisam_storedproc_06.test@1.3, 2008-04-24 00:02:53+02:00, kent@mysql.com +2 -2
    Test case adjustments

  mysql-test/suite/funcs_1/t/myisam_storedproc_07.test@1.3, 2008-04-24 00:02:53+02:00, kent@mysql.com +2 -2
    Test case adjustments

  mysql-test/suite/funcs_1/t/myisam_storedproc_08.test@1.3, 2008-04-24 00:02:53+02:00, kent@mysql.com +2 -2
    Test case adjustments

  mysql-test/suite/funcs_1/t/myisam_storedproc_10.test@1.3, 2008-04-24 00:02:53+02:00, kent@mysql.com +2 -2
    Test case adjustments

  mysql-test/suite/funcs_1/triggers/trig_frkey2.inc@1.2, 2008-04-24 00:02:53+02:00, kent@mysql.com +51 -51
    Test case adjustments

  mysql-test/suite/funcs_1/triggers/triggers_0102.inc@1.3, 2008-04-24 00:02:53+02:00, kent@mysql.com +114 -114
    Test case adjustments

  mysql-test/suite/funcs_1/triggers/triggers_03.inc@1.2, 2008-04-24 00:02:53+02:00, kent@mysql.com +49 -126
    Test case adjustments

  mysql-test/suite/funcs_1/triggers/triggers_0407.inc@1.2, 2008-04-24 00:02:53+02:00, kent@mysql.com +109 -109
    Test case adjustments

  mysql-test/suite/funcs_1/triggers/triggers_08.inc@1.2, 2008-04-24 00:02:53+02:00, kent@mysql.com +150 -129
    Test case adjustments

  mysql-test/suite/funcs_1/triggers/triggers_09.inc@1.2, 2008-04-24 00:02:53+02:00, kent@mysql.com +76 -78
    Test case adjustments

  mysql-test/suite/funcs_1/triggers/triggers_1011ext.inc@1.2, 2008-04-24 00:02:53+02:00, kent@mysql.com +21 -21
    Test case adjustments

  mysql-test/suite/funcs_1/views/func_view.inc@1.3, 2008-04-24 00:02:53+02:00, kent@mysql.com +111 -163
    Test case adjustments

  mysql-test/suite/funcs_1/views/views_master.inc@1.5, 2008-04-24 00:02:53+02:00, kent@mysql.com +3 -3
    Test case adjustments

ChangeSet@1.2610, 2008-04-01 12:29:53+02:00, mkindahl@dl145h.mysql.com +1 -0
  Post-merge fixes.
  TAG: clone-5.0.60-build

  mysql-test/r/binlog_index.result@1.2, 2008-04-01 12:29:48+02:00, mkindahl@dl145h.mysql.com +2 -2
    Result set change.

ChangeSet@1.2598.1.2, 2008-03-31 16:32:45+02:00, mkindahl@dl145h.mysql.com +2 -0
  Removing race conditions from rpl_packet causing test to fail.

  mysql-test/r/rpl_packet.result@1.6, 2008-03-31 16:32:41+02:00, mkindahl@dl145h.mysql.com +4 -0
    Result change.

  mysql-test/t/rpl_packet.test@1.7, 2008-03-31 16:32:41+02:00, mkindahl@dl145h.mysql.com +15 -1
    Setting net_buffer_length correctly for the test instead of relying on it
    being set correctly. Waiting for slave to stop after issuing a SLAVE STOP
    and waiting for slave to start when issuing a SLAVE START to prevent race
    conditions causing test failure.

ChangeSet@1.2608, 2008-03-30 15:46:37-04:00, iggy@amd64.(none) +1 -0
  Bug#26243 - Cleanup Valgrind error

  sql/tztime.cc@1.43, 2008-03-30 15:46:35-04:00, iggy@amd64.(none) +1 -1
    Bug#26243 - Cleanup Valgrind error

ChangeSet@1.2607, 2008-03-29 17:50:46+02:00, gkodinov@macbook.gmz +7 -0
  fixed warnings from the fix of 26243

  myisam/mi_check.c@1.159, 2008-03-29 17:50:43+02:00, gkodinov@macbook.gmz +1 -1
    fixed warnings from the fix of 26243

  myisam/mi_keycache.c@1.13, 2008-03-29 17:50:43+02:00, gkodinov@macbook.gmz +1 -0
    fixed warnings from the fix of 26243

  mysys/mf_keycache.c@1.66, 2008-03-29 17:50:43+02:00, gkodinov@macbook.gmz +1 -1
    fixed warnings from the fix of 26243

  sql/examples/ha_tina.cc@1.31, 2008-03-29 17:50:44+02:00, gkodinov@macbook.gmz +1 -1
    fixed warnings from the fix of 26243

  sql/item_func.cc@1.369, 2008-03-29 17:50:43+02:00, gkodinov@macbook.gmz +1 -1
    fixed warnings from the fix of 26243

  sql/lock.cc@1.101, 2008-03-29 17:50:43+02:00, gkodinov@macbook.gmz +1 -1
    fixed warnings from the fix of 26243

  sql/sql_analyse.cc@1.73, 2008-03-29 17:50:43+02:00, gkodinov@macbook.gmz +12 -12
    fixed warnings from the fix of 26243

ChangeSet@1.2606, 2008-03-29 16:12:23+02:00, gkodinov@macbook.gmz +4 -0
  fixes for warnings and compile errors for the fix of bug 26243

  extra/charset2html.c@1.10, 2008-03-29 16:12:21+02:00, gkodinov@macbook.gmz +2 -0
    fixes for warnings and compile errors for the fix of bug 26243

  sql/ha_berkeley.cc@1.169, 2008-03-29 16:12:21+02:00, gkodinov@macbook.gmz +4 -4
    fixes for warnings and compile errors for the fix of bug 26243

  sql/mysqld.cc@1.640, 2008-03-29 16:12:21+02:00, gkodinov@macbook.gmz +1 -1
    fixes for warnings and compile errors for the fix of bug 26243

  sql/sql_union.cc@1.145, 2008-03-29 16:12:21+02:00, gkodinov@macbook.gmz +2 -0
    fixes for warnings and compile errors for the fix of bug 26243

ChangeSet@1.2605, 2008-03-29 09:52:16+02:00, gkodinov@macbook.gmz +27 -0
  fixed warnings and compile errors from the fix for bug 26243

  configure.in@1.476, 2008-03-29 09:52:01+02:00, gkodinov@macbook.gmz +3 -0
    fixed warnings and compile errors from the fix for bug 26243

  heap/hp_test2.c@1.25, 2008-03-29 09:52:01+02:00, gkodinov@macbook.gmz +0 -2
    fixed warnings and compile errors from the fix for bug 26243

  libmysql/libmysql.c@1.254, 2008-03-29 09:52:01+02:00, gkodinov@macbook.gmz +1 -1
    fixed warnings and compile errors from the fix for bug 26243

  myisam/mi_check.c@1.158, 2008-03-29 09:52:02+02:00, gkodinov@macbook.gmz +10 -10
    fixed warnings and compile errors from the fix for bug 26243

  myisam/mi_delete.c@1.45, 2008-03-29 09:52:02+02:00, gkodinov@macbook.gmz +11 -11
    fixed warnings and compile errors from the fix for bug 26243

  myisam/mi_dynrec.c@1.51, 2008-03-29 09:52:02+02:00, gkodinov@macbook.gmz +3 -3
    fixed warnings and compile errors from the fix for bug 26243

  myisam/mi_key.c@1.57, 2008-03-29 09:52:02+02:00, gkodinov@macbook.gmz +1 -1
    fixed warnings and compile errors from the fix for bug 26243

  myisam/mi_open.c@1.113, 2008-03-29 09:52:02+02:00, gkodinov@macbook.gmz +1 -1
    fixed warnings and compile errors from the fix for bug 26243

  myisam/mi_packrec.c@1.46, 2008-03-29 09:52:02+02:00, gkodinov@macbook.gmz +1 -1
    fixed warnings and compile errors from the fix for bug 26243

  myisam/mi_page.c@1.27, 2008-03-29 09:52:02+02:00, gkodinov@macbook.gmz +2 -2
    fixed warnings and compile errors from the fix for bug 26243

  myisam/mi_search.c@1.66, 2008-03-29 09:52:02+02:00, gkodinov@macbook.gmz +4 -4
    fixed warnings and compile errors from the fix for bug 26243

  myisam/mi_statrec.c@1.16, 2008-03-29 09:52:02+02:00, gkodinov@macbook.gmz +2 -2
    fixed warnings and compile errors from the fix for bug 26243

  myisam/mi_test1.c@1.31, 2008-03-29 09:52:02+02:00, gkodinov@macbook.gmz +0 -1
    fixed warnings and compile errors from the fix for bug 26243

  myisam/mi_test2.c@1.33, 2008-03-29 09:52:02+02:00, gkodinov@macbook.gmz +2 -4
    fixed warnings and compile errors from the fix for bug 26243

  myisam/mi_test3.c@1.19, 2008-03-29 09:52:02+02:00, gkodinov@macbook.gmz +0 -2
    fixed warnings and compile errors from the fix for bug 26243

  myisam/mi_write.c@1.64, 2008-03-29 09:52:03+02:00, gkodinov@macbook.gmz +4 -4
    fixed warnings and compile errors from the fix for bug 26243

  myisammrg/myrg_rkey.c@1.22, 2008-03-29 09:52:03+02:00, gkodinov@macbook.gmz +1 -1
    fixed warnings and compile errors from the fix for bug 26243

  ndb/src/ndbapi/DictCache.cpp@1.23, 2008-03-29 09:52:03+02:00, gkodinov@macbook.gmz +1 -1
    fixed warnings and compile errors from the fix for bug 26243

  ndb/src/ndbapi/NdbBlob.cpp@1.37, 2008-03-29 09:52:03+02:00, gkodinov@macbook.gmz +5 -3
    fixed warnings and compile errors from the fix for bug 26243

  ndb/src/ndbapi/NdbOperationDefine.cpp@1.28, 2008-03-29 09:52:03+02:00, gkodinov@macbook.gmz +1 -1
    fixed warnings and compile errors from the fix for bug 26243

  ndb/src/ndbapi/NdbOperationInt.cpp@1.18, 2008-03-29 09:52:03+02:00, gkodinov@macbook.gmz +1 -1
    fixed warnings and compile errors from the fix for bug 26243

  ndb/src/ndbapi/NdbOperationSearch.cpp@1.32, 2008-03-29 09:52:03+02:00, gkodinov@macbook.gmz +1 -1
    fixed warnings and compile errors from the fix for bug 26243

  sql-common/client.c@1.122, 2008-03-29 09:52:04+02:00, gkodinov@macbook.gmz +1 -1
    fixed warnings and compile errors from the fix for bug 26243

  sql/ha_federated.cc@1.91, 2008-03-29 09:52:03+02:00, gkodinov@macbook.gmz +1 -1
    fixed warnings and compile errors from the fix for bug 26243

  sql/ha_innodb.cc@1.325, 2008-03-29 09:52:03+02:00, gkodinov@macbook.gmz +1 -1
    fixed warnings and compile errors from the fix for bug 26243

  sql/ha_ndbcluster.cc@1.322, 2008-03-29 09:52:04+02:00, gkodinov@macbook.gmz +16 -18
    fixed warnings and compile errors from the fix for bug 26243

  sql/ha_ndbcluster_cond.cc@1.8, 2008-03-29 09:52:04+02:00, gkodinov@macbook.gmz +1 -1
    fixed warnings and compile errors from the fix for bug 26243

ChangeSet@1.2602.1.1, 2008-03-28 23:39:47+03:00, anozdrin@quad.opbmk +3 -0
  Fix tree:
    1. Use 'dat' extension, because it is handled in Makefile.am;
    2. Fix typo: the bug id is 35469, not 35649.

  mysql-test/r/loaddata.result@1.34, 2008-03-28 23:39:47+03:00, anozdrin@quad.opbmk +4 -4
    Update result file.

  mysql-test/std_data/bug35469.dat@1.2, 2008-03-28 23:37:48+03:00, anozdrin@quad.opbmk +0 -0
    Rename: mysql-test/std_data/bug35649.data -> mysql-test/std_data/bug35469.dat

  mysql-test/t/loaddata.test@1.29, 2008-03-28 23:39:47+03:00, anozdrin@quad.opbmk +4 -4
    1. Use 'dat' extension, because it is handled in Makefile.am;
    2. Fix typo: the bug id is 35469, not 35649.

ChangeSet@1.2572.24.2, 2008-03-28 14:02:27-04:00, iggy@amd64.(none) +19 -0
  Bug#26243 mysql command line crash after control-c
  - Backported the 5.1 DBUG to 5.0.
  - Avoid memory cleanup race on Windows client for CTRL-C

  client/mysql.cc@1.250, 2008-03-28 14:02:22-04:00, iggy@amd64.(none) +19 -5
    Bug#26243 mysql command line crash after control-c
    - On Windows, the sigint handler shouldn't call mysql_end
    because the main thread will do so automatically.
    - Remove unnecessary signal call from the sigint handler.
    - Call my_end with proper value.

  dbug/dbug.c@1.25, 2008-03-28 14:02:22-04:00, iggy@amd64.(none) +1466 -1247
    Bug#26243 mysql command line crash after control-c
    - Backported the 5.1 DBUG library. The old version uses a non-thread 
    safe global variable 'static struct state *stack'.

  dbug/factorial.c@1.5, 2008-03-28 14:02:22-04:00, iggy@amd64.(none) +12 -2
    Bug#26243 mysql command line crash after control-c
    - Backported the 5.1 DBUG library. The old version uses a non-thread 
    safe global variable 'static struct state *stack'.

  dbug/user.r@1.7, 2008-03-28 14:02:22-04:00, iggy@amd64.(none) +185 -112
    Bug#26243 mysql command line crash after control-c
    - Backported the 5.1 DBUG library. The old version uses a non-thread 
    safe global variable 'static struct state *stack'.

  include/my_dbug.h@1.23, 2008-03-28 14:02:22-04:00, iggy@amd64.(none) +52 -44
    Bug#26243 mysql command line crash after control-c
    - Backported the 5.1 DBUG library. The old version uses a non-thread 
    safe global variable 'static struct state *stack'.

  libmysql/libmysql.c@1.251.1.1, 2008-03-28 14:02:22-04:00, iggy@amd64.(none) +0 -4
    Bug#26243 mysql command line crash after control-c
    - Update for new DBUG library.

  myisam/mi_open.c@1.109.1.1, 2008-03-28 14:02:23-04:00, iggy@amd64.(none) +1 -1
    Bug#26243 mysql command line crash after control-c
    - Update for new DBUG library.

  sql/ha_federated.cc@1.86.1.1, 2008-03-28 14:02:23-04:00, iggy@amd64.(none) +1 -1
    Bug#26243 mysql command line crash after control-c
    - Update for new DBUG library.

  sql/ha_innodb.cc@1.324, 2008-03-28 14:02:23-04:00, iggy@amd64.(none) +1 -1
    Bug#26243 mysql command line crash after control-c
    - Update for new DBUG library.

  sql/ha_myisammrg.cc@1.92.1.1, 2008-03-28 14:02:23-04:00, iggy@amd64.(none) +1 -1
    Bug#26243 mysql command line crash after control-c
    - Update for new DBUG library.

  sql/item_cmpfunc.cc@1.274, 2008-03-28 14:02:23-04:00, iggy@amd64.(none) +1 -1
    Bug#26243 mysql command line crash after control-c
    - Update for new DBUG library.

  sql/mysqld.cc@1.639, 2008-03-28 14:02:23-04:00, iggy@amd64.(none) +4 -9
    Bug#26243 mysql command line crash after control-c
    - Update for new DBUG library.

  sql/net_serv.cc@1.104, 2008-03-28 14:02:23-04:00, iggy@amd64.(none) +2 -2
    Bug#26243 mysql command line crash after control-c
    - Update for new DBUG library.

  sql/opt_range.cc@1.258, 2008-03-28 14:02:23-04:00, iggy@amd64.(none) +1 -5
    Bug#26243 mysql command line crash after control-c
    - Update for new DBUG library.

  sql/set_var.cc@1.198, 2008-03-28 14:02:23-04:00, iggy@amd64.(none) +1 -1
    Bug#26243 mysql command line crash after control-c
    - Update for new DBUG library.

  sql/slave.cc@1.305.2.1, 2008-03-28 14:02:23-04:00, iggy@amd64.(none) +1 -1
    Bug#26243 mysql command line crash after control-c
    - Update for new DBUG library.

  sql/sql_cache.cc@1.110, 2008-03-28 14:02:23-04:00, iggy@amd64.(none) +3 -3
    Bug#26243 mysql command line crash after control-c
    - Update for new DBUG library.

  sql/sql_select.cc@1.558.2.1, 2008-03-28 14:02:23-04:00, iggy@amd64.(none) +1 -1
    Bug#26243 mysql command line crash after control-c
    - Update for new DBUG library.

  tests/mysql_client_test.c@1.249.1.4, 2008-03-28 14:02:23-04:00, iggy@amd64.(none) +0 -1
    Bug#26243 mysql command line crash after control-c
    - Update for new DBUG library.

ChangeSet@1.2600.1.1, 2008-03-28 18:59:13+03:00, anozdrin@quad.opbmk +5 -0
  Fix for Bug#35469: server crash with LOAD DATA INFILE to a VIEW.
  
  The problem was that LOAD DATA code (sql_load.cc) didn't take into
  account that there may be items, representing references to other
  columns. This is a usual case in views. The crash happened because
  Item_direct_view_ref was casted to Item_user_var_as_out_param,
  which is not a base class.
  
  The fix is to
    1) Handle references properly;
    2) Ensure that an item is treated as a user variable only when
       it is a user variable indeed;
    3) Report an error if LOAD DATA is used to load data into
       non-updatable column.

  mysql-test/r/loaddata.result@1.33, 2008-03-28 18:59:13+03:00, anozdrin@quad.opbmk +76 -0
    Update result file.

  mysql-test/std_data/bug35649.data@1.1, 2008-03-28 18:59:13+03:00, anozdrin@quad.opbmk +3 -0
    Add a data file for the test case.

  mysql-test/std_data/bug35649.data@1.0, 2008-03-28 18:59:13+03:00, anozdrin@quad.opbmk +0 -0

  mysql-test/t/loaddata.test@1.28, 2008-03-28 18:59:13+03:00, anozdrin@quad.opbmk +82 -0
    Add a test case form Bug#35469: server crash with
    LOAD DATA INFILE to a VIEW.

  sql/share/errmsg.txt@1.82.1.1, 2008-03-28 18:59:13+03:00, anozdrin@quad.opbmk +4 -0
    Introduce a new error.

  sql/sql_load.cc@1.120, 2008-03-28 18:59:13+03:00, anozdrin@quad.opbmk +42 -14
    Handle reference-items properly.

ChangeSet@1.1616.3132.2, 2008-03-28 14:27:22+01:00, mattiasj@witty. +1 -0
  Bug#21413 - Engine table handler used by multiple threads
              in REPLACE DELAYED
      
  post push patch, removing the optimization for
  copying delayed_insert variables.

  sql/sql_insert.cc@1.86.27.4, 2008-03-28 14:27:21+01:00, mattiasj@witty. +2 -3
    Bug#21413 - Engine table handler used by multiple threads
                in REPLACE DELAYED
    
    post push patch, removing the optimization for
    copying delayed_insert variables.
    (restored some parts which caused errors)

ChangeSet@1.2567.26.6, 2008-03-27 19:49:32+03:00, evgen@moonbone.local +10 -0
  Bug#27219: Aggregate functions in ORDER BY.
  
  Mixing aggregate functions and non-grouping columns is not allowed in the
  ONLY_FULL_GROUP_BY mode. However in some cases the error wasn't thrown because
  of insufficient check.
  
  In order to check more thoroughly the new algorithm employs a list of outer
  fields used in a sum function and a SELECT_LEX::full_group_by_flag.
  Each non-outer field checked to find out whether it's aggregated or not and
  the current select is marked accordingly.
  All outer fields that are used under an aggregate function are added to the
  Item_sum::outer_fields list and later checked by the Item_sum::check_sum_func
  function.

  mysql-test/r/group_by.result@1.83, 2008-03-27 19:49:15+03:00, evgen@moonbone.local +146 -0
    Added a test case for the bug#27219: Aggregate functions in ORDER BY.

  mysql-test/t/group_by.test@1.68, 2008-03-27 19:49:13+03:00, evgen@moonbone.local +117 -0
    Added a test case for the bug#27219: Aggregate functions in ORDER BY.

  sql/item.cc@1.302.1.1, 2008-03-27 19:49:19+03:00, evgen@moonbone.local +24 -4
    Bug#27219: Aggregate functions in ORDER BY.
    Now the Item_field::fix_fields function checks whether the field is aggregated
    or not and marks its select_lex accordingly.

  sql/item_subselect.cc@1.162.1.1, 2008-03-27 19:49:18+03:00, evgen@moonbone.local +14 -0
    Bug#27219: Aggregate functions in ORDER BY.
    The Item_in_subselect::select_in_like_transformer function now drops
    ORDER BY clause in all selects in a subquery.

  sql/item_sum.cc@1.220.1.1, 2008-03-27 19:49:18+03:00, evgen@moonbone.local +64 -0
    Bug#27219: Aggregate functions in ORDER BY.
    Now the Item_sum::check_sum_func function now checks whether fields in the
    outer_fields list are aggregated or not and marks selects accordingly.

  sql/item_sum.h@1.115, 2008-03-27 19:49:17+03:00, evgen@moonbone.local +7 -0
    Bug#27219: Aggregate functions in ORDER BY.
    The outer_fields list is added to the Item_sum class.

  sql/mysql_priv.h@1.468.1.1, 2008-03-27 19:49:17+03:00, evgen@moonbone.local +7 -0
    Bug#27219: Aggregate functions in ORDER BY.
    Defined a set of constants used in the new check for mixing non aggregated
    fields and sum functions in the ONLY_FULL_GROUP_BY_MODE.

  sql/sql_lex.cc@1.232, 2008-03-27 19:49:16+03:00, evgen@moonbone.local +1 -2
    Bug#27219: Aggregate functions in ORDER BY.
    Initialization of the full_group_by_flag bitmap.
    SELECT_LEX::test_limit function doesn't reset ORDER BY
    clause anymore.
    

  sql/sql_lex.h@1.255, 2008-03-27 19:49:16+03:00, evgen@moonbone.local +10 -1
    Bug#27219: Aggregate functions in ORDER BY.
    The full_group_by_flag is added to the SELECT_LEX class.

  sql/sql_select.cc@1.558.1.1, 2008-03-27 19:49:15+03:00, evgen@moonbone.local +5 -29
    Bug#27219: Aggregate functions in ORDER BY.
    Implementation of new check for mixing non aggregated fields and aggregation
    function in the ONLY_FULL_GROUP_BY mode.

ChangeSet@1.2572.25.3, 2008-03-27 09:37:20-03:00, davi@mysql.com +2 -0
  Patch clean up.
  Fixed interference between tests: Users were added but not properly removed.
  This caused later tests to fail.

  mysql-test/r/grant.result@1.72, 2008-03-27 09:37:18-03:00, davi@mysql.com +2 -2
    Fixed interference between tests: Users were added but not properly removed.
    This caused later tests to fail.

  mysql-test/t/grant.test@1.61, 2008-03-27 09:37:19-03:00, davi@mysql.com +2 -2
    Fixed interference between tests: Users were added but not properly removed.
    This caused later tests to fail.

ChangeSet@1.2595.1.1, 2008-03-27 13:02:59+01:00, df@pippilotta.erinye.com +1 -0
  BUG#25340

  win/configure.js@1.9, 2008-03-27 13:02:57+01:00, df@pippilotta.erinye.com +2 -0
    BUG#25340

ChangeSet@1.2572.1.30, 2008-03-27 13:42:34+08:00, hezx@mail.hezx.com +6 -0
  post fix after push of BUG#33029

  mysql-test/r/binlog_killed_simulate.result@1.2, 2008-03-27 13:42:30+08:00, hezx@mail.hezx.com +3 -3
    Update test result after push of bug#33029

  mysql-test/r/mix_innodb_myisam_binlog.result@1.41, 2008-03-27 13:42:30+08:00, hezx@mail.hezx.com +93 -93
    Update test result after push of bug#33029

  mysql-test/r/multi_update.result@1.50, 2008-03-27 13:42:30+08:00, hezx@mail.hezx.com +2 -2
    Update test result after push of bug#33029

  mysql-test/r/rpl_auto_increment_bug33029.result@1.2, 2008-03-27 13:42:30+08:00, hezx@mail.hezx.com +0 -2
    disable warning messages

  mysql-test/r/rpl_user.result@1.3, 2008-03-27 13:42:30+08:00, hezx@mail.hezx.com +7 -7
    Update test result after push of bug#33029

  mysql-test/t/rpl_auto_increment_bug33029.test@1.2, 2008-03-27 13:42:30+08:00, hezx@mail.hezx.com +2 -0
    disable warning messages

ChangeSet@1.1616.3132.1, 2008-03-27 01:13:39+01:00, mattiasj@witty. +1 -0
  Recommit of antonys previous commit.
  
  Bug#21413
  "Engine table handler used by multiple threads in REPLACE DELAYED"
  When executing a REPLACE DELAYED statement, the storage engine
  ::extra() method was invoked by a different thread than the thread
  which has acquired the handler instance.
  
  This did not cause problems within the current server and with
  the current storage engines.
  But it has the potential to confuse future storage engines.
  
  Added code to avoid surplus calls to extra() method in case of DELAYED
  which avoids calling storage engine from a different thread than
  expected.
  
  No test case.
  This change does not change behavior in conjunction with current
  storage engines. So it cannot be tested by the regression test suite.

  sql/sql_insert.cc@1.86.27.3, 2008-03-27 01:13:38+01:00, mattiasj@witty. +30 -14
    Bug#21413
    When performing DELAYED operations, we should not call
    the storage engine methods from the 'wrong' context.
    Ensure that the calls to the methods are appropiately guarded
    by either moving calls to sections where the lock_type is checked.
    No need to copy all elements of TABLE_LIST when opening table
    using open_ltable().

ChangeSet@1.2572.23.1, 2008-03-26 22:43:12+04:00, gshchepa@host.loc +3 -0
  Fixed bug #35193.
  View definition as SELECT ... FROM DUAL WHERE ... has
  valid syntax, but use of such view in SELECT or
  SHOW CREATE VIEW syntax causes unexpected syntax error.
  
  Server omits FROM DUAL clause when storing view body
  string in a .frm file for further evaluation.
  However, syntax of SELECT-witout-FROM query is more
  restrictive than SELECT FROM DUAL syntax, and doesn't
  allow the WHERE clause.
  
  NOTE: this syntax difference is not documented.
  
  
  View registration procedure has been modified to
  preserve original structure of view's body.
  

  mysql-test/r/view.result@1.215, 2008-03-26 22:09:59+04:00, gshchepa@host.loc +18 -0
    Added test case for bug #35193.

  mysql-test/t/view.test@1.195, 2008-03-26 22:09:59+04:00, gshchepa@host.loc +23 -0
    Added test case for bug #35193.

  sql/sql_select.cc@1.559, 2008-03-26 22:10:00+04:00, gshchepa@host.loc +8 -0
    Fixed bug #35193.
    The st_select_lex::print function always omits FROM DUAL clause,
    even if original SELECT query has the WHERE clause.
    
    The mysql_register_view function uses this function to reconstruct
    a body of view's AS clause for further evaluation and stores that
    reconstructed clause in a .frm file.
    
    SELECT without FROM syntax is more restrictive than 
    SELECT FROM DUAL syntax: second one allows
    the WHERE clause, but first one is not.
    
    Use of this view in SELECT or SHOW CREATE VIEW queries
    causes unexpected syntax errors.
    
    
    The st_select_lex::print function has been modified to
    reconstruct FROM DUAL clause in queries when needed.
    
    
    TODO: Syntax difference is not documented and should be
    eliminated, however improvement of
    the SELECT-without-FROM syntax is not trivial and leads to
    significant modification of grammar file because of additional
    shift/reduce conflicts.

ChangeSet@1.2572.18.7, 2008-03-25 11:20:11-06:00, malff@lambda.hsd1.co.comcast.net. +2 -0
  Bug#20906 (Multiple assignments in SET in stored routine produce incorrect
  instructions)
  
  This bug can not be reproduced in the current version,
  adding the test case to the test suite for coverage, no code change.

  mysql-test/r/sp-code.result@1.13, 2008-03-25 11:20:08-06:00, malff@lambda.hsd1.co.comcast.net. +28 -0
    Bug#20906 (Multiple assignments in SET in stored routine produce incorrect
    instructions)

  mysql-test/t/sp-code.test@1.10, 2008-03-25 11:20:08-06:00, malff@lambda.hsd1.co.comcast.net. +32 -0
    Bug#20906 (Multiple assignments in SET in stored routine produce incorrect
    instructions)

ChangeSet@1.2572.18.6, 2008-03-25 19:44:27+04:00, gshchepa@host.loc +2 -0
  information_schema.test, information_schema.result:
    Minor test case cleanup after bug#34529.

  mysql-test/r/information_schema.result@1.130, 2008-03-25 19:30:52+04:00, gshchepa@host.loc +2 -1
    Minor test case cleanup after bug#34529.

  mysql-test/t/information_schema.test@1.99, 2008-03-25 19:43:31+04:00, gshchepa@host.loc +4 -2
    Minor test case cleanup after bug#34529.

ChangeSet@1.2572.13.6, 2008-03-25 12:47:57+04:00, svoj@mysql.com +2 -0
  BUG#35509 - Federated leaks memory when connecting to
              localhost/default port
  
  When creating federated table that points to unspecified host or
  localhost on unspecified port or port is 0, small memory leak occurs.
  
  This happens because we make a copy of unix socket path, which is
  never freed.
  
  With this fix we do not make a copy of unix socket path, instead
  share->socket points to MYSQL_UNIX_ADDR constant directly.
  
  This fix is covered by a test case for BUG34788.
  
  Affects 5.0 only.

  mysql-test/t/federated.test@1.44, 2008-03-25 12:47:55+04:00, svoj@mysql.com +5 -0
    A test case for BUG#35509.

  sql/ha_federated.cc@1.89, 2008-03-25 12:47:55+04:00, svoj@mysql.com +1 -2
    When creating federated table we call parse_url() to check if connect
    string is correct. parse_url() may make a copy of unix socket path if
    port is not specified or 0 and host is not specified or 'localhost'.
    This copy is never freed.
    
    As there is no need to make a copy of unix socket path, let
    share->socket point to MYSQL_UNIX_ADDR directly.

ChangeSet@1.2572.20.1, 2008-03-21 17:23:17+02:00, gkodinov@macbook.gmz +17 -0
  Bug #26461: Intrinsic data type bool (1 byte) redefined to BOOL (4 bytes)
  
  The bool data type was redefined to BOOL (4 bytes on windows).
  Removed the #define and fixed some of the warnings that were uncovered
  by this.
  Note that the fix also disables 2 warnings :
  4800 : 'type' : forcing value to bool 'true' or 'false' (performance warning)
  4805: 'operation' : unsafe mix of type 'type' and type 'type' in operation
  
  These warnings will be handled in a separate bug, as they are performance related or bogus.
  
  Fixed to int the return type of functions that return more than 
  2 distinct values.

  CMakeLists.txt@1.23.1.1, 2008-03-21 17:23:13+02:00, gkodinov@macbook.gmz +4 -0
    Bug #26461: disable the C4800 and C4805 warnings temporarily

  include/config-win.h@1.87.1.1, 2008-03-21 17:23:13+02:00, gkodinov@macbook.gmz +1 -3
    Bug #26461: 
     - no need for this define for Windows.
     - windows C++ compilers have a bool type

  include/my_global.h@1.147.1.1, 2008-03-21 17:23:13+02:00, gkodinov@macbook.gmz +1 -1
    Bug #26461: removed bool_defined (no longer needed)

  sql/handler.h@1.190, 2008-03-21 17:23:13+02:00, gkodinov@macbook.gmz +1 -1
    Bug #26461: bool functions must return boolean values

  sql/mysql_priv.h@1.469, 2008-03-21 17:23:13+02:00, gkodinov@macbook.gmz +7 -7
    Bug #26461: fixed return type of functions that return more than
    2 distinct values.

  sql/procedure.h@1.24, 2008-03-21 17:23:13+02:00, gkodinov@macbook.gmz +1 -1
    Bug #26461: fixed return type of functions that return more than
    2 distinct values.

  sql/sql_acl.cc@1.229, 2008-03-21 17:23:14+02:00, gkodinov@macbook.gmz +3 -3
    Bug #26461: fixed return type of functions that return more than
    2 distinct values.

  sql/sql_acl.h@1.56, 2008-03-21 17:23:14+02:00, gkodinov@macbook.gmz +3 -3
    Bug #26461: fixed return type of functions that return more than
    2 distinct values.

  sql/sql_analyse.cc@1.72, 2008-03-21 17:23:14+02:00, gkodinov@macbook.gmz +1 -1
    Bug #26461: fixed return type of functions that return more than
    2 distinct values.

  sql/sql_analyse.h@1.23, 2008-03-21 17:23:14+02:00, gkodinov@macbook.gmz +1 -1
    Bug #26461: fixed return type of functions that return more than
    2 distinct values.

  sql/sql_base.cc@1.400, 2008-03-21 17:23:14+02:00, gkodinov@macbook.gmz +1 -1
    Bug #26461: fixed return type of functions that return more than
    2 distinct values.

  sql/sql_db.cc@1.138, 2008-03-21 17:23:14+02:00, gkodinov@macbook.gmz +1 -1
    Bug #26461: fixed return type of functions that return more than
    2 distinct values.

  sql/sql_delete.cc@1.202.2.1, 2008-03-21 17:23:14+02:00, gkodinov@macbook.gmz +2 -2
    Bug #26461: fixed return type of functions that return more than
    2 distinct values.

  sql/sql_load.cc@1.119, 2008-03-21 17:23:14+02:00, gkodinov@macbook.gmz +1 -1
    Bug #26461: fixed return type of functions that return more than
    2 distinct values.

  sql/sql_parse.cc@1.647, 2008-03-21 17:23:14+02:00, gkodinov@macbook.gmz +2 -2
    Bug #26461: fixed return type of functions that return more than
    2 distinct values.

  sql/sql_prepare.cc@1.210.1.1, 2008-03-21 17:23:14+02:00, gkodinov@macbook.gmz +3 -3
    Bug #26461: fixed return type of functions that return more than
    2 distinct values.

  sql/sql_update.cc@1.226.1.1, 2008-03-21 17:23:14+02:00, gkodinov@macbook.gmz +1 -1
    Bug #26461: fixed return type of functions that return more than
    2 distinct values.

ChangeSet@1.2572.13.5, 2008-03-20 19:07:17+04:00, svoj@mysql.com +3 -0
  BUG#34788 - malformed federated connection url is not handled
              correctly - crashes server !
  
  Creating federated table with connect string containing empty
  (zero-length) host name and port is evaluated as 0 (port is
  incorrect, omitted or 0) crashes server.
  
  This happens because federated calls strcmp() with NULL pointer.
  
  Fixed by avoiding strcmp() call if hostname is set to NULL.

  mysql-test/r/federated.result@1.49, 2008-03-20 19:07:16+04:00, svoj@mysql.com +2 -0
    A test case for BUG#34788.

  mysql-test/t/federated.test@1.43, 2008-03-20 19:07:16+04:00, svoj@mysql.com +7 -0
    A test case for BUG#34788.

  sql/ha_federated.cc@1.88, 2008-03-20 19:07:16+04:00, svoj@mysql.com +8 -1
    Fixed that parse_url() may call strcmp() with NULL pointer.

ChangeSet@1.2585.1.2, 2008-03-19 18:36:41-04:00, cmiller@zippy.cornsilk.net +1 -0
  Suggestion of Tim.  Avoid unnecessary sleep.

  support-files/mysql.server.sh@1.60, 2008-03-19 18:36:39-04:00, cmiller@zippy.cornsilk.net +1 -1
    Suggestion of Tim.  Avoid unnecessary sleep.

ChangeSet@1.2585.1.1, 2008-03-19 18:13:56-04:00, cmiller@zippy.cornsilk.net +1 -0
  Bug#30378: mysql.server needs to skip wait_for_pid() when mysqld \
  	isn't running
  
  Pass the process id of the manager as a parameter to "wait_for_pid"
  and if the manager isn't running, then do not continue to wait.
  
  Also, capture the error message of our process-existence test, 
  "kill -0", as we expect errors and shouldn't pass them to the user.  
  Additionally, be a bit more descriptive of what the problem is.

  support-files/mysql.server.sh@1.59, 2008-03-19 18:13:55-04:00, cmiller@zippy.cornsilk.net +27 -4
    Test that the PID-file's manager is running while we're waiting for
    something to happen with the pid-file.
    
    Capture the error message of our process-existence test, "kill -0",
    as we expect errors and shouldn't pass them to the user.
    Additionally, be a bit more descriptive of what the problem is.

ChangeSet@1.1616.3131.1, 2008-03-19 19:13:28+01:00, joerg@trift2. +1 -0
  support-files/mysql.spec.sh  :   Add the man pages for "ndbd" and "ndb_mgmd".

  support-files/mysql.spec.sh@1.83.8.1, 2008-03-19 19:13:26+01:00, joerg@trift2. +6 -0
    Add the man pages for "ndbd" and "ndb_mgmd".

ChangeSet@1.2572.12.6, 2008-03-19 15:01:03-03:00, davi@mysql.com +1 -0
  Bug#30960 processlist state '*** DEAD ***' on recent 5.0.48 windows builds
  
  The problem is that unimplemented WIN32 version of pthread_kill
  is returning ESRCH no matter the arguments, causing calls to
  mysqld_list_processes to set the procinfo to dead because
  pthread_kill returns non zero. The dead procinfo would show
  up on a second invocation of show processlist.

  include/my_pthread.h@1.102, 2008-03-19 15:00:53-03:00, davi@mysql.com +4 -4
    When unimplemented, pthread_kill must return zero for
    any process id other then zero.

ChangeSet@1.2572.19.1, 2008-03-19 18:44:50+02:00, aelkin@mysql1000.(none) +3 -0
  Bug #35178 INSERT_ID not written to binary log for inserts against BLACKHOLE backed tables
  
  binlogging of insert into a autoincrement blackhole table ignored
  an explicit set insert_id.
  
  Fixed with refining of the blackhole's insert method to call
  update_auto_increment() that prepares binlogging the insert query 
  with the preceeding set insert_id.
  
  Note, as the engine does not store any actual data one has to explicitly
  provide to the server with the value of the autoincrement column via
  set insert_id. Otherwise binlogging will happend with the default 
  set insert_id=1.

  mysql-test/r/blackhole.result@1.15, 2008-03-19 18:44:49+02:00, aelkin@mysql1000.(none) +17 -0
    results changed

  mysql-test/t/blackhole.test@1.15, 2008-03-19 18:44:49+02:00, aelkin@mysql1000.(none) +24 -2
    a regression test for the bug added

  sql/ha_blackhole.cc@1.30, 2008-03-19 18:44:49+02:00, aelkin@mysql1000.(none) +1 -1
    blackhole's insert method is refined to call update_auto_increment()
    that prepares binlogging the insert query with the preceeding set insert_id.

ChangeSet@1.2567.27.2, 2008-03-19 14:32:28+01:00, mhansson@riffraff.(none) +3 -0
  Bug#34529: Crash on complex Falcon I_S select after ALTER .. PARTITION BY
    
  When swapping out heap I_S tables to disk, this is done after plan refinement.
  Thus, READ_RECORD::file will still point to the (deleted) heap handler at start
  of execution. This causes segmentation fault if join buffering is used and the 
  query is a star query where the result is found to be empty before accessing
  some table. In this case that table has not been initialized (i.e. had its 
  READ_RECORD re-initialized) before the cleanup routine tries to close the handler.
  Fixed by updating READ_RECORD::file when changing handler.

  mysql-test/r/information_schema.result@1.129, 2008-03-19 14:32:27+01:00, mhansson@riffraff.(none) +10 -0
    Bug#34529: Test result.

  mysql-test/t/information_schema.test@1.98, 2008-03-19 14:32:27+01:00, mhansson@riffraff.(none) +21 -0
    Bug#34529: Test case.

  sql/sql_show.cc@1.360, 2008-03-19 14:32:27+01:00, mhansson@riffraff.(none) +2 -0
    Bug#34529: The fix.

ChangeSet@1.2559.58.1, 2008-03-19 15:51:22+04:00, holyfoot@mysql.com +3 -0
  Bug #33334 mysqltest_embedded crashes when disconnecting before reap.
  
  Before breaking the connection we have to check that there's no query
    executing at the moment. Otherwise it can lead to crash in embedded server.

  client/mysqltest.c@1.309.1.4, 2008-03-19 15:51:20+04:00, holyfoot@mysql.com +25 -9
    Bug #33334 mysqltest_embedded crashes when disconnecting before reap.
    
    Wait until the query thread is finished before we break the connection.
    Waiting part moved to a separate wait_query_thread_end() function

  mysql-test/r/flush.result@1.18, 2008-03-19 15:51:20+04:00, holyfoot@mysql.com +1 -0
    Bug #33334 mysqltest_embedded crashes when disconnecting before reap.
    
    test result

  mysql-test/t/flush.test@1.24, 2008-03-19 15:51:20+04:00, holyfoot@mysql.com +9 -0
    Bug #33334 mysqltest_embedded crashes when disconnecting before reap.
    
    test case

ChangeSet@1.2572.13.4, 2008-03-18 16:38:12+04:00, svoj@mysql.com +2 -0
  Make gcov happy.

  sql/log_event.cc@1.247, 2008-03-18 16:38:10+04:00, svoj@mysql.com +1 -1
    Make gcov happy.

  sql/repl_failsafe.cc@1.68, 2008-03-18 16:38:10+04:00, svoj@mysql.com +1 -1
    Make gcov happy.

ChangeSet@1.1616.3130.2, 2008-03-18 00:57:57+01:00, kent@mysql.com +1 -0
  Raise version number after cloning 4.1.24

  configure.in@1.201.75.1, 2008-03-18 00:57:45+01:00, kent@mysql.com +2 -2
    Raise version number after cloning 4.1.24

ChangeSet@1.2572.17.1, 2008-03-17 20:19:04+02:00, aelkin@mysql1000.(none) +5 -0
  Bug #18199  PURGE BINARY LOGS fails silently with missing logs;
  Bug #18453  Warning/error message if there is a mismatch between ...
   
  There were three problems:
   
   1. the reported lack of warnings for the BEFORE syntax of PURGE;
   2. the similar lack of warnings for the TO syntax;
   3. incompatible behaviour between the two in that the latter blanked out
      regardlessly of presence or lack the actual file corresponding to
      an index record; the former version gave up at the first mismatch.
  
  fixed with deploying the warning's generation and synronizing logics of 
  purge_logs() and purge_logs_before_date().
  my_stat() is called in either of two branches of purge_logs() (responsible
  for the TO syntax of PURGE) similarly to how it has behaved in the BEFORE syntax.
  If there is no actual binlog file, my_stat returns NULL and my_delete is
  not invoked.
  A critical error is reported to the user if a file from the index
  could not be retrieved info about or deleted with a system error code
  different than ENOENT.

  mysql-test/include/show_binary_logs.inc@1.1, 2008-03-17 20:19:03+02:00, aelkin@mysql1000.(none) +3 -0
    a new macro - shortcut of show binary logs

  mysql-test/include/show_binary_logs.inc@1.0, 2008-03-17 20:19:03+02:00, aelkin@mysql1000.(none) +0 -0

  mysql-test/r/binlog_index.result@1.1, 2008-03-17 20:19:03+02:00, aelkin@mysql1000.(none) +39 -0
    new results

  mysql-test/r/binlog_index.result@1.0, 2008-03-17 20:19:03+02:00, aelkin@mysql1000.(none) +0 -0

  mysql-test/t/binlog_index.test@1.1, 2008-03-17 20:19:03+02:00, aelkin@mysql1000.(none) +69 -0
    a regression test for the bugs

  mysql-test/t/binlog_index.test@1.0, 2008-03-17 20:19:03+02:00, aelkin@mysql1000.(none) +0 -0

  sql/log.cc@1.223.1.1, 2008-03-17 20:19:03+02:00, aelkin@mysql1000.(none) +127 -26
    generating warning in two functions.
    refining logics to call my_stat() by purge_logs() as it happens
    in purge_logs_before_date().
    my_delete() is called only if my_stat() ensured existance of the file.
    A critical error is reported to the user if a file from the index
    could not be my_stat():ed or my_delete():d with an error different
    than ENOENT.

  sql/share/errmsg.txt@1.83, 2008-03-17 20:19:03+02:00, aelkin@mysql1000.(none) +2 -0
    new error message

ChangeSet@1.2572.8.6, 2008-03-17 11:16:37-03:00, davi@mysql.com +1 -0
  Post-merge fix for Bug 35103.

  sql/sql_prepare.cc@1.212, 2008-03-17 11:16:34-03:00, davi@mysql.com +1 -1
    Don't send unexpected error to the client.

ChangeSet@1.2572.8.5, 2008-03-14 17:40:12-03:00, davi@mysql.com +4 -0
  Bug#35103 mysql_client_test::test_bug29948 causes sporadic failures
  
  The problem was that the COM_STMT_SEND_LONG_DATA was sending a response
  packet if the prepared statement wasn't found in the server (due to
  reconnection). The commands COM_STMT_SEND_LONG_DATA and COM_STMT_CLOSE
  should not send any packets, even error packets should not be sent since
  they are not expected by the client API.
  
  The solution is to clear generated during the execution of the aforementioned
  commands and to skip resend of prepared statement commands. Another fix is
  that if the connection breaks during the send of prepared statement command,
  the command is not sent again since the prepared statement is no longer in the
  server.

  libmysql/libmysql.c@1.249.2.1, 2008-03-14 17:40:10-03:00, davi@mysql.com +12 -5
    The mysql handle might be reset after a reconnection.
    Pass the now used stmt argument to cli_advanced_command.

  sql-common/client.c@1.119.1.1, 2008-03-14 17:40:10-03:00, davi@mysql.com +7 -3
    Don't resend command if the connection broke and it's a prepared
    statement command. If the session is broken, prepared statements
    on the server are gone, set the error accordanly.

  sql/sql_prepare.cc@1.211, 2008-03-14 17:40:10-03:00, davi@mysql.com +10 -6
    Clear any error set during the execution of the request
    command.

  tests/mysql_client_test.c@1.251, 2008-03-14 17:40:10-03:00, davi@mysql.com +1 -78
    Fix memory leak by freeing result associated with statement.
    Remove test case for Bug 29948 because it's not reliable in
    5.0 (fixed in 5.1) due to KILL queries sending two packets for
    a thread that kills itself.

ChangeSet@1.2572.10.7, 2008-03-14 20:51:32+01:00, istruewing@stella.local +2 -0
  Post-merge fix

  mysql-test/r/type_set.result@1.16, 2008-03-14 20:51:31+01:00, istruewing@stella.local +1 -0
    Post-merge fix

  mysql-test/t/type_set.test@1.13, 2008-03-14 20:51:31+01:00, istruewing@stella.local +1 -1
    Post-merge fix

ChangeSet@1.2567.28.2, 2008-03-14 23:11:59+04:00, gshchepa@host.loc +4 -0
  Fixed bug #34763.
  
  Queries like:
  
    SELECT ROW(1, 2) IN (SELECT t1.a, 2)
      FROM t1 GROUP BY t1.a
  
  or 
  
    SELECT ROW(1, 2) IN (SELECT t1.a, 2 FROM t2)
      FROM t1 GROUP BY t1.a
  
  lead to assertion failure in the
  Item_in_subselect::row_value_transformer method in debugging
  build, or to unexpected error message in release build:
  
    ERROR 1247 (42S22): Reference '<list ref>' not supported (forward
                        reference in item list)
  
  Unexpected error message and assertion failure have been
  eliminated.

  mysql-test/r/subselect3.result@1.13, 2008-03-14 22:55:55+04:00, gshchepa@host.loc +12 -1
    Added test case for bug #34763.

  mysql-test/t/subselect3.test@1.13, 2008-03-14 22:55:58+04:00, gshchepa@host.loc +18 -1
    Added test case for bug #34763.

  sql/item.cc@1.301.1.1, 2008-03-14 22:55:59+04:00, gshchepa@host.loc +9 -6
    Fixed bug #34763.
    The Item_ref::fix_fields method has been modified to silently
    ignore not fixed outer references: by the definition, those
    references should be fixed later by the call to the
    fix_inner_refs function.

  sql/item_subselect.cc@1.163, 2008-03-14 22:56:00+04:00, gshchepa@host.loc +10 -2
    Fixed bug #34763.
    The Item_in_subselect::row_value_transformer method has been
    modified to eliminate assertion failure on not fixed outer
    references: by the definition those references are allowed in
    this context and should be fixed later by the call to the
    fix_inner_refs function.

ChangeSet@1.2572.14.1, 2008-03-14 19:38:22+04:00, svoj@mysql.com +4 -0
  BUG#28248 - mysqldump results with MERGE ... UNION=() cannot be executed
  
  When there are no underlying tables specified for a merge table,
  SHOW CREATE TABLE outputs a statement that cannot be executed. The
  same is true for mysqldump (it generates dumps that cannot be
  executed).
  
  This happens because SQL parser does not accept empty UNION() clause.
  
  This patch changes the following:
  - it is now possible to execute CREATE/ALTER statement with
    empty UNION() clause.
  - the same as above, but still worth noting: it is now possible to
    remove underlying tables mapping using ALTER TABLE ... UNION=().
  - SHOW CREATE TABLE does not output UNION() clause if there are
    no underlying tables specified for a merge table. This makes
    mysqldump slightly smaller.

  mysql-test/r/merge.result@1.65, 2008-03-14 19:38:20+04:00, svoj@mysql.com +22 -0
    A test case for BUG#28248.

  mysql-test/t/merge.test@1.55, 2008-03-14 19:38:20+04:00, svoj@mysql.com +13 -0
    A test case for BUG#28248.

  sql/ha_myisammrg.cc@1.93, 2008-03-14 19:38:20+04:00, svoj@mysql.com +6 -0
    Do not output UNION clause in SHOW CREATE TABLE, when there are
    no underlying tables defined.

  sql/sql_yacc.yy@1.545.1.2, 2008-03-14 19:38:20+04:00, svoj@mysql.com +1 -1
    Make underlying table list for MERGE engine optional.
    
    As for MERGE engine empty underlying tables list is valid, it should
    be valid for the parser as well.
    
    This change is mostly needed to restore dumps made by earlier MySQL
    versions. Also with this fix it is possible to remove underlying
    tables mapping by using ALTER TABLE ... UNION=().

ChangeSet@1.2572.13.1, 2008-03-14 17:17:03+04:00, svoj@mysql.com +2 -0
  BUG#13861 - START SLAVE UNTIL may stop 1 evnt too late if
              log-slave-updates and circul repl
  
  This is a test case fix for BUG#13861.

  mysql-test/r/rpl_dual_pos_advance.result@1.4, 2008-03-14 17:17:01+04:00, svoj@mysql.com +0 -3
    Fix for a test case for BUG#13861.

  mysql-test/t/rpl_dual_pos_advance.test@1.5, 2008-03-14 17:17:01+04:00, svoj@mysql.com +0 -6
    Fix for a test case for BUG#13861.
    
    master_pos_wait() requires slave sql thread running. But it is not
    guaranteed for this test case. As we use start slave until it may
    execute all events and shutdown before master_pos_wait() is started.
    
    On the other hand it is safe just to wait for slave to stop here,
    as start slave returns _after_ sql thread is started.

ChangeSet@1.2567.29.1, 2008-03-14 10:03:01+08:00, hezx@mail.hezx.com +4 -0
  BUG#33029 5.0 to 5.1 replication fails on dup key when inserting
  using a trig in SP
  
  For all 5.0 and up to 5.1.12 exclusive, when a stored routine or
  trigger caused an INSERT into an AUTO_INCREMENT column, the
  generated AUTO_INCREMENT value should not be written into the
  binary log, which means if a statement does not generate
  AUTO_INCREMENT value itself, there will be no Intvar event (SET
  INSERT_ID) associated with it even if one of the stored routine
  or trigger caused generation of such a value. And meanwhile, when
  executing a stored routine or trigger, it would ignore the
  INSERT_ID value even if there is a INSERT_ID value available set
  by a SET INSERT_ID statement.
  
  Starting from MySQL 5.1.12, the generated AUTO_INCREMENT value is
  written into the binary log, and the value will be used if
  available when executing the stored routine or trigger.
  
  Prior fix of this bug in MySQL 5.0 and prior MySQL 5.1.12
  (referenced as the buggy versions in the text below), when a
  statement that generates AUTO_INCREMENT value by the top
  statement was executed in the body of a SP, all statements in the
  SP after this statement would be treated as if they had generated
  AUTO_INCREMENT by the top statement.  When a statement that did
  not generate AUTO_INCREMENT value by the top statement but by a
  function/trigger called by it, an erroneous Intvar event would be
  associated with the statement, this erroneous INSERT_ID value
  wouldn't cause problem when replicating between masters and
  slaves of 5.0.x or prior 5.1.12, because the erroneous INSERT_ID
  value was not used when executing functions/triggers. But when
  replicating from buggy versions to 5.1.12 or newer, which will
  use the INSERT_ID value in functions/triggers, the erroneous
  value will be used, which would cause duplicate entry error and
  cause the slave to stop.
  
  The patch for 5.0 fixed it not to generate the erroneous Intvar
  event, another patch for 5.1 fixed it to ignore the SET INSERT_ID
  value when executing functions/triggers if it is replicating from
  a master of buggy versions.

  mysql-test/include/show_binlog_events.inc@1.2, 2008-03-14 10:02:59+08:00, hezx@mail.hezx.com +9 -3
    add $binlog_start parameter to set the start position when show binlog events, if not set a default value will be used.
    
    mask out column 2(Pos), 4(Server_id), table_id, and file_id

  mysql-test/r/rpl_auto_increment_bug33029.result@1.1, 2008-03-14 10:02:59+08:00, hezx@mail.hezx.com +167 -0
    Add test for bug33029, test if the master generate the erroneous event or not

  mysql-test/r/rpl_auto_increment_bug33029.result@1.0, 2008-03-14 10:02:59+08:00, hezx@mail.hezx.com +0 -0

  mysql-test/t/rpl_auto_increment_bug33029.test@1.1, 2008-03-14 10:02:59+08:00, hezx@mail.hezx.com +107 -0
    Add test for bug33029, test if the master generate the erroneous event or not

  mysql-test/t/rpl_auto_increment_bug33029.test@1.0, 2008-03-14 10:02:59+08:00, hezx@mail.hezx.com +0 -0

  sql/sql_class.cc@1.283, 2008-03-14 10:02:59+08:00, hezx@mail.hezx.com +7 -0
    Reset insert_id_used after each query in SP

ChangeSet@1.2572.10.3, 2008-03-13 16:39:27+01:00, istruewing@stella.local +3 -0
  Bug#33756 - query cache with concurrent_insert=0 appears broken
  
  When concurrent inserts were disabled, statements after an INSERT
  were not put into the query cache. This happened because we do not
  save the current data file length at statement start when
  concurrent inserts are disabled. But we checked the always zero
  local length against the real file length anyway.
    
  Fixed by doing the check only if concurrent inserts are not diabled.

  mysql-test/r/query_cache.result@1.87, 2008-03-13 16:39:26+01:00, istruewing@stella.local +27 -0
    Bug#33756 - query cache with concurrent_insert=0 appears broken
    Added test result.

  mysql-test/t/query_cache.test@1.66, 2008-03-13 16:39:26+01:00, istruewing@stella.local +20 -0
    Bug#33756 - query cache with concurrent_insert=0 appears broken
    Added test.

  sql/ha_myisam.cc@1.186, 2008-03-13 16:39:26+01:00, istruewing@stella.local +40 -30
    Bug#33756 - query cache with concurrent_insert=0 appears broken
    Changed code so that file length check is done only when
    concurrent inserts are possible.

ChangeSet@1.2572.12.4, 2008-03-13 12:14:14+03:00, kaa@kaamos.(none) +1 -0
  Bug#35103 mysql_client_test::test_bug29948 causes sporadic failures
    
  Disable test case for bug 29948, which is causing sporadically
  failures in other tests inside mysql_client_test.

  tests/mysql_client_test.c@1.249.1.3, 2008-03-13 12:14:13+03:00, kaa@kaamos.(none) +4 -1
    Disable test case.

ChangeSet@1.2571.1.1, 2008-03-12 17:03:50-04:00, cmiller@zippy.cornsilk.net +1 -0
  Bug#34192: mysqldump from mysql 5.0.51 silently fails on dumping \
  	databases from 4.0 server
  
  mysqldump treated a failure to set the results charset as a severe
  error.  
  
  Now, don't try to set the charset for the SHOW CREATE TABLE statement,
  if remote server's version is earlier than 4.1, which means it 
  doesn't support changing charsets.

  client/mysqldump.c@1.275.1.1, 2008-03-12 17:03:49-04:00, cmiller@zippy.cornsilk.net +24 -3
    Don't set the charset for receiving results if the server doesn't 
    support it.

ChangeSet@1.2572.10.2, 2008-03-12 15:38:57+01:00, istruewing@stella.local +1 -0
  Bug#35247 - rpl_transaction.test produces warnings files
  
  The test file tried to use a mysqltest command '--warning'
  but there is no such command.
  
  Changed '--warning' to '#--warning'.

  mysql-test/t/rpl_transaction.test@1.4, 2008-03-12 15:38:55+01:00, istruewing@stella.local +1 -1
    Bug#35247 - rpl_transaction.test produces warnings files
    Changed '--warning' to '#--warning'.

ChangeSet@1.2572.8.4, 2008-03-12 16:13:33+03:00, anozdrin@quad. +3 -0
  A fix for Bug#34643: TRUNCATE crash if trigger and foreign key.
    
  In cases when TRUNCATE was executed by invoking mysql_delete() rather
  than by table recreation (for example, when TRUNCATE was issued on
  InnoDB table with is referenced by foreign key) triggers were invoked.
  In debug builds this also led to crash because of an assertion, which
  assumes that some preliminary actions take place before trigger 
  invocation, which doesn't happen in case of TRUNCATE.
  
  The fix is not to execute triggers in mysql_delete() when this
  function is used by TRUNCATE.

  mysql-test/r/trigger-trans.result@1.4, 2008-03-12 16:13:32+03:00, anozdrin@quad. +19 -0
    Update result file.

  mysql-test/t/trigger-trans.test@1.3, 2008-03-12 16:13:32+03:00, anozdrin@quad. +32 -0
    A test case for Bug#34643: TRUNCATE crash if trigger and foreign key.

  sql/sql_delete.cc@1.202.1.1, 2008-03-12 16:13:32+03:00, anozdrin@quad. +10 -5
    Do not process triggers in TRUNCATE.

ChangeSet@1.2572.12.3, 2008-03-12 12:13:41+03:00, kaa@kaamos.(none) +1 -0
  Re-enabled the test for mysql_insert_id() after merging from main.

  tests/mysql_client_test.c@1.249.1.2, 2008-03-12 12:13:40+03:00, kaa@kaamos.(none) +1 -7
    Re-enabled the test for mysql_insert_id() after merging from main.

ChangeSet@1.2582.1.1, 2008-03-11 19:54:35+01:00, mleich@five.local.lan +36 -0
  Post fix for
  WL#4203 Reorganize and fix the data dictionary tests of
          testsuite funcs_1
  because the goal to fix
  Bug#34532 Some funcs_1 tests do not clean up at end of testing
  was partially missed.
  Some minor additional modifications are for
     WL#4304 Cleanup in funcs_1 tests

  BitKeeper/deleted/.del-innodb_triggers.result@1.2, 2008-03-11 19:52:33+01:00, mleich@five.local.lan +0 -0
    Rename: mysql-test/suite/funcs_1/r/innodb_triggers.result -> BitKeeper/deleted/.del-innodb_triggers.result

  BitKeeper/deleted/.del-memory_triggers.result@1.2, 2008-03-11 19:52:33+01:00, mleich@five.local.lan +0 -0
    Rename: mysql-test/suite/funcs_1/r/memory_triggers.result -> BitKeeper/deleted/.del-memory_triggers.result

  BitKeeper/deleted/.del-myisam_triggers.result@1.2, 2008-03-11 19:52:33+01:00, mleich@five.local.lan +0 -0
    Rename: mysql-test/suite/funcs_1/r/myisam_triggers.result -> BitKeeper/deleted/.del-myisam_triggers.result

  mysql-test/suite/funcs_1/cursors/cursors_master.test@1.2, 2008-03-11 19:54:33+01:00, mleich@five.local.lan +0 -1
    Backport of file in 5.1

  mysql-test/suite/funcs_1/datadict/datadict_load.inc@1.3, 2008-03-11 19:54:33+01:00, mleich@five.local.lan +33 -49
    Cleanup

  mysql-test/suite/funcs_1/r/innodb_storedproc_02.result@1.3, 2008-03-11 19:53:16+01:00, mleich@five.local.lan +0 -0
    Change mode to -rw-rw-r--

  mysql-test/suite/funcs_1/r/innodb_storedproc_03.result@1.3, 2008-03-11 19:53:16+01:00, mleich@five.local.lan +0 -0
    Change mode to -rw-rw-r--

  mysql-test/suite/funcs_1/r/innodb_storedproc_07.result@1.3, 2008-03-11 19:53:16+01:00, mleich@five.local.lan +0 -0
    Change mode to -rw-rw-r--

  mysql-test/suite/funcs_1/r/innodb_storedproc_08.result@1.3, 2008-03-11 19:53:16+01:00, mleich@five.local.lan +0 -0
    Change mode to -rw-rw-r--

  mysql-test/suite/funcs_1/r/innodb_storedproc_10.result@1.3, 2008-03-11 19:53:16+01:00, mleich@five.local.lan +0 -0
    Change mode to -rw-rw-r--

  mysql-test/suite/funcs_1/r/innodb_views.result@1.6, 2008-03-11 19:54:33+01:00, mleich@five.local.lan +11946 -502
    Updated results

  mysql-test/suite/funcs_1/r/is_columns_innodb.result@1.2, 2008-03-11 19:54:33+01:00, mleich@five.local.lan +0 -1
    Updated results

  mysql-test/suite/funcs_1/r/is_columns_memory.result@1.2, 2008-03-11 19:54:33+01:00, mleich@five.local.lan +0 -1
    Updated results

  mysql-test/suite/funcs_1/r/is_columns_myisam.result@1.2, 2008-03-11 19:54:33+01:00, mleich@five.local.lan +0 -1
    Updated results

  mysql-test/suite/funcs_1/r/is_columns_ndb.result@1.2, 2008-03-11 19:54:33+01:00, mleich@five.local.lan +0 -1
    Updated results

  mysql-test/suite/funcs_1/r/is_tables_innodb.result@1.2, 2008-03-11 19:54:33+01:00, mleich@five.local.lan +0 -1
    Updated results

  mysql-test/suite/funcs_1/r/is_tables_memory.result@1.2, 2008-03-11 19:54:33+01:00, mleich@five.local.lan +0 -1
    Updated results

  mysql-test/suite/funcs_1/r/is_tables_myisam.result@1.2, 2008-03-11 19:54:33+01:00, mleich@five.local.lan +0 -1
    Updated results

  mysql-test/suite/funcs_1/r/is_tables_ndb.result@1.2, 2008-03-11 19:54:33+01:00, mleich@five.local.lan +0 -1
    Updated results

  mysql-test/suite/funcs_1/r/memory_storedproc_02.result@1.3, 2008-03-11 19:53:17+01:00, mleich@five.local.lan +0 -0
    Change mode to -rw-rw-r--

  mysql-test/suite/funcs_1/r/memory_storedproc_03.result@1.3, 2008-03-11 19:53:17+01:00, mleich@five.local.lan +0 -0
    Change mode to -rw-rw-r--

  mysql-test/suite/funcs_1/r/memory_storedproc_07.result@1.3, 2008-03-11 19:53:17+01:00, mleich@five.local.lan +0 -0
    Change mode to -rw-rw-r--

  mysql-test/suite/funcs_1/r/memory_storedproc_08.result@1.3, 2008-03-11 19:53:17+01:00, mleich@five.local.lan +0 -0
    Change mode to -rw-rw-r--

  mysql-test/suite/funcs_1/r/memory_storedproc_10.result@1.3, 2008-03-11 19:53:17+01:00, mleich@five.local.lan +0 -0
    Change mode to -rw-rw-r--

  mysql-test/suite/funcs_1/r/memory_views.result@1.6, 2008-03-11 19:54:33+01:00, mleich@five.local.lan +11946 -502
    Updated results

  mysql-test/suite/funcs_1/r/myisam_storedproc_02.result@1.3, 2008-03-11 19:53:17+01:00, mleich@five.local.lan +0 -0
    Change mode to -rw-rw-r--

  mysql-test/suite/funcs_1/r/myisam_storedproc_03.result@1.3, 2008-03-11 19:53:17+01:00, mleich@five.local.lan +0 -0
    Change mode to -rw-rw-r--

  mysql-test/suite/funcs_1/r/myisam_storedproc_07.result@1.3, 2008-03-11 19:53:17+01:00, mleich@five.local.lan +0 -0
    Change mode to -rw-rw-r--

  mysql-test/suite/funcs_1/r/myisam_storedproc_08.result@1.3, 2008-03-11 19:53:17+01:00, mleich@five.local.lan +0 -0
    Change mode to -rw-rw-r--

  mysql-test/suite/funcs_1/r/myisam_storedproc_10.result@1.3, 2008-03-11 19:53:17+01:00, mleich@five.local.lan +0 -0
    Change mode to -rw-rw-r--

  mysql-test/suite/funcs_1/r/myisam_views.result@1.6, 2008-03-11 19:54:34+01:00, mleich@five.local.lan +12088 -9328
    Updated results

  mysql-test/suite/funcs_1/t/innodb_storedproc.test@1.2, 2008-03-11 19:54:34+01:00, mleich@five.local.lan +3 -0
    Backport of file in 5.1

  mysql-test/suite/funcs_1/t/memory_storedproc.test@1.2, 2008-03-11 19:54:34+01:00, mleich@five.local.lan +2 -0
    Backport of file in 5.1

  mysql-test/suite/funcs_1/t/myisam_storedproc.test@1.2, 2008-03-11 19:54:34+01:00, mleich@five.local.lan +2 -0
    Backport of file in 5.1

  mysql-test/suite/funcs_1/t/myisam_trig_1011ext.test@1.3, 2008-03-11 19:54:34+01:00, mleich@five.local.lan +0 -9
    Cleanup

  mysql-test/suite/funcs_1/views/views_master.inc@1.4, 2008-03-11 19:54:34+01:00, mleich@five.local.lan +440 -409
    Backport of file in 5.1 which got many fixes for instabilities
    and other improvements

ChangeSet@1.2583, 2008-03-11 15:21:58+01:00, kent@mysql.com +1 -0
  make_win_bin_dist:
    Include .pdb files for tools and libraries (bug#35104)

  scripts/make_win_bin_dist@1.23.1.1, 2008-03-11 15:21:17+01:00, kent@mysql.com +27 -13
    Include .pdb files for tools and libraries (bug#35104)

ChangeSet@1.2572.1.25, 2008-03-11 14:42:54+01:00, sven@riska.(none) +2 -0
  BUG#31024: STOP SLAVE does not stop attempted connect()s
  Problem: if the IO slave thread is attempting to connect,
  STOP SLAVE waits for the attempt to finish. 
  It may take a long time.
  Fix: don't wait, stop the slave immediately.

  sql/slave.cc@1.308, 2008-03-11 14:42:53+01:00, sven@riska.(none) +14 -1
    Send a SIGALRM signal to the slave thread when stopping it (using
    pthread_kill()). This breaks current socket(), connect(), poll() etc.
    calls, and makes the subsequent thd->awake() call effective.
    
    Also, move the definition of KICK_SLAVE to slave.cc.

  sql/sql_repl.h@1.42, 2008-03-11 14:42:53+01:00, sven@riska.(none) +0 -6
    Removed KICK_SLAVE and inlined it in slave.cc because:
     - it was only called once, so better to make it local to where it is used
     - it needed to include a preprocessor conditional in the middle

ChangeSet@1.2559.57.1, 2008-03-10 11:12:12+01:00, tnurnberg@mysql.com +3 -0
  Bug#34731: highest possible value for INT erroneously filtered by WHERE
  
  WHERE f1 < n ignored row if f1 was indexed integer column and
  f1 = TYPE_MAX ^ n = TYPE_MAX+1. The latter value when treated
  as TYPE overflowed (obviously). This was not handled, it is now.

  mysql-test/r/range.result@1.59.1.1, 2008-03-10 11:12:09+01:00, tnurnberg@mysql.com +39 -0
    show that on an index int column, we no longer disregard
    a field val of TYPE_MAX in SELECT ... WHERE ... < TYPE_MAX+1

  mysql-test/t/range.test@1.49.1.1, 2008-03-10 11:12:10+01:00, tnurnberg@mysql.com +47 -0
    show that on an index int column, we no longer disregard
    a field val of TYPE_MAX in SELECT ... WHERE ... < TYPE_MAX+1

  sql/opt_range.cc@1.254.1.3, 2008-03-10 11:12:10+01:00, tnurnberg@mysql.com +54 -36
    Handle overflowing of int-types in range-optimizer.
    Unfortunately requires re-indentation of entire block.
    Overflow (err == 1) was handled, but only if
    field->cmp_type() != value->result_type(), which it
    just wasn't in our case.

ChangeSet@1.2572.11.1, 2008-03-10 03:25:54-06:00, tsmith@ramayana.hindu.god +2 -0
  Bug #25486: mysqld_multi.server.sh missing from builds
  
  Make mysqld_multi.server executable, and allow it to be installed
  via chkconfig on LSB-compliant systems.

  scripts/make_binary_distribution.sh@1.132, 2008-03-10 03:25:51-06:00, tsmith@ramayana.hindu.god +2 -2
    Adjust permissions on some support-files/* scripts:  make mysqld_multi.server
    executable, and mysql-VERSION.spec not executable.

  support-files/mysqld_multi.server.sh@1.3, 2008-03-10 03:25:51-06:00, tsmith@ramayana.hindu.god +4 -0
    Add LSB comments for chkconfig to simplify installation for sysadmins.

ChangeSet@1.2580.1.1, 2008-03-07 15:45:40-05:00, iggy@amd64.(none) +1 -0
  Bug #27101 mysqlhotcopy --record_log_pos retrieves wrong slave parameters
  - Make sure mysqlhotcopy doesn't create unrestorable slaves.

  scripts/mysqlhotcopy.sh@1.56, 2008-03-07 15:45:38-05:00, iggy@amd64.(none) +5 -4
    Bug #27101 mysqlhotcopy --record_log_pos retrieves wrong slave parameters
    - Record what's been executed by the slave, not what's been delivered.

ChangeSet@1.2572.1.24, 2008-03-07 21:14:28+02:00, aelkin@mysql1000.(none) +6 -0
  Bug #26622 MASTER_POS_WAIT does not work as documented
  
  Affected tests fixing. After the fix for st_relay_log_info::wait_for_pos() that
  handles widely used select('master-bin.xxxx',pos) invoked by mysqltest
  there appeared to be four tests that either tried synchronizing when
  the slave was stopped or used incorrect synchronization method like
  to call `sync_with_master' from the current connection being to the
  master itself.
  
  Fixed with correcting the current connection or/and using the correct
  synchronization macro when possible.

  mysql-test/r/rpl_loaddata.result@1.35, 2008-03-07 21:14:26+02:00, aelkin@mysql1000.(none) +2 -1
    results changed

  mysql-test/r/rpl_slave_status.result@1.8, 2008-03-07 21:14:26+02:00, aelkin@mysql1000.(none) +1 -0
    results changed

  mysql-test/t/rpl_loaddata.test@1.27, 2008-03-07 21:14:26+02:00, aelkin@mysql1000.(none) +11 -2
    fixing cleanup for two tests

  mysql-test/t/rpl_skip_error.test@1.11, 2008-03-07 21:14:26+02:00, aelkin@mysql1000.(none) +3 -2
    fixing cleanup for two tests

  mysql-test/t/rpl_slave_status.test@1.9, 2008-03-07 21:14:26+02:00, aelkin@mysql1000.(none) +5 -1
    fixing cleanup

  mysql-test/t/rpl_temporary.test@1.26, 2008-03-07 21:14:27+02:00, aelkin@mysql1000.(none) +3 -2
    fixing synchronizations to use the intended correct macro.

ChangeSet@1.2581, 2008-03-07 17:33:07+01:00, mleich@five.local.lan +226 -0
  WL#4203 Reorganize and fix the data dictionary tests of
          testsuite funcs_1
  1. Fix the following bugs
     Bug#30440 "datadict" tests (all engines) fail: Character sets depend on configuration
        Solution: Test variants charset_collation_* adjusted to different builds
     Bug#32603 "datadict" tests (all engines) fail in "community" tree: "PROFILING" table
        Solution: Excluding "PROFILING" table from queries
     Bug#33654 "slow log" is missing a line
        Solution: Unify the content of the fields TABLES.TABLE_ROWS and
                  STATISTICS.CARDINALITY within result sets
     Bug#34532 Some funcs_1 tests do not clean up at end of testing
        Solution: DROP objects/reset global server variables modified during testing
                  + let tests missing implementation end before loading of tables
     Bug#31421 funcs_1: ndb__datadict fails, discrepancy between scripts and expected results
        Solution: Cut <engine>__datadict tests into smaller tests + generate new results.
     Bug#33599 INFORMATION_SCHEMA.STATISTICS got a new column INDEX_COMMENT: tests fail (2)
        Generation of new results during post merge fix
     Bug#33600 CHARACTER_OCTET_LENGTH is now CHARACTER_MAXIMUM_LENGTH * 4
        Generation of new results during post merge fix
     Bug#33631 Platform-specific replace of CHARACTER_MAXIMUM_LENGTH broken by 4-byte encoding
        Generation of new results during post merge fix
        + removal of platform-specific replace routine (no more needed)
  2. Restructure the tests
     - Test not more than one INFORMATION_SCHEMA view per testscript
     - Separate tests of I_S view layout+functionality from content related to the
       all time existing databases "information_schema", "mysql" and "test"
     - Avoid storage engine related variants of tests which are not sensible to
       storage engines at all.
  3. Reimplement or add some subtests + cleanup
     There is a some probability that even the reviewed changeset
     - does not fix all bugs from above   or
     - contains new bugs which show up on some platforms <> Linux or on one of
       the various build types
  4. The changeset contains fixes according to
     - one code review
     - minor bugs within testing code found after code review (accepted by reviewer)
     - problems found during tests with 5.0.56 in build environment

  BitKeeper/deleted/.del-create_database.inc@1.2, 2008-03-07 16:47:09+01:00, mleich@five.local.lan +0 -0
    Delete: mysql-test/suite/funcs_1/include/create_database.inc

  BitKeeper/deleted/.del-create_user_lowest_priv.inc@1.2, 2008-03-07 16:47:09+01:00, mleich@five.local.lan +0 -0
    Delete: mysql-test/suite/funcs_1/include/create_user_lowest_priv.inc

  BitKeeper/deleted/.del-create_user_no_super.inc@1.2, 2008-03-07 16:47:09+01:00, mleich@five.local.lan +0 -0
    Delete: mysql-test/suite/funcs_1/include/create_user_no_super.inc

  BitKeeper/deleted/.del-datadict_help_tables_build.result@1.2, 2008-03-07 16:47:51+01:00, mleich@five.local.lan +0 -0
    Delete: mysql-test/suite/funcs_1/r/datadict_help_tables_build.result

  BitKeeper/deleted/.del-datadict_help_tables_build.test@1.2, 2008-03-07 16:47:51+01:00, mleich@five.local.lan +0 -0
    Delete: mysql-test/suite/funcs_1/t/datadict_help_tables_build.test

  BitKeeper/deleted/.del-datadict_help_tables_dev.result@1.2, 2008-03-07 16:47:51+01:00, mleich@five.local.lan +0 -0
    Delete: mysql-test/suite/funcs_1/r/datadict_help_tables_dev.result

  BitKeeper/deleted/.del-datadict_help_tables_dev.test@1.2, 2008-03-07 16:47:51+01:00, mleich@five.local.lan +0 -0
    Delete: mysql-test/suite/funcs_1/t/datadict_help_tables_dev.test

  BitKeeper/deleted/.del-datadict_master.inc@1.7, 2008-03-07 16:47:51+01:00, mleich@five.local.lan +0 -0
    Delete: mysql-test/suite/funcs_1/datadict/datadict_master.inc

  BitKeeper/deleted/.del-datadict_show_schema.inc@1.4, 2008-03-07 16:48:46+01:00, mleich@five.local.lan +0 -0
    Delete: mysql-test/suite/funcs_1/datadict/datadict_show_schema.inc

  BitKeeper/deleted/.del-datadict_show_table_design.inc@1.2, 2008-03-07 16:48:46+01:00, mleich@five.local.lan +0 -0
    Delete: mysql-test/suite/funcs_1/datadict/datadict_show_table_design.inc

  BitKeeper/deleted/.del-datadict_tables.inc@1.3, 2008-03-07 16:48:46+01:00, mleich@five.local.lan +0 -0
    Delete: mysql-test/suite/funcs_1/datadict/datadict_tables.inc

  BitKeeper/deleted/.del-datadict_tables_error.inc@1.2, 2008-03-07 16:48:46+01:00, mleich@five.local.lan +0 -0
    Delete: mysql-test/suite/funcs_1/datadict/datadict_tables_error.inc

  BitKeeper/deleted/.del-datadict_tables_error_1.inc@1.2, 2008-03-07 16:48:46+01:00, mleich@five.local.lan +0 -0
    Delete: mysql-test/suite/funcs_1/datadict/datadict_tables_error_1.inc

  BitKeeper/deleted/.del-datadict_tables_error_1044.inc@1.3, 2008-03-07 16:48:46+01:00, mleich@five.local.lan +0 -0
    Delete: mysql-test/suite/funcs_1/datadict/datadict_tables_error_1044.inc

  mysql-test/suite/funcs_1/datadict/datadict_tables_error_1044.inc@1.2, 2008-03-07 16:29:40+01:00, mleich@five.local.lan +0 -0
    Change mode to -rw-rw-r--

  BitKeeper/deleted/.del-datadict_tables_error_1049.inc@1.2, 2008-03-07 16:49:32+01:00, mleich@five.local.lan +0 -0
    Delete: mysql-test/suite/funcs_1/datadict/datadict_tables_error_1049.inc

  BitKeeper/deleted/.del-datadict_tables_error_1051.inc@1.2, 2008-03-07 16:49:32+01:00, mleich@five.local.lan +0 -0
    Delete: mysql-test/suite/funcs_1/datadict/datadict_tables_error_1051.inc

  BitKeeper/deleted/.del-datadict_tables_error_1146.inc@1.2, 2008-03-07 16:49:32+01:00, mleich@five.local.lan +0 -0
    Delete: mysql-test/suite/funcs_1/datadict/datadict_tables_error_1146.inc

  BitKeeper/deleted/.del-datadict_tables_error_1288.inc@1.2, 2008-03-07 16:49:32+01:00, mleich@five.local.lan +0 -0
    Delete: mysql-test/suite/funcs_1/datadict/datadict_tables_error_1288.inc

  BitKeeper/deleted/.del-innodb__datadict.result@1.7, 2008-03-07 16:49:32+01:00, mleich@five.local.lan +0 -0
    Delete: mysql-test/suite/funcs_1/r/innodb__datadict.result

  BitKeeper/deleted/.del-innodb__datadict.test@1.3, 2008-03-07 16:49:32+01:00, mleich@five.local.lan +0 -0
    Delete: mysql-test/suite/funcs_1/t/innodb__datadict.test

  BitKeeper/deleted/.del-innodb__load.result@1.2, 2008-03-07 16:37:00+01:00, mleich@five.local.lan +0 -0
    Delete: mysql-test/suite/funcs_1/r/innodb__load.result

  BitKeeper/deleted/.del-innodb__load.test@1.2, 2008-03-07 16:36:51+01:00, mleich@five.local.lan +0 -0
    Delete: mysql-test/suite/funcs_1/t/innodb__load.test

  BitKeeper/deleted/.del-memory__datadict.result@1.7, 2008-03-07 16:50:27+01:00, mleich@five.local.lan +0 -0
    Delete: mysql-test/suite/funcs_1/r/memory__datadict.result

  BitKeeper/deleted/.del-memory__datadict.test@1.3, 2008-03-07 16:50:03+01:00, mleich@five.local.lan +0 -0
    Delete: mysql-test/suite/funcs_1/t/memory__datadict.test

  BitKeeper/deleted/.del-memory__load.result@1.2, 2008-03-07 16:37:36+01:00, mleich@five.local.lan +0 -0
    Delete: mysql-test/suite/funcs_1/r/memory__load.result

  BitKeeper/deleted/.del-memory__load.test@1.2, 2008-03-07 16:37:25+01:00, mleich@five.local.lan +0 -0
    Delete: mysql-test/suite/funcs_1/t/memory__load.test

  BitKeeper/deleted/.del-myisam__datadict.result@1.7, 2008-03-07 16:50:03+01:00, mleich@five.local.lan +0 -0
    Delete: mysql-test/suite/funcs_1/r/myisam__datadict.result

  BitKeeper/deleted/.del-myisam__datadict.test@1.3, 2008-03-07 16:50:03+01:00, mleich@five.local.lan +0 -0
    Delete: mysql-test/suite/funcs_1/t/myisam__datadict.test

  BitKeeper/deleted/.del-myisam__load.result@1.2, 2008-03-07 16:37:46+01:00, mleich@five.local.lan +0 -0
    Delete: mysql-test/suite/funcs_1/r/myisam__load.result

  BitKeeper/deleted/.del-myisam__load.test@1.2, 2008-03-07 16:37:16+01:00, mleich@five.local.lan +0 -0
    Delete: mysql-test/suite/funcs_1/t/myisam__load.test

  mysql-test/suite/funcs_1/README.txt@1.3, 2008-03-07 17:33:00+01:00, mleich@five.local.lan +44 -132
    Cleanup in description

  mysql-test/suite/funcs_1/datadict/basics_mixed1.inc@1.1, 2008-03-07 17:33:04+01:00, mleich@five.local.lan +53 -0
    Auxiliary script

  mysql-test/suite/funcs_1/datadict/basics_mixed1.inc@1.0, 2008-03-07 17:33:04+01:00, mleich@five.local.lan +0 -0

  mysql-test/suite/funcs_1/datadict/basics_mixed2.inc@1.1, 2008-03-07 17:33:04+01:00, mleich@five.local.lan +55 -0
    Auxiliary script

  mysql-test/suite/funcs_1/datadict/basics_mixed2.inc@1.0, 2008-03-07 17:33:04+01:00, mleich@five.local.lan +0 -0

  mysql-test/suite/funcs_1/datadict/basics_mixed3.inc@1.1, 2008-03-07 17:33:05+01:00, mleich@five.local.lan +42 -0
    Auxiliary script

  mysql-test/suite/funcs_1/datadict/basics_mixed3.inc@1.0, 2008-03-07 17:33:04+01:00, mleich@five.local.lan +0 -0

  mysql-test/suite/funcs_1/datadict/charset_collation.inc@1.1, 2008-03-07 17:33:05+01:00, mleich@five.local.lan +122 -0
    Auxiliary script

  mysql-test/suite/funcs_1/datadict/charset_collation.inc@1.0, 2008-03-07 17:33:05+01:00, mleich@five.local.lan +0 -0

  mysql-test/suite/funcs_1/datadict/columns.inc@1.1, 2008-03-07 17:33:05+01:00, mleich@five.local.lan +87 -0
    Auxiliary script

  mysql-test/suite/funcs_1/datadict/columns.inc@1.0, 2008-03-07 17:33:05+01:00, mleich@five.local.lan +0 -0

  mysql-test/suite/funcs_1/datadict/datadict.pre@1.1, 2008-03-07 17:33:05+01:00, mleich@five.local.lan +54 -0
    Auxiliary script

  mysql-test/suite/funcs_1/datadict/datadict.pre@1.0, 2008-03-07 17:33:05+01:00, mleich@five.local.lan +0 -0

  mysql-test/suite/funcs_1/datadict/is_table_query.inc@1.1, 2008-03-07 17:33:05+01:00, mleich@five.local.lan +42 -0
    Auxiliary script

  mysql-test/suite/funcs_1/datadict/is_table_query.inc@1.0, 2008-03-07 17:33:05+01:00, mleich@five.local.lan +0 -0

  mysql-test/suite/funcs_1/datadict/statistics.inc@1.1, 2008-03-07 17:33:05+01:00, mleich@five.local.lan +55 -0
    Auxiliary script

  mysql-test/suite/funcs_1/datadict/statistics.inc@1.0, 2008-03-07 17:33:05+01:00, mleich@five.local.lan +0 -0

  mysql-test/suite/funcs_1/datadict/table_constraints.inc@1.1, 2008-03-07 17:33:05+01:00, mleich@five.local.lan +45 -0
    Auxiliary script

  mysql-test/suite/funcs_1/datadict/table_constraints.inc@1.0, 2008-03-07 17:33:05+01:00, mleich@five.local.lan +0 -0

  mysql-test/suite/funcs_1/datadict/tables1.inc@1.1, 2008-03-07 17:33:05+01:00, mleich@five.local.lan +39 -0
    Auxiliary script

  mysql-test/suite/funcs_1/datadict/tables1.inc@1.0, 2008-03-07 17:33:05+01:00, mleich@five.local.lan +0 -0

  mysql-test/suite/funcs_1/datadict/tables2.inc@1.1, 2008-03-07 17:33:05+01:00, mleich@five.local.lan +47 -0
    Auxiliary script

  mysql-test/suite/funcs_1/datadict/tables2.inc@1.0, 2008-03-07 17:33:05+01:00, mleich@five.local.lan +0 -0

  mysql-test/suite/funcs_1/include/cleanup.inc@1.1, 2008-03-07 17:33:04+01:00, mleich@five.local.lan +21 -0
    Auxiliary script

  mysql-test/suite/funcs_1/include/cleanup.inc@1.0, 2008-03-07 17:33:04+01:00, mleich@five.local.lan +0 -0

  mysql-test/suite/funcs_1/include/memory_tb1.inc@1.2, 2008-03-07 17:33:00+01:00, mleich@five.local.lan +0 -3
    Move setting of variables into the caller scripts

  mysql-test/suite/funcs_1/include/memory_tb2.inc@1.2, 2008-03-07 17:33:00+01:00, mleich@five.local.lan +0 -3
    Move setting of variables into the caller scripts

  mysql-test/suite/funcs_1/include/memory_tb3.inc@1.2, 2008-03-07 17:33:00+01:00, mleich@five.local.lan +0 -3
    Move setting of variables into the caller scripts

  mysql-test/suite/funcs_1/include/memory_tb4.inc@1.2, 2008-03-07 17:33:00+01:00, mleich@five.local.lan +0 -3
    Move setting of variables into the caller scripts

  mysql-test/suite/funcs_1/include/sp_tb.inc@1.2, 2008-03-07 17:33:00+01:00, mleich@five.local.lan +0 -4
    Remove outdated comment

  mysql-test/suite/funcs_1/r/charset_collation_1.result@1.1, 2008-03-07 17:33:04+01:00, mleich@five.local.lan +309 -0
    Expected result for new test

  mysql-test/suite/funcs_1/r/charset_collation_1.result@1.0, 2008-03-07 17:33:04+01:00, mleich@five.local.lan +0 -0

  mysql-test/suite/funcs_1/r/charset_collation_2.result@1.1, 2008-03-07 17:33:04+01:00, mleich@five.local.lan +311 -0
    Expected result for new test

  mysql-test/suite/funcs_1/r/charset_collation_2.result@1.0, 2008-03-07 17:33:04+01:00, mleich@five.local.lan +0 -0

  mysql-test/suite/funcs_1/r/charset_collation_3.result@1.1, 2008-03-07 17:33:04+01:00, mleich@five.local.lan +309 -0
    Expected result for new test

  mysql-test/suite/funcs_1/r/charset_collation_3.result@1.0, 2008-03-07 17:33:04+01:00, mleich@five.local.lan +0 -0

  mysql-test/suite/funcs_1/r/innodb_bitdata.result@1.2, 2008-03-07 17:33:00+01:00, mleich@five.local.lan +0 -64
    Updated results

  mysql-test/suite/funcs_1/r/innodb_cursors.result@1.2, 2008-03-07 17:33:00+01:00, mleich@five.local.lan +0 -78
    Updated results

  mysql-test/suite/funcs_1/r/innodb_storedproc_02.result@1.2, 2008-03-07 17:33:00+01:00, mleich@five.local.lan +0 -2
    Updated results

  mysql-test/suite/funcs_1/r/innodb_storedproc_03.result@1.2, 2008-03-07 17:33:00+01:00, mleich@five.local.lan +0 -2
    Updated results

  mysql-test/suite/funcs_1/r/innodb_storedproc_06.result@1.2, 2008-03-07 17:33:00+01:00, mleich@five.local.lan +0 -2
    Updated results

  mysql-test/suite/funcs_1/r/innodb_storedproc_07.result@1.2, 2008-03-07 17:33:00+01:00, mleich@five.local.lan +0 -2
    Updated results

  mysql-test/suite/funcs_1/r/innodb_storedproc_08.result@1.2, 2008-03-07 17:33:00+01:00, mleich@five.local.lan +0 -2
    Updated results

  mysql-test/suite/funcs_1/r/innodb_storedproc_10.result@1.2, 2008-03-07 17:33:00+01:00, mleich@five.local.lan +0 -2
    Updated results

  mysql-test/suite/funcs_1/r/innodb_trig_0102.result@1.3, 2008-03-07 17:33:00+01:00, mleich@five.local.lan +1 -1
    Updated results

  mysql-test/suite/funcs_1/r/innodb_trig_03.result@1.2, 2008-03-07 17:33:00+01:00, mleich@five.local.lan +1 -1
    Updated results

  mysql-test/suite/funcs_1/r/innodb_trig_0407.result@1.2, 2008-03-07 17:33:00+01:00, mleich@five.local.lan +1 -1
    Updated results

  mysql-test/suite/funcs_1/r/innodb_trig_08.result@1.4, 2008-03-07 17:33:00+01:00, mleich@five.local.lan +1 -1
    Updated results

  mysql-test/suite/funcs_1/r/innodb_trig_09.result@1.3, 2008-03-07 17:33:00+01:00, mleich@five.local.lan +1 -1
    Updated results

  mysql-test/suite/funcs_1/r/innodb_trig_1011ext.result@1.2, 2008-03-07 17:33:00+01:00, mleich@five.local.lan +1 -1
    Updated results

  mysql-test/suite/funcs_1/r/innodb_trig_frkey.result@1.2, 2008-03-07 17:33:00+01:00, mleich@five.local.lan +1 -1
    Updated results

  mysql-test/suite/funcs_1/r/innodb_views.result@1.5, 2008-03-07 17:33:01+01:00, mleich@five.local.lan +2 -2
    Updated results

  mysql-test/suite/funcs_1/r/is_basics_mixed.result@1.1, 2008-03-07 17:33:04+01:00, mleich@five.local.lan +602 -0
    Expected result for new test

  mysql-test/suite/funcs_1/r/is_basics_mixed.result@1.0, 2008-03-07 17:33:04+01:00, mleich@five.local.lan +0 -0

  mysql-test/suite/funcs_1/r/is_character_sets.result@1.1, 2008-03-07 17:33:04+01:00, mleich@five.local.lan +78 -0
    Expected result for new test

  mysql-test/suite/funcs_1/r/is_character_sets.result@1.0, 2008-03-07 17:33:04+01:00, mleich@five.local.lan +0 -0

  mysql-test/suite/funcs_1/r/is_collation_character_set_applicability.result@1.1, 2008-03-07 17:33:04+01:00, mleich@five.local.lan +76 -0
    Expected result for new test

  mysql-test/suite/funcs_1/r/is_collation_character_set_applicability.result@1.0, 2008-03-07 17:33:04+01:00, mleich@five.local.lan +0 -0

  mysql-test/suite/funcs_1/r/is_collations.result@1.1, 2008-03-07 17:33:04+01:00, mleich@five.local.lan +90 -0
    Expected result for new test

  mysql-test/suite/funcs_1/r/is_collations.result@1.0, 2008-03-07 17:33:04+01:00, mleich@five.local.lan +0 -0

  mysql-test/suite/funcs_1/r/is_column_privileges.result@1.1, 2008-03-07 17:33:04+01:00, mleich@five.local.lan +370 -0
    Expected result for new test

  mysql-test/suite/funcs_1/r/is_column_privileges.result@1.0, 2008-03-07 17:33:04+01:00, mleich@five.local.lan +0 -0

  mysql-test/suite/funcs_1/r/is_column_privileges_is_mysql_test.result@1.1, 2008-03-07 17:33:04+01:00, mleich@five.local.lan +37 -0
    Expected result for new test

  mysql-test/suite/funcs_1/r/is_column_privileges_is_mysql_test.result@1.0, 2008-03-07 17:33:04+01:00, mleich@five.local.lan +0 -0

  mysql-test/suite/funcs_1/r/is_columns.result@1.1, 2008-03-07 17:33:04+01:00, mleich@five.local.lan +486 -0
    Expected result for new test

  mysql-test/suite/funcs_1/r/is_columns.result@1.0, 2008-03-07 17:33:04+01:00, mleich@five.local.lan +0 -0

  mysql-test/suite/funcs_1/r/is_columns_innodb.result@1.1, 2008-03-07 17:33:04+01:00, mleich@five.local.lan +1130 -0
    Expected result for new test

  mysql-test/suite/funcs_1/r/is_columns_innodb.result@1.0, 2008-03-07 17:33:04+01:00, mleich@five.local.lan +0 -0

  mysql-test/suite/funcs_1/r/is_columns_is.result@1.1, 2008-03-07 17:33:04+01:00, mleich@five.local.lan +380 -0
    Expected result for new test

  mysql-test/suite/funcs_1/r/is_columns_is.result@1.0, 2008-03-07 17:33:04+01:00, mleich@five.local.lan +0 -0

  mysql-test/suite/funcs_1/r/is_columns_memory.result@1.1, 2008-03-07 17:33:04+01:00, mleich@five.local.lan +1076 -0
    Expected result for new test

  mysql-test/suite/funcs_1/r/is_columns_memory.result@1.0, 2008-03-07 17:33:04+01:00, mleich@five.local.lan +0 -0

  mysql-test/suite/funcs_1/r/is_columns_myisam.result@1.1, 2008-03-07 17:33:04+01:00, mleich@five.local.lan +1207 -0
    Expected result for new test

  mysql-test/suite/funcs_1/r/is_columns_myisam.result@1.0, 2008-03-07 17:33:04+01:00, mleich@five.local.lan +0 -0

  mysql-test/suite/funcs_1/r/is_columns_mysql.result@1.1, 2008-03-07 17:33:04+01:00, mleich@five.local.lan +361 -0
    Expected result for new test

  mysql-test/suite/funcs_1/r/is_columns_mysql.result@1.0, 2008-03-07 17:33:04+01:00, mleich@five.local.lan +0 -0

  mysql-test/suite/funcs_1/r/is_columns_ndb.result@1.1, 2008-03-07 17:33:04+01:00, mleich@five.local.lan +223 -0
    Expected result for new test

  mysql-test/suite/funcs_1/r/is_columns_ndb.result@1.0, 2008-03-07 17:33:04+01:00, mleich@five.local.lan +0 -0

  mysql-test/suite/funcs_1/r/is_key_column_usage.result@1.1, 2008-03-07 17:33:04+01:00, mleich@five.local.lan +370 -0
    Expected result for new test

  mysql-test/suite/funcs_1/r/is_key_column_usage.result@1.0, 2008-03-07 17:33:04+01:00, mleich@five.local.lan +0 -0

  mysql-test/suite/funcs_1/r/is_routines.result@1.1, 2008-03-07 17:33:04+01:00, mleich@five.local.lan +605 -0
    Expected result for new test

  mysql-test/suite/funcs_1/r/is_routines.result@1.0, 2008-03-07 17:33:04+01:00, mleich@five.local.lan +0 -0

  mysql-test/suite/funcs_1/r/is_schema_privileges.result@1.1, 2008-03-07 17:33:04+01:00, mleich@five.local.lan +304 -0
    Expected result for new test

  mysql-test/suite/funcs_1/r/is_schema_privileges.result@1.0, 2008-03-07 17:33:04+01:00, mleich@five.local.lan +0 -0

  mysql-test/suite/funcs_1/r/is_schema_privileges_is_mysql_test.result@1.1, 2008-03-07 17:33:04+01:00, mleich@five.local.lan +51 -0
    Expected result for new test

  mysql-test/suite/funcs_1/r/is_schema_privileges_is_mysql_test.result@1.0, 2008-03-07 17:33:04+01:00, mleich@five.local.lan +0 -0

  mysql-test/suite/funcs_1/r/is_schemata.result@1.1, 2008-03-07 17:33:04+01:00, mleich@five.local.lan +181 -0
    Expected result for new test

  mysql-test/suite/funcs_1/r/is_schemata.result@1.0, 2008-03-07 17:33:04+01:00, mleich@five.local.lan +0 -0

  mysql-test/suite/funcs_1/r/is_schemata_is_mysql_test.result@1.1, 2008-03-07 17:33:04+01:00, mleich@five.local.lan +42 -0
    Expected result for new test

  mysql-test/suite/funcs_1/r/is_schemata_is_mysql_test.result@1.0, 2008-03-07 17:33:04+01:00, mleich@five.local.lan +0 -0

  mysql-test/suite/funcs_1/r/is_statistics.result@1.1, 2008-03-07 17:33:04+01:00, mleich@five.local.lan +352 -0
    Expected result for new test

  mysql-test/suite/funcs_1/r/is_statistics.result@1.0, 2008-03-07 17:33:04+01:00, mleich@five.local.lan +0 -0

  mysql-test/suite/funcs_1/r/is_statistics_is.result@1.1, 2008-03-07 17:33:04+01:00, mleich@five.local.lan +17 -0
    Expected result for new test

  mysql-test/suite/funcs_1/r/is_statistics_is.result@1.0, 2008-03-07 17:33:04+01:00, mleich@five.local.lan +0 -0

  mysql-test/suite/funcs_1/r/is_statistics_mysql.result@1.1, 2008-03-07 17:33:04+01:00, mleich@five.local.lan +60 -0
    Expected result for new test

  mysql-test/suite/funcs_1/r/is_statistics_mysql.result@1.0, 2008-03-07 17:33:04+01:00, mleich@five.local.lan +0 -0

  mysql-test/suite/funcs_1/r/is_table_constraints.result@1.1, 2008-03-07 17:33:04+01:00, mleich@five.local.lan +310 -0
    Expected result for new test

  mysql-test/suite/funcs_1/r/is_table_constraints.result@1.0, 2008-03-07 17:33:04+01:00, mleich@five.local.lan +0 -0

  mysql-test/suite/funcs_1/r/is_table_constraints_is.result@1.1, 2008-03-07 17:33:04+01:00, mleich@five.local.lan +17 -0
    Expected result for new test

  mysql-test/suite/funcs_1/r/is_table_constraints_is.result@1.0, 2008-03-07 17:33:04+01:00, mleich@five.local.lan +0 -0

  mysql-test/suite/funcs_1/r/is_table_constraints_mysql.result@1.1, 2008-03-07 17:33:04+01:00, mleich@five.local.lan +37 -0
    Expected result for new test

  mysql-test/suite/funcs_1/r/is_table_constraints_mysql.result@1.0, 2008-03-07 17:33:04+01:00, mleich@five.local.lan +0 -0

  mysql-test/suite/funcs_1/r/is_table_privileges.result@1.1, 2008-03-07 17:33:04+01:00, mleich@five.local.lan +332 -0
    Expected result for new test

  mysql-test/suite/funcs_1/r/is_table_privileges.result@1.0, 2008-03-07 17:33:04+01:00, mleich@five.local.lan +0 -0

  mysql-test/suite/funcs_1/r/is_tables.result@1.1, 2008-03-07 17:33:04+01:00, mleich@five.local.lan +419 -0
    Expected result for new test

  mysql-test/suite/funcs_1/r/is_tables.result@1.0, 2008-03-07 17:33:04+01:00, mleich@five.local.lan +0 -0

  mysql-test/suite/funcs_1/r/is_tables_innodb.result@1.1, 2008-03-07 17:33:04+01:00, mleich@five.local.lan +1063 -0
    Expected result for new test

  mysql-test/suite/funcs_1/r/is_tables_innodb.result@1.0, 2008-03-07 17:33:04+01:00, mleich@five.local.lan +0 -0

  mysql-test/suite/funcs_1/r/is_tables_is.result@1.1, 2008-03-07 17:33:04+01:00, mleich@five.local.lan +771 -0
    Expected result for new test

  mysql-test/suite/funcs_1/r/is_tables_is.result@1.0, 2008-03-07 17:33:04+01:00, mleich@five.local.lan +0 -0

  mysql-test/suite/funcs_1/r/is_tables_memory.result@1.1, 2008-03-07 17:33:04+01:00, mleich@five.local.lan +1052 -0
    Expected result for new test

  mysql-test/suite/funcs_1/r/is_tables_memory.result@1.0, 2008-03-07 17:33:04+01:00, mleich@five.local.lan +0 -0

  mysql-test/suite/funcs_1/r/is_tables_myisam.result@1.1, 2008-03-07 17:33:04+01:00, mleich@five.local.lan +1092 -0
    Expected result for new test

  mysql-test/suite/funcs_1/r/is_tables_myisam.result@1.0, 2008-03-07 17:33:04+01:00, mleich@five.local.lan +0 -0

  mysql-test/suite/funcs_1/r/is_tables_mysql.result@1.1, 2008-03-07 17:33:04+01:00, mleich@five.local.lan +424 -0
    Expected result for new test

  mysql-test/suite/funcs_1/r/is_tables_mysql.result@1.0, 2008-03-07 17:33:04+01:00, mleich@five.local.lan +0 -0

  mysql-test/suite/funcs_1/r/is_tables_ndb.result@1.1, 2008-03-07 17:33:04+01:00, mleich@five.local.lan +560 -0
    Expected result for new test

  mysql-test/suite/funcs_1/r/is_tables_ndb.result@1.0, 2008-03-07 17:33:04+01:00, mleich@five.local.lan +0 -0

  mysql-test/suite/funcs_1/r/is_triggers.result@1.1, 2008-03-07 17:33:04+01:00, mleich@five.local.lan +212 -0
    Expected result for new test

  mysql-test/suite/funcs_1/r/is_triggers.result@1.0, 2008-03-07 17:33:04+01:00, mleich@five.local.lan +0 -0

  mysql-test/suite/funcs_1/r/is_user_privileges.result@1.1, 2008-03-07 17:33:04+01:00, mleich@five.local.lan +400 -0
    Expected result for new test

  mysql-test/suite/funcs_1/r/is_user_privileges.result@1.0, 2008-03-07 17:33:04+01:00, mleich@five.local.lan +0 -0

  mysql-test/suite/funcs_1/r/is_views.result@1.1, 2008-03-07 17:33:04+01:00, mleich@five.local.lan +238 -0
    Expected result for new test

  mysql-test/suite/funcs_1/r/is_views.result@1.0, 2008-03-07 17:33:04+01:00, mleich@five.local.lan +0 -0

  mysql-test/suite/funcs_1/r/memory_bitdata.result@1.2, 2008-03-07 17:33:01+01:00, mleich@five.local.lan +0 -65
    Updated results

  mysql-test/suite/funcs_1/r/memory_cursors.result@1.2, 2008-03-07 17:33:01+01:00, mleich@five.local.lan +0 -75
    Updated results

  mysql-test/suite/funcs_1/r/memory_storedproc_02.result@1.2, 2008-03-07 17:33:01+01:00, mleich@five.local.lan +0 -2
    Updated results

  mysql-test/suite/funcs_1/r/memory_storedproc_03.result@1.2, 2008-03-07 17:33:01+01:00, mleich@five.local.lan +0 -2
    Updated results

  mysql-test/suite/funcs_1/r/memory_storedproc_06.result@1.2, 2008-03-07 17:33:01+01:00, mleich@five.local.lan +0 -2
    Updated results

  mysql-test/suite/funcs_1/r/memory_storedproc_07.result@1.2, 2008-03-07 17:33:01+01:00, mleich@five.local.lan +0 -2
    Updated results

  mysql-test/suite/funcs_1/r/memory_storedproc_08.result@1.2, 2008-03-07 17:33:01+01:00, mleich@five.local.lan +0 -2
    Updated results

  mysql-test/suite/funcs_1/r/memory_storedproc_10.result@1.2, 2008-03-07 17:33:01+01:00, mleich@five.local.lan +0 -2
    Updated results

  mysql-test/suite/funcs_1/r/memory_trig_0102.result@1.3, 2008-03-07 17:33:01+01:00, mleich@five.local.lan +1 -3
    Updated results

  mysql-test/suite/funcs_1/r/memory_trig_03.result@1.2, 2008-03-07 17:33:01+01:00, mleich@five.local.lan +1 -3
    Updated results

  mysql-test/suite/funcs_1/r/memory_trig_0407.result@1.2, 2008-03-07 17:33:01+01:00, mleich@five.local.lan +1 -3
    Updated results

  mysql-test/suite/funcs_1/r/memory_trig_08.result@1.4, 2008-03-07 17:33:01+01:00, mleich@five.local.lan +1 -3
    Updated results

  mysql-test/suite/funcs_1/r/memory_trig_09.result@1.3, 2008-03-07 17:33:01+01:00, mleich@five.local.lan +1 -3
    Updated results

  mysql-test/suite/funcs_1/r/memory_trig_1011ext.result@1.2, 2008-03-07 17:33:01+01:00, mleich@five.local.lan +1 -3
    Updated results

  mysql-test/suite/funcs_1/r/memory_views.result@1.5, 2008-03-07 17:33:01+01:00, mleich@five.local.lan +2 -6
    Updated results

  mysql-test/suite/funcs_1/r/myisam_bitdata.result@1.2, 2008-03-07 17:33:01+01:00, mleich@five.local.lan +0 -73
    Updated results

  mysql-test/suite/funcs_1/r/myisam_cursors.result@1.2, 2008-03-07 17:33:01+01:00, mleich@five.local.lan +0 -81
    Updated results

  mysql-test/suite/funcs_1/r/myisam_storedproc_02.result@1.2, 2008-03-07 17:33:01+01:00, mleich@five.local.lan +0 -2
    Updated results

  mysql-test/suite/funcs_1/r/myisam_storedproc_03.result@1.2, 2008-03-07 17:33:01+01:00, mleich@five.local.lan +0 -2
    Updated results

  mysql-test/suite/funcs_1/r/myisam_storedproc_06.result@1.2, 2008-03-07 17:33:01+01:00, mleich@five.local.lan +0 -2
    Updated results

  mysql-test/suite/funcs_1/r/myisam_storedproc_07.result@1.2, 2008-03-07 17:33:01+01:00, mleich@five.local.lan +0 -2
    Updated results

  mysql-test/suite/funcs_1/r/myisam_storedproc_08.result@1.2, 2008-03-07 17:33:01+01:00, mleich@five.local.lan +0 -2
    Updated results

  mysql-test/suite/funcs_1/r/myisam_storedproc_10.result@1.2, 2008-03-07 17:33:01+01:00, mleich@five.local.lan +0 -2
    Updated results

  mysql-test/suite/funcs_1/r/myisam_trig_0102.result@1.3, 2008-03-07 17:33:01+01:00, mleich@five.local.lan +1 -1
    Updated results

  mysql-test/suite/funcs_1/r/myisam_trig_03.result@1.2, 2008-03-07 17:33:01+01:00, mleich@five.local.lan +1 -1
    Updated results

  mysql-test/suite/funcs_1/r/myisam_trig_0407.result@1.2, 2008-03-07 17:33:01+01:00, mleich@five.local.lan +1 -1
    Updated results

  mysql-test/suite/funcs_1/r/myisam_trig_08.result@1.4, 2008-03-07 17:33:01+01:00, mleich@five.local.lan +1 -1
    Updated results

  mysql-test/suite/funcs_1/r/myisam_trig_09.result@1.3, 2008-03-07 17:33:02+01:00, mleich@five.local.lan +1 -1
    Updated results

  mysql-test/suite/funcs_1/r/myisam_trig_1011ext.result@1.2, 2008-03-07 17:33:02+01:00, mleich@five.local.lan +1 -1
    Updated results

  mysql-test/suite/funcs_1/r/myisam_views.result@1.5, 2008-03-07 17:33:02+01:00, mleich@five.local.lan +9379 -9379
    Updated results

  mysql-test/suite/funcs_1/storedproc/load_sp_tb.inc@1.2, 2008-03-07 17:33:02+01:00, mleich@five.local.lan +0 -3
    Move setting of variables into the caller scripts

  mysql-test/suite/funcs_1/storedproc/storedproc_02.inc@1.2, 2008-03-07 16:29:40+01:00, mleich@five.local.lan +0 -0
    Change mode to -rw-rw-r--

  mysql-test/suite/funcs_1/storedproc/storedproc_03.inc@1.2, 2008-03-07 16:29:40+01:00, mleich@five.local.lan +0 -0
    Change mode to -rw-rw-r--

  mysql-test/suite/funcs_1/storedproc/storedproc_06.inc@1.2, 2008-03-07 16:29:40+01:00, mleich@five.local.lan +0 -0
    Change mode to -rw-rw-r--

  mysql-test/suite/funcs_1/storedproc/storedproc_07.inc@1.2, 2008-03-07 16:29:40+01:00, mleich@five.local.lan +0 -0
    Change mode to -rw-rw-r--

  mysql-test/suite/funcs_1/storedproc/storedproc_08.inc@1.2, 2008-03-07 16:29:40+01:00, mleich@five.local.lan +0 -0
    Change mode to -rw-rw-r--

  mysql-test/suite/funcs_1/storedproc/storedproc_08_show.inc@1.2, 2008-03-07 16:29:40+01:00, mleich@five.local.lan +0 -0
    Change mode to -rw-rw-r--

  mysql-test/suite/funcs_1/storedproc/storedproc_10.inc@1.2, 2008-03-07 16:29:40+01:00, mleich@five.local.lan +0 -0
    Change mode to -rw-rw-r--

  mysql-test/suite/funcs_1/t/charset_collation_1.test@1.1, 2008-03-07 17:33:03+01:00, mleich@five.local.lan +30 -0
    Check content of information_schema views
       character_sets, collations,
       collation_character_set_applicability
    Build variant 1

  mysql-test/suite/funcs_1/t/charset_collation_1.test@1.0, 2008-03-07 17:33:03+01:00, mleich@five.local.lan +0 -0

  mysql-test/suite/funcs_1/t/charset_collation_2.test@1.1, 2008-03-07 17:33:03+01:00, mleich@five.local.lan +24 -0
    Check content of information_schema views
       character_sets, collations,
       collation_character_set_applicability
    Build variant 2

  mysql-test/suite/funcs_1/t/charset_collation_2.test@1.0, 2008-03-07 17:33:03+01:00, mleich@five.local.lan +0 -0

  mysql-test/suite/funcs_1/t/charset_collation_3.test@1.1, 2008-03-07 17:33:03+01:00, mleich@five.local.lan +24 -0
    Check content of information_schema views
       character_sets, collations,
       collation_character_set_applicability
    Build variant 3

  mysql-test/suite/funcs_1/t/charset_collation_3.test@1.0, 2008-03-07 17:33:03+01:00, mleich@five.local.lan +0 -0

  mysql-test/suite/funcs_1/t/innodb_bitdata.test@1.2, 2008-03-07 17:33:02+01:00, mleich@five.local.lan +6 -23
    Cleanup

  mysql-test/suite/funcs_1/t/innodb_cursors.test@1.2, 2008-03-07 17:33:02+01:00, mleich@five.local.lan +6 -21
    Cleanup

  mysql-test/suite/funcs_1/t/innodb_storedproc_02.test@1.2, 2008-03-07 16:27:45+01:00, mleich@five.local.lan +0 -0
    Change mode to -rw-rw-r--

  mysql-test/suite/funcs_1/t/innodb_storedproc_03.test@1.2, 2008-03-07 16:27:45+01:00, mleich@five.local.lan +0 -0
    Change mode to -rw-rw-r--

  mysql-test/suite/funcs_1/t/innodb_storedproc_06.test@1.2, 2008-03-07 16:27:45+01:00, mleich@five.local.lan +0 -0
    Change mode to -rw-rw-r--

  mysql-test/suite/funcs_1/t/innodb_storedproc_07.test@1.2, 2008-03-07 16:27:45+01:00, mleich@five.local.lan +0 -0
    Change mode to -rw-rw-r--

  mysql-test/suite/funcs_1/t/innodb_storedproc_08.test@1.2, 2008-03-07 16:27:45+01:00, mleich@five.local.lan +0 -0
    Change mode to -rw-rw-r--

  mysql-test/suite/funcs_1/t/innodb_storedproc_10.test@1.2, 2008-03-07 16:27:45+01:00, mleich@five.local.lan +0 -0
    Change mode to -rw-rw-r--

  mysql-test/suite/funcs_1/t/innodb_trig_0102.test@1.2, 2008-03-07 17:33:03+01:00, mleich@five.local.lan +4 -22
    Cleanup

  mysql-test/suite/funcs_1/t/innodb_trig_03.test@1.2, 2008-03-07 17:33:03+01:00, mleich@five.local.lan +4 -22
    Cleanup

  mysql-test/suite/funcs_1/t/innodb_trig_0407.test@1.2, 2008-03-07 17:33:03+01:00, mleich@five.local.lan +4 -22
    Cleanup

  mysql-test/suite/funcs_1/t/innodb_trig_08.test@1.2, 2008-03-07 17:33:03+01:00, mleich@five.local.lan +4 -22
    Cleanup

  mysql-test/suite/funcs_1/t/innodb_trig_09.test@1.2, 2008-03-07 17:33:03+01:00, mleich@five.local.lan +4 -22
    Cleanup

  mysql-test/suite/funcs_1/t/innodb_trig_1011ext.test@1.2, 2008-03-07 17:33:03+01:00, mleich@five.local.lan +4 -22
    Cleanup

  mysql-test/suite/funcs_1/t/innodb_trig_frkey.test@1.2, 2008-03-07 17:33:03+01:00, mleich@five.local.lan +4 -22
    Cleanup

  mysql-test/suite/funcs_1/t/innodb_views.test@1.2, 2008-03-07 17:33:03+01:00, mleich@five.local.lan +12 -34
    Cleanup

  mysql-test/suite/funcs_1/t/is_basics_mixed.test@1.1, 2008-03-07 17:33:03+01:00, mleich@five.local.lan +503 -0
    Test some basic properties which are independend of the storage
    engine used for the creation of tables.

  mysql-test/suite/funcs_1/t/is_basics_mixed.test@1.0, 2008-03-07 17:33:03+01:00, mleich@five.local.lan +0 -0

  mysql-test/suite/funcs_1/t/is_character_sets.test@1.1, 2008-03-07 17:33:03+01:00, mleich@five.local.lan +107 -0
    Tests related to functionality of
    information_schema.character_sets

  mysql-test/suite/funcs_1/t/is_character_sets.test@1.0, 2008-03-07 17:33:03+01:00, mleich@five.local.lan +0 -0

  mysql-test/suite/funcs_1/t/is_collation_character_set_applicability.test@1.1, 2008-03-07 17:33:03+01:00, mleich@five.local.lan +108 -0
    Tests related to functionality of
    information_schema.collation_character_set_applicability

  mysql-test/suite/funcs_1/t/is_collation_character_set_applicability.test@1.0, 2008-03-07 17:33:03+01:00, mleich@five.local.lan +0 -0

  mysql-test/suite/funcs_1/t/is_collations.test@1.1, 2008-03-07 17:33:03+01:00, mleich@five.local.lan +114 -0
    Tests related to functionality of
    information_schema.collations

  mysql-test/suite/funcs_1/t/is_collations.test@1.0, 2008-03-07 17:33:03+01:00, mleich@five.local.lan +0 -0

  mysql-test/suite/funcs_1/t/is_column_privileges.test@1.1, 2008-03-07 17:33:03+01:00, mleich@five.local.lan +351 -0
    Tests related to functionality of
    information_schema.column_privileges

  mysql-test/suite/funcs_1/t/is_column_privileges.test@1.0, 2008-03-07 17:33:03+01:00, mleich@five.local.lan +0 -0

  mysql-test/suite/funcs_1/t/is_column_privileges_is_mysql_test.test@1.1, 2008-03-07 17:33:03+01:00, mleich@five.local.lan +58 -0
    Check content of information_schema.column_privileges about databases
    mysql and test

  mysql-test/suite/funcs_1/t/is_column_privileges_is_mysql_test.test@1.0, 2008-03-07 17:33:03+01:00, mleich@five.local.lan +0 -0

  mysql-test/suite/funcs_1/t/is_columns.test@1.1, 2008-03-07 17:33:03+01:00, mleich@five.local.lan +444 -0
    Tests related to functionality of
    information_schema.columns

  mysql-test/suite/funcs_1/t/is_columns.test@1.0, 2008-03-07 17:33:03+01:00, mleich@five.local.lan +0 -0

  mysql-test/suite/funcs_1/t/is_columns_innodb.test@1.1, 2008-03-07 17:33:03+01:00, mleich@five.local.lan +21 -0
    Check content of information_schema.columns when some
    tables are preloaded
    Variant for InnoDB

  mysql-test/suite/funcs_1/t/is_columns_innodb.test@1.0, 2008-03-07 17:33:03+01:00, mleich@five.local.lan +0 -0

  mysql-test/suite/funcs_1/t/is_columns_is.test@1.1, 2008-03-07 17:33:03+01:00, mleich@five.local.lan +19 -0
    Check content of information_schema.columns about schema
    information_schema

  mysql-test/suite/funcs_1/t/is_columns_is.test@1.0, 2008-03-07 17:33:03+01:00, mleich@five.local.lan +0 -0

  mysql-test/suite/funcs_1/t/is_columns_memory.test@1.1, 2008-03-07 17:33:03+01:00, mleich@five.local.lan +21 -0
    Check content of information_schema.columns when some
    tables are preloaded
    Variant for MEMORY

  mysql-test/suite/funcs_1/t/is_columns_memory.test@1.0, 2008-03-07 17:33:03+01:00, mleich@five.local.lan +0 -0

  mysql-test/suite/funcs_1/t/is_columns_myisam.test@1.1, 2008-03-07 17:33:03+01:00, mleich@five.local.lan +21 -0
    Check content of information_schema.columns when some
    tables are preloaded
    Variant for MyISAM

  mysql-test/suite/funcs_1/t/is_columns_myisam.test@1.0, 2008-03-07 17:33:03+01:00, mleich@five.local.lan +0 -0

  mysql-test/suite/funcs_1/t/is_columns_mysql.test@1.1, 2008-03-07 17:33:03+01:00, mleich@five.local.lan +13 -0
    Check content of information_schema.columns about schema
    mysql

  mysql-test/suite/funcs_1/t/is_columns_mysql.test@1.0, 2008-03-07 17:33:03+01:00, mleich@five.local.lan +0 -0

  mysql-test/suite/funcs_1/t/is_columns_ndb.test@1.1, 2008-03-07 17:33:03+01:00, mleich@five.local.lan +33 -0
    Check content of information_schema.columns when some
    tables are preloaded
    Variant for NDB

  mysql-test/suite/funcs_1/t/is_columns_ndb.test@1.0, 2008-03-07 17:33:03+01:00, mleich@five.local.lan +0 -0

  mysql-test/suite/funcs_1/t/is_key_column_usage.test@1.1, 2008-03-07 17:33:03+01:00, mleich@five.local.lan +344 -0
    Tests related to functionality of
    information_schema.key_column_usage

  mysql-test/suite/funcs_1/t/is_key_column_usage.test@1.0, 2008-03-07 17:33:03+01:00, mleich@five.local.lan +0 -0

  mysql-test/suite/funcs_1/t/is_routines.test@1.1, 2008-03-07 17:33:03+01:00, mleich@five.local.lan +471 -0
    Tests related to functionality of
    information_schema.routines

  mysql-test/suite/funcs_1/t/is_routines.test@1.0, 2008-03-07 17:33:03+01:00, mleich@five.local.lan +0 -0

  mysql-test/suite/funcs_1/t/is_schema_privileges.test@1.1, 2008-03-07 17:33:03+01:00, mleich@five.local.lan +336 -0
    Tests related to functionality of
    information_schema.schema_privileges

  mysql-test/suite/funcs_1/t/is_schema_privileges.test@1.0, 2008-03-07 17:33:03+01:00, mleich@five.local.lan +0 -0

  mysql-test/suite/funcs_1/t/is_schema_privileges_is_mysql_test.test@1.1, 2008-03-07 17:33:03+01:00, mleich@five.local.lan +58 -0
    Check content of information_schema.schema_privileges about schemas
    information_schema, mysql and test

  mysql-test/suite/funcs_1/t/is_schema_privileges_is_mysql_test.test@1.0, 2008-03-07 17:33:03+01:00, mleich@five.local.lan +0 -0

  mysql-test/suite/funcs_1/t/is_schemata.test@1.1, 2008-03-07 17:33:03+01:00, mleich@five.local.lan +246 -0
    Tests related to functionality of
    information_schema.schemata

  mysql-test/suite/funcs_1/t/is_schemata.test@1.0, 2008-03-07 17:33:03+01:00, mleich@five.local.lan +0 -0

  mysql-test/suite/funcs_1/t/is_schemata_is_mysql_test.test@1.1, 2008-03-07 17:33:03+01:00, mleich@five.local.lan +58 -0
    Check content of information_schema.schemata about schemas
    information_schema, mysql and test

  mysql-test/suite/funcs_1/t/is_schemata_is_mysql_test.test@1.0, 2008-03-07 17:33:03+01:00, mleich@five.local.lan +0 -0

  mysql-test/suite/funcs_1/t/is_statistics.test@1.1, 2008-03-07 17:33:03+01:00, mleich@five.local.lan +379 -0
    Tests related to functionality of
    information_schema.statistics

  mysql-test/suite/funcs_1/t/is_statistics.test@1.0, 2008-03-07 17:33:03+01:00, mleich@five.local.lan +0 -0

  mysql-test/suite/funcs_1/t/is_statistics_is.test@1.1, 2008-03-07 17:33:03+01:00, mleich@five.local.lan +14 -0
    Check content of information_schema.statistics about schema
    information_schema

  mysql-test/suite/funcs_1/t/is_statistics_is.test@1.0, 2008-03-07 17:33:03+01:00, mleich@five.local.lan +0 -0

  mysql-test/suite/funcs_1/t/is_statistics_mysql.test@1.1, 2008-03-07 17:33:03+01:00, mleich@five.local.lan +15 -0
    Check content of information_schema.statistics about schema
    mysql

  mysql-test/suite/funcs_1/t/is_statistics_mysql.test@1.0, 2008-03-07 17:33:03+01:00, mleich@five.local.lan +0 -0

  mysql-test/suite/funcs_1/t/is_table_constraints.test@1.1, 2008-03-07 17:33:03+01:00, mleich@five.local.lan +331 -0
    Tests related to functionality of
    information_schema.table_constraints

  mysql-test/suite/funcs_1/t/is_table_constraints.test@1.0, 2008-03-07 17:33:03+01:00, mleich@five.local.lan +0 -0

  mysql-test/suite/funcs_1/t/is_table_constraints_is.test@1.1, 2008-03-07 17:33:03+01:00, mleich@five.local.lan +14 -0
    Check content of information_schema.table_constraints about schema
    information_schema

  mysql-test/suite/funcs_1/t/is_table_constraints_is.test@1.0, 2008-03-07 17:33:03+01:00, mleich@five.local.lan +0 -0

  mysql-test/suite/funcs_1/t/is_table_constraints_mysql.test@1.1, 2008-03-07 17:33:03+01:00, mleich@five.local.lan +14 -0
    Check content of information_schema.table_constraints about schema
    mysql

  mysql-test/suite/funcs_1/t/is_table_constraints_mysql.test@1.0, 2008-03-07 17:33:03+01:00, mleich@five.local.lan +0 -0

  mysql-test/suite/funcs_1/t/is_table_privileges.test@1.1, 2008-03-07 17:33:03+01:00, mleich@five.local.lan +349 -0
    Tests related to functionality of
    information_schema.table_privileges

  mysql-test/suite/funcs_1/t/is_table_privileges.test@1.0, 2008-03-07 17:33:03+01:00, mleich@five.local.lan +0 -0

  mysql-test/suite/funcs_1/t/is_tables.test@1.1, 2008-03-07 17:33:04+01:00, mleich@five.local.lan +474 -0
    Tests related to functionality of
    information_schema.tables

  mysql-test/suite/funcs_1/t/is_tables.test@1.0, 2008-03-07 17:33:04+01:00, mleich@five.local.lan +0 -0

  mysql-test/suite/funcs_1/t/is_tables_innodb.test@1.1, 2008-03-07 17:33:04+01:00, mleich@five.local.lan +22 -0
    Check content of information_schema.tables when some
    tables are preloaded
    Variant for InnoDB

  mysql-test/suite/funcs_1/t/is_tables_innodb.test@1.0, 2008-03-07 17:33:04+01:00, mleich@five.local.lan +0 -0

  mysql-test/suite/funcs_1/t/is_tables_is.test@1.1, 2008-03-07 17:33:04+01:00, mleich@five.local.lan +18 -0
    Check content of information_schema.tables about schema
    information_schema

  mysql-test/suite/funcs_1/t/is_tables_is.test@1.0, 2008-03-07 17:33:04+01:00, mleich@five.local.lan +0 -0

  mysql-test/suite/funcs_1/t/is_tables_memory.test@1.1, 2008-03-07 17:33:04+01:00, mleich@five.local.lan +22 -0
    Check content of information_schema.tables when some
    tables are preloaded
    Variant for MEMORY

  mysql-test/suite/funcs_1/t/is_tables_memory.test@1.0, 2008-03-07 17:33:04+01:00, mleich@five.local.lan +0 -0

  mysql-test/suite/funcs_1/t/is_tables_myisam.test@1.1, 2008-03-07 17:33:04+01:00, mleich@five.local.lan +22 -0
    Check content of information_schema.tables when some
    tables are preloaded
    Variant for MyISAM

  mysql-test/suite/funcs_1/t/is_tables_myisam.test@1.0, 2008-03-07 17:33:04+01:00, mleich@five.local.lan +0 -0

  mysql-test/suite/funcs_1/t/is_tables_mysql.test@1.1, 2008-03-07 17:33:04+01:00, mleich@five.local.lan +14 -0
    Check content of information_schema.tables about schema
    mysql

  mysql-test/suite/funcs_1/t/is_tables_mysql.test@1.0, 2008-03-07 17:33:04+01:00, mleich@five.local.lan +0 -0

  mysql-test/suite/funcs_1/t/is_tables_ndb.test@1.1, 2008-03-07 17:33:04+01:00, mleich@five.local.lan +34 -0
    Check content of information_schema.tables when some
    tables are preloaded
    Variant for NDB

  mysql-test/suite/funcs_1/t/is_tables_ndb.test@1.0, 2008-03-07 17:33:04+01:00, mleich@five.local.lan +0 -0

  mysql-test/suite/funcs_1/t/is_triggers.test@1.1, 2008-03-07 17:33:04+01:00, mleich@five.local.lan +253 -0
    Tests related to functionality of
    information_schema.triggers

  mysql-test/suite/funcs_1/t/is_triggers.test@1.0, 2008-03-07 17:33:04+01:00, mleich@five.local.lan +0 -0

  mysql-test/suite/funcs_1/t/is_user_privileges.test@1.1, 2008-03-07 17:33:04+01:00, mleich@five.local.lan +347 -0
    Tests related to functionality of
    information_schema.user_privileges

  mysql-test/suite/funcs_1/t/is_user_privileges.test@1.0, 2008-03-07 17:33:04+01:00, mleich@five.local.lan +0 -0

  mysql-test/suite/funcs_1/t/is_views.test@1.1, 2008-03-07 17:33:04+01:00, mleich@five.local.lan +305 -0
    Tests related to functionality of
    information_schema.views

  mysql-test/suite/funcs_1/t/is_views.test@1.0, 2008-03-07 17:33:04+01:00, mleich@five.local.lan +0 -0

  mysql-test/suite/funcs_1/t/memory_bitdata.test@1.2, 2008-03-07 17:33:03+01:00, mleich@five.local.lan +7 -23
    Cleanup

  mysql-test/suite/funcs_1/t/memory_cursors.test@1.2, 2008-03-07 17:33:03+01:00, mleich@five.local.lan +6 -21
    Cleanup

  mysql-test/suite/funcs_1/t/memory_storedproc_02.test@1.2, 2008-03-07 16:27:45+01:00, mleich@five.local.lan +0 -0
    Change mode to -rw-rw-r--

  mysql-test/suite/funcs_1/t/memory_storedproc_03.test@1.2, 2008-03-07 16:27:45+01:00, mleich@five.local.lan +0 -0
    Change mode to -rw-rw-r--

  mysql-test/suite/funcs_1/t/memory_storedproc_06.test@1.2, 2008-03-07 16:27:45+01:00, mleich@five.local.lan +0 -0
    Change mode to -rw-rw-r--

  mysql-test/suite/funcs_1/t/memory_storedproc_07.test@1.2, 2008-03-07 16:27:45+01:00, mleich@five.local.lan +0 -0
    Change mode to -rw-rw-r--

  mysql-test/suite/funcs_1/t/memory_storedproc_08.test@1.2, 2008-03-07 16:27:45+01:00, mleich@five.local.lan +0 -0
    Change mode to -rw-rw-r--

  mysql-test/suite/funcs_1/t/memory_storedproc_10.test@1.2, 2008-03-07 16:27:45+01:00, mleich@five.local.lan +0 -0
    Change mode to -rw-rw-r--

  mysql-test/suite/funcs_1/t/memory_trig_0102.test@1.2, 2008-03-07 17:33:03+01:00, mleich@five.local.lan +4 -22
    Cleanup

  mysql-test/suite/funcs_1/t/memory_trig_03.test@1.2, 2008-03-07 17:33:03+01:00, mleich@five.local.lan +4 -22
    Cleanup

  mysql-test/suite/funcs_1/t/memory_trig_0407.test@1.2, 2008-03-07 17:33:03+01:00, mleich@five.local.lan +4 -22
    Cleanup

  mysql-test/suite/funcs_1/t/memory_trig_08.test@1.2, 2008-03-07 17:33:03+01:00, mleich@five.local.lan +4 -22
    Cleanup

  mysql-test/suite/funcs_1/t/memory_trig_09.test@1.2, 2008-03-07 17:33:03+01:00, mleich@five.local.lan +4 -22
    Cleanup

  mysql-test/suite/funcs_1/t/memory_trig_1011ext.test@1.2, 2008-03-07 17:33:03+01:00, mleich@five.local.lan +4 -22
    Cleanup

  mysql-test/suite/funcs_1/t/memory_views.test@1.2, 2008-03-07 17:33:03+01:00, mleich@five.local.lan +12 -34
    Cleanup

  mysql-test/suite/funcs_1/t/myisam_bitdata.test@1.2, 2008-03-07 17:33:03+01:00, mleich@five.local.lan +7 -23
    Cleanup

  mysql-test/suite/funcs_1/t/myisam_cursors.test@1.2, 2008-03-07 17:33:03+01:00, mleich@five.local.lan +6 -21
    Cleanup

  mysql-test/suite/funcs_1/t/myisam_storedproc_02.test@1.2, 2008-03-07 16:27:45+01:00, mleich@five.local.lan +0 -0
    Change mode to -rw-rw-r--

  mysql-test/suite/funcs_1/t/myisam_storedproc_03.test@1.2, 2008-03-07 16:27:45+01:00, mleich@five.local.lan +0 -0
    Change mode to -rw-rw-r--

  mysql-test/suite/funcs_1/t/myisam_storedproc_06.test@1.2, 2008-03-07 16:27:45+01:00, mleich@five.local.lan +0 -0
    Change mode to -rw-rw-r--

  mysql-test/suite/funcs_1/t/myisam_storedproc_07.test@1.2, 2008-03-07 16:27:45+01:00, mleich@five.local.lan +0 -0
    Change mode to -rw-rw-r--

  mysql-test/suite/funcs_1/t/myisam_storedproc_08.test@1.2, 2008-03-07 16:27:45+01:00, mleich@five.local.lan +0 -0
    Change mode to -rw-rw-r--

  mysql-test/suite/funcs_1/t/myisam_storedproc_10.test@1.2, 2008-03-07 16:27:45+01:00, mleich@five.local.lan +0 -0
    Change mode to -rw-rw-r--

  mysql-test/suite/funcs_1/t/myisam_trig_0102.test@1.2, 2008-03-07 17:33:03+01:00, mleich@five.local.lan +4 -22
    Cleanup

  mysql-test/suite/funcs_1/t/myisam_trig_03.test@1.2, 2008-03-07 17:33:03+01:00, mleich@five.local.lan +4 -22
    Cleanup

  mysql-test/suite/funcs_1/t/myisam_trig_0407.test@1.2, 2008-03-07 17:33:03+01:00, mleich@five.local.lan +4 -22
    Cleanup

  mysql-test/suite/funcs_1/t/myisam_trig_08.test@1.2, 2008-03-07 17:33:03+01:00, mleich@five.local.lan +4 -22
    Cleanup

  mysql-test/suite/funcs_1/t/myisam_trig_09.test@1.2, 2008-03-07 17:33:03+01:00, mleich@five.local.lan +4 -22
    Cleanup

  mysql-test/suite/funcs_1/t/myisam_trig_1011ext.test@1.2, 2008-03-07 17:33:03+01:00, mleich@five.local.lan +4 -13
    Cleanup

  mysql-test/suite/funcs_1/t/myisam_views.test@1.2, 2008-03-07 17:33:03+01:00, mleich@five.local.lan +12 -33
    Cleanup

ChangeSet@1.2567.27.1, 2008-03-07 11:15:49+02:00, gkodinov@magare.gmz +4 -0
  Bug #34909: mysqldump returns a 0 status on error when using 
    --master-data
  
  No error code was returned by mysqldump if it detects that binary
  logging is not enabled on the server.
  Fixed by returning error code.

  client/mysqldump.c@1.276, 2008-03-07 11:15:49+02:00, gkodinov@magare.gmz +1 -0
    Bug #34909: add error code

  mysql-test/r/mysqldump-no-binlog.result@1.1, 2008-03-07 11:15:49+02:00, gkodinov@magare.gmz +1 -0
    Bug #34909: test case

  mysql-test/r/mysqldump-no-binlog.result@1.0, 2008-03-07 11:15:49+02:00, gkodinov@magare.gmz +0 -0

  mysql-test/t/mysqldump-no-binlog-master.opt@1.1, 2008-03-07 11:15:49+02:00, gkodinov@magare.gmz +1 -0
    Bug #34909: test case

  mysql-test/t/mysqldump-no-binlog-master.opt@1.0, 2008-03-07 11:15:49+02:00, gkodinov@magare.gmz +0 -0

  mysql-test/t/mysqldump-no-binlog.test@1.1, 2008-03-07 11:15:49+02:00, gkodinov@magare.gmz +6 -0
    Bug #34909: test case

  mysql-test/t/mysqldump-no-binlog.test@1.0, 2008-03-07 11:15:49+02:00, gkodinov@magare.gmz +0 -0

ChangeSet@1.2567.8.22, 2008-03-06 18:19:47+03:00, kaa@kaamos.(none) +3 -0
  Fix for bug #34512: CAST( AVG( double ) AS DECIMAL )
                      returns wrong results
  
  Casting AVG() to DECIMAL led to incorrect results when the arguments
  had a non-DECIMAL type, because in this case
  Item_sum_avg::val_decimal() performed the division by the number of
  arguments twice.
  
  Fixed by changing Item_sum_avg::val_decimal() to not rely on
  Item_sum_sum::val_decimal(), i.e. calculate sum and divide using
  DECIMAL arithmetics for DECIMAL arguments, and utilize val_real() with
  subsequent conversion to DECIMAL otherwise.

  mysql-test/r/func_group.result@1.66, 2008-03-06 18:19:47+03:00, kaa@kaamos.(none) +6 -0
    Added a test case for bug #34512.

  mysql-test/t/func_group.test@1.61, 2008-03-06 18:19:47+03:00, kaa@kaamos.(none) +10 -0
    Added a test case for bug #34512.

  sql/item_sum.cc@1.221, 2008-03-06 18:19:47+03:00, kaa@kaamos.(none) +9 -1
    Do not use Item_sum_sum::val_decimal() in Item_sum_avg::val_decimal()
    because the first one, depending on the arguments type, may return
    either the sum of the arguments, or the average calculated by the
    virtual val_real() method of Item_sum_avg. Instead, do our own
    calculation based on the arguments type.

ChangeSet@1.2572.1.23, 2008-03-06 14:49:21+02:00, aelkin@mysql1000.(none) +3 -0
  Bug#26622  MASTER_POS_WAIT does not work as documented
  
  MASTER_POS_WAIT return values are different than expected when the server is not a slave. 
  It returns -1 instead of NULL.
  
  Fixed with correcting  st_relay_log_info::wait_for_pos() to return the proper
  value in the case of rli info is not inited.

  mysql-test/r/rpl_master_pos_wait.result@1.9, 2008-03-06 14:49:18+02:00, aelkin@mysql1000.(none) +6 -0
    results changed

  mysql-test/t/rpl_master_pos_wait.test@1.7, 2008-03-06 14:49:19+02:00, aelkin@mysql1000.(none) +11 -0
    the new test to check that select master_pos_wait() to a server does 
    not have master info returns NULL as specified.

  sql/slave.cc@1.307, 2008-03-06 14:49:19+02:00, aelkin@mysql1000.(none) +1 -1
    changing the return value to correspond the specification.

ChangeSet@1.2572.8.3, 2008-03-06 09:16:53-03:00, davi@mysql.com +1 -0
  Bug#35103 mysql_client_test::test_bug29948 causes sporadic failures
  
  Disable test case for bug 29948, which is causing sporadically
  failures in other tests inside mysql_client_test.

  tests/mysql_client_test.c@1.250, 2008-03-06 09:16:52-03:00, davi@mysql.com +4 -1
    Disable test case.

ChangeSet@1.2567.25.3, 2008-03-06 09:58:49+04:00, bar@mysql.com +3 -0
  additional test fixes for bug 27580

  mysql-test/r/ctype_cp1250_ch.result@1.8, 2008-03-06 09:58:47+04:00, bar@mysql.com +34 -0
    additional test fixes for bug 27580

  mysql-test/r/ctype_cp932.result@1.12.1.1, 2008-03-06 09:58:47+04:00, bar@mysql.com +19 -0
    additional test fixes for bug 27580

  mysql-test/r/ctype_ucs.result@1.61.1.2, 2008-03-06 09:58:47+04:00, bar@mysql.com +17 -0
    additional test fixes for bug 27580

ChangeSet@1.2559.56.1, 2008-03-05 16:02:33+03:00, kaa@kaamos.(none) +2 -0
  Fix for bug #34889: mysql_client_test::test_mysql_insert_id test fails 
                      sporadically
  
  Under some circumstances, the mysql_insert_id() value after SELECT ...
  INSERT could return a wrong value. This could happen when the last
  SELECT ... INSERT did not involve an AUTO_INCREMENT column, but the
  value of mysql_insert_id() was changed by some previous statements.
  
  Fixed by checking the value of thd->insert_id_used in
  select_insert::send_eof() and returning 0 for mysql_insert_id() if it
  is not set.

  sql/sql_insert.cc@1.257, 2008-03-05 16:02:32+03:00, kaa@kaamos.(none) +2 -1
    Do not return thd->last_insert_id unconditionally in
    select_insert::send_eof(). First check if thd->insert_id_used is
    non-zero, and return 0 otherwise.

  tests/mysql_client_test.c@1.244.1.1, 2008-03-05 16:02:32+03:00, kaa@kaamos.(none) +16 -0
    Added a test case for bug #34889.

ChangeSet@1.2572.8.2, 2008-03-04 10:32:30-03:00, davi@mysql.com +1 -0
  Use the same name for mysql_client_test output file in all branches.

  mysql-test/t/mysql_client_test.test@1.22, 2008-03-04 10:32:28-03:00, davi@mysql.com +2 -2
    Rename mysql_client_test output file to mysql_client_test.out.log

ChangeSet@1.2572.8.1, 2008-03-04 10:17:49-03:00, davi@mysql.com +1 -0
  Bug#35009 Results of mysql_client_test are discarded upon failure
  
  It's impossible to determine which test inside mysql_client_test
  failed if the log file is overwritten by mysqltest when dumping
  the test case results. Redirect mysql_client_test output to a
  separate file.

  mysql-test/t/mysql_client_test.test@1.21, 2008-03-04 10:17:48-03:00, davi@mysql.com +2 -2
    Redirect mysql_client_test output to a separate log file so
    it doesn't get overwritten by mysqltest.

ChangeSet@1.2567.25.1, 2008-03-04 16:13:08+04:00, bar@mysql.com +5 -0
  Bug#23097 mysql can't insert korean on mysql prompt.
  Problem: libedit is a very pure-ASCII oriented library,
  and it is not aware of extended (0x80..0xFF) or even multi-byte
  characters. It considered such characters as non-printable
  and didn't allow to input them.
  Fix: make libedit think that all bytes >= 0x80 are printable.

  cmd-line-utils/libedit/el.h@1.6, 2008-03-04 16:13:06+04:00, bar@mysql.com +2 -0
    Defining macro, a locale's isprint() replacement.
    We'll consider all 8bit values as printable characters.

  cmd-line-utils/libedit/key.c@1.6, 2008-03-04 16:13:06+04:00, bar@mysql.com +2 -2
    Changing isprint() to el_isprint().

  cmd-line-utils/libedit/map.c@1.8, 2008-03-04 16:13:06+04:00, bar@mysql.com +1 -1
    Changing isprint() to el_isprint().

  cmd-line-utils/libedit/read.c@1.8, 2008-03-04 16:13:06+04:00, bar@mysql.com +1 -1
    Changing isprint() to el_isprint().

  cmd-line-utils/libedit/refresh.c@1.7, 2008-03-04 16:13:06+04:00, bar@mysql.com +3 -3
    Changing isprint() to el_isprint().

ChangeSet@1.2572.1.21, 2008-03-03 21:19:58+01:00, joerg@trift2. +1 -0
  Raise the version number after cloning 5.0.58

  configure.in@1.466.1.5, 2008-03-03 21:19:53+01:00, joerg@trift2. +2 -2
    Raise the version number after cloning 5.0.58

ChangeSet@1.2567.24.1, 2008-03-03 20:35:44+03:00, sergefp@mysql.com +3 -0
  BUG#34945: "ref_or_null queries that are null_rejecting and have a null value crash mysql"
  - Apply Eric Bergen's patch: in join_read_always_key(), move ha_index_init() call
    to before the late NULLs filtering code.
  - Backport function comments from 6.0.

  mysql-test/r/null_key.result@1.39, 2008-03-03 20:35:38+03:00, sergefp@mysql.com +18 -0
    BUG#34945: "ref_or_null queries that are null_rejecting and have a null value crash mysql"
    - Testcase

  mysql-test/t/null_key.test@1.16, 2008-03-03 20:35:38+03:00, sergefp@mysql.com +23 -0
    BUG#34945: "ref_or_null queries that are null_rejecting and have a null value crash mysql"
    - Testcase

  sql/sql_select.cc@1.558, 2008-03-03 20:35:38+03:00, sergefp@mysql.com +26 -3
    BUG#34945: "ref_or_null queries that are null_rejecting and have a null value crash mysql"
    - Apply Eric Bergen's patch: in join_read_always_key(), move ha_index_init() call
      to before the late NULLs filtering code.
    - Backport function comments from 6.0

ChangeSet@1.2559.55.1, 2008-03-03 17:34:06+03:00, kaa@kaamos.(none) +1 -0
  Fix for bug #31781: multi-table UPDATE with temp-pool enabled fails 
                      with errno 17
  
  my_create() did not perform any checks for the case when a file is
  successfully created by a call to open(), but the call to
  my_register_filename() later fails because the number of open files
  has exceeded the my_open_files limit. This can happen on platforms 
  which do not have getrlimit(), and hence we do not know the real limit
  for open files. In such a case an error was returned to a caller
  although the file has actually been created. Since callers assume
  my_create() to return an error only when it failed to create a file,
  they did not perform any cleanups, leaving an 'orphaned' file on the
  file system.
  
  Fixed by adding a check for the above case to my_create() and ensuring
  the newly created file is deleted before returning an error.
  
  Creating a deterministic test case in the test suite is impossible,
  because the exact steps required to reproduce the above situation
  depend on the platform and/or environment (OS per-user limits, queries
  executed by previous tests, startup parameters). The patch was
  manually tested on Windows using examples posted in the bug report.

  mysys/my_create.c@1.15, 2008-03-03 17:34:05+03:00, kaa@kaamos.(none) +17 -3
    Ensure that, if the call to my_register_filename() in my_create()
    failed, but the previous open() called succeeded, the newly created
    file is deleted before returning an error. 

ChangeSet@1.2567.8.20, 2008-03-03 15:02:34+04:00, gluh@mysql.com +2 -0
  test case fix

  mysql-test/r/symlink.result@1.41, 2008-03-03 15:02:32+04:00, gluh@mysql.com +4 -4
    test case fix

  mysql-test/t/symlink.test@1.32, 2008-03-03 15:02:32+04:00, gluh@mysql.com +4 -4
    test case fix

ChangeSet@1.2572.6.2, 2008-03-02 21:20:36+03:00, skozlov@mysql.com +2 -0
  Bug#22438

  mysql-test/r/mysqldump.result@1.133, 2008-03-02 21:20:30+03:00, skozlov@mysql.com +1 -1
    updated result

  mysql-test/t/mysqldump.test@1.125, 2008-03-02 21:20:30+03:00, skozlov@mysql.com +1 -0
    hide master_log_pos number

ChangeSet@1.1616.3129.1, 2008-03-01 18:25:41+01:00, kent@mysql.com +1 -0
  mysql.spec.sh:
    - Aligned copyright headers and text with 5.0
    - Don't strip binaries on SuSE 9
    - Formatting alignment with spec file in 5.0
    - Run full test on "normal" binary, and less on "Max"
    - Let test runs on "Max" identify the runs with "max" and "max+ps"

  support-files/mysql.spec.sh@1.83.1.53, 2008-03-01 18:07:19+01:00, kent@mysql.com +60 -32
    - Aligned copyright headers and text with 5.0
    - Don't strip binaries on SuSE 9
    - Formatting alignment with spec file in 5.0
    - Run full test on "normal" binary, and less on "Max"
    - Let test runs on "Max" identify the runs with "max" and "max+ps"

ChangeSet@1.2567.8.18, 2008-02-29 17:50:01+04:00, gluh@mysql.com +1 -0
  wrong merge fix

  sql/sql_parse.cc@1.644.1.2, 2008-02-29 17:49:59+04:00, gluh@mysql.com +0 -2
    wrong merge fix

ChangeSet@1.1616.3128.3, 2008-02-29 16:56:41+04:00, gluh@mysql.com +2 -0
  test fix

  mysql-test/r/symlink.result@1.11.1.19, 2008-02-29 16:56:40+04:00, gluh@mysql.com +4 -4
    result fix

  mysql-test/t/symlink.test@1.11.1.12, 2008-02-29 16:56:40+04:00, gluh@mysql.com +3 -0
    test fix

ChangeSet@1.2567.23.1, 2008-02-29 15:11:11+04:00, gshchepa@host.loc +1 -0
  Fixed bug #34830: mixed table and field names in Item_ref
                    and Item_direct_ref constructor calls.
  
  Order of ref->field_name and ref->table_name arguments
  is of Item_ref and Item_direct_ref in the fix_inner_refs
  function is inverted.

  sql/sql_select.cc@1.557, 2008-02-29 15:02:47+04:00, gshchepa@host.loc +4 -4
    Fixed bug #34830: mixed table and field names in Item_ref
                      and Item_direct_ref constructor calls.
    
    Order of ref->field_name and ref->table_name arguments
    is of Item_ref and Item_direct_ref in the fix_inner_refs
    function is inverted. See definitions:
    
      Item_ref(Name_resolution_context *context_arg, Item **item,
               const char *table_name_arg, const char *field_name_arg,
               bool alias_name_used_arg= FALSE)
      and
    
      Item_direct_ref(Name_resolution_context *context_arg, Item **item,
                      const char *table_name_arg,
                      const char *field_name_arg,
                      bool alias_name_used_arg= FALSE)

ChangeSet@1.2567.8.16, 2008-02-29 15:04:00+04:00, gluh@mysql.com +3 -0
  after merge fix

  mysql-test/r/symlink.result@1.39, 2008-02-29 15:03:58+04:00, gluh@mysql.com +23 -24
    after merge fix

  mysql-test/t/symlink.test@1.30, 2008-02-29 15:03:58+04:00, gluh@mysql.com +8 -30
    after merge fix

  sql/mysqld.cc@1.637, 2008-02-29 15:03:58+04:00, gluh@mysql.com +2 -8
    after merge fix

ChangeSet@1.1616.3128.2, 2008-02-29 13:55:00+04:00, gluh@mysql.com +5 -0
  Bug#32167 another privilege bypass with DATA/INDEX DIRECORY(ver 4.1,5.0)
  added new function test_if_data_home_dir() which checks that
  path does not contain mysql data home directory.
  Using of mysql data home directory in
  DATA DIRECTORY & INDEX DIRECTORY is disallowed.

  mysql-test/r/symlink.result@1.11.1.18, 2008-02-29 13:54:59+04:00, gluh@mysql.com +21 -17
    test result

  mysql-test/t/symlink.test@1.11.1.11, 2008-02-29 13:54:59+04:00, gluh@mysql.com +29 -19
    test case

  sql/mysql_priv.h@1.186.91.65, 2008-02-29 13:54:59+04:00, gluh@mysql.com +1 -0
    new variable mysql_unpacked_real_data_home

  sql/mysqld.cc@1.356.117.5, 2008-02-29 13:54:59+04:00, gluh@mysql.com +4 -0
    new variable mysql_unpacked_real_data_home

  sql/sql_parse.cc@1.271.134.4, 2008-02-29 13:54:59+04:00, gluh@mysql.com +60 -1
    added new function test_if_data_home_dir() which checks that
    path does not contain mysql data home directory.
    Using of mysql data home directory in
    DATA DIRECTORY & INDEX DIRECTORY is disallowed.

ChangeSet@1.2579, 2008-02-28 23:53:01-05:00, iggy@alf.(none) +1 -0
  Bug #24992 Enabling Shared Memory support on Windows x64 causes client to fail
  - Mistaken macro defintions cause mysys to read packets in the wrong order.

  include/my_global.h@1.149, 2008-02-28 23:52:59-05:00, iggy@alf.(none) +2 -2
    Bug #24992 Enabling Shared Memory support on Windows x64 causes client to fail
    - Use low byte order optimizations for Windows.

ChangeSet@1.2559.54.1, 2008-02-28 22:53:31+04:00, gshchepa@host.loc +3 -0
  Fixed bug #34620: item_row.cc:50: Item_row::illegal_method_call(const char*):
                    Assertion `0' failed
  
  If ROW item is a part of an expression that also has
  aggregate function calls (COUNT/SUM/AVG...), a
  "splitting" with an Item::split_sum_func2 function
  is applied to that ROW item.
  Current implementation of Item::split_sum_func2
  replaces this Item_row with a newly created
  Item_aggregate_ref reference to it.
  Then the row cache tries to work with the
  Item_aggregate_ref object as with the Item_row object:
  row cache calls row-emulation methods such as cols and
  element_index. Item_aggregate_ref (like it's parent
  Item_ref) inherits dummy implementations of those
  methods from the hierarchy root Item, and call to
  them leads to failed assertions and wrong data
  output.
  
  Row-emulation virtual functions (cols, element_index, addr,
  check_cols, null_inside and bring_value) of Item_ref have
  been overloaded to forward calls to an underlying item
  reference.
  
  

  mysql-test/r/row.result@1.29, 2008-02-28 22:53:19+04:00, gshchepa@host.loc +9 -0
    Added test case for bug #34620.

  mysql-test/t/row.test@1.26, 2008-02-28 22:53:20+04:00, gshchepa@host.loc +13 -0
    Added test case for bug #34620.

  sql/item.h@1.250, 2008-02-28 22:53:21+04:00, gshchepa@host.loc +29 -0
    Fixed bug #34620.
    Row-emulation virtual functions (cols, element_index, addr,
    check_cols, null_inside and bring_value) of Item_ref have
    been overloaded to forward calls to an underlying item
    reference.

ChangeSet@1.2559.53.2, 2008-02-28 14:23:22+01:00, tnurnberg@mysql.com +7 -0
  Bug#34749: Server crash when using NAME_CONST() with an aggregate function
  
  NAME_CONST('whatever', -1) * MAX(whatever) bombed since -1 was
  not seen as constant, but as FUNCTION_UNARY_MINUS(constant)
  while we are at the same time pretending it was a basic const
  item. This confused the aggregate handlers in exciting ways.
  We now make NAME_CONST() behave more consistently.

  mysql-test/r/func_misc.result@1.29.1.5, 2008-02-28 14:23:21+01:00, tnurnberg@mysql.com +19 -0
    show that a combination of NAME_CONST('x', -y) and an aggregate
    no longer crashes the server.

  mysql-test/t/func_misc.test@1.23.1.5, 2008-02-28 14:23:21+01:00, tnurnberg@mysql.com +18 -0
    show that a combination of NAME_CONST('x', -y) and an aggregate
    no longer crashes the server.

  sql/ha_ndbcluster_cond.cc@1.7, 2008-02-28 14:23:21+01:00, tnurnberg@mysql.com +6 -3
    tell cluster about "new" function type NEG_FUNC.
    (this was previous identified as UNKNOWN_FUNC,
    so we just handle it the same way, that's all.)

  sql/ha_ndbcluster_cond.h@1.5, 2008-02-28 14:23:21+01:00, tnurnberg@mysql.com +1 -0
    tell cluster about "new" function type NEG_FUNC.
    (this was previous identified as UNKNOWN_FUNC,
    so we just handle it the same way, that's all.)

  sql/item.cc@1.297.3.1, 2008-02-28 14:23:21+01:00, tnurnberg@mysql.com +26 -1
    make NAME_CONST() transparent in that type() of
    -constant is that of constant, not that of unary
    minus (id est, FUNC_ITEM).

  sql/item.h@1.248.2.1, 2008-02-28 14:23:21+01:00, tnurnberg@mysql.com +1 -8
    Move constructor to item.cc

  sql/item_func.h@1.180, 2008-02-28 14:23:21+01:00, tnurnberg@mysql.com +3 -2
    Revert Bug#30832; we can apply the magic more narrowly
    (just for NAME_CONST() rather than all Item_func_neg).
    
    Introduce new function type "NEG_FUNC."

ChangeSet@1.2567.22.1, 2008-02-28 13:31:19+02:00, gkodinov@magare.gmz +3 -0
  Bug #34747: crash in debug assertion check after derived table
  
  Was a double-free of the Unique member of Item_func_group_concat.
  This was not causing a crash because the Unique is a descendent of
  Sql_alloc.
  Fixed to free the Unique only if it was allocated for the instance 
  of Item_func_group_concat it was referenced from

  mysql-test/r/func_gconcat.result@1.75, 2008-02-28 13:31:18+02:00, gkodinov@magare.gmz +15 -0
    Bug #34747: test case

  mysql-test/t/func_gconcat.test@1.62, 2008-02-28 13:31:18+02:00, gkodinov@magare.gmz +17 -0
    Bug #34747: test case

  sql/item_sum.cc@1.220, 2008-02-28 13:31:18+02:00, gkodinov@magare.gmz +1 -1
    Bug #34747: free the Unique only if it was allocated
    for this instance of Item_func_group_concat

ChangeSet@1.2572.7.1, 2008-02-27 16:17:05-05:00, iggy@alf.(none) +3 -0
  Bug #23839 Multiple declarations of macros
  - Remove duplicate macro defintions.

  CMakeLists.txt@1.24, 2008-02-27 16:17:00-05:00, iggy@alf.(none) +8 -0
    Bug #23839 Multiple declarations of macros
    - Make sure _WIN64 is defined for proper Intellisense functionality.

  include/config-win.h@1.88, 2008-02-27 16:17:01-05:00, iggy@alf.(none) +0 -54
    Bug #23839 Multiple declarations of macros
    - Remove extra definitions.  Use the my_global.h defines instead.

  include/my_global.h@1.148, 2008-02-27 16:17:03-05:00, iggy@alf.(none) +5 -6
    Bug #23839 Multiple declarations of macros
    - Slight change to maintain current definitions for Windows.

ChangeSet@1.2559.52.2, 2008-02-27 18:12:08+03:00, kaa@kaamos.(none) +1 -0
  Fixed test suite failures with --ps-protocol introduced in PB by
  the patch for bug #33834.

  mysql-test/t/func_time.test@1.75, 2008-02-27 18:12:07+03:00, kaa@kaamos.(none) +7 -1
    Fixed test suite failures with --ps-protocol introduced in PB by
    the patch for bug #33834.

ChangeSet@1.2559.53.1, 2008-02-27 12:42:43+04:00, holyfoot@mysql.com +6 -0
  Bug #25097 mysql_server_init fails silently if no errmsg.sys is present.
  
  There was no way to return an error from the client library
  if no MYSQL connections was established.
  So here i added variables to store that king of errors and
  made functions like mysql_error(NULL) to return these.

  client/mysql.cc@1.246.1.1, 2008-02-27 12:42:41+04:00, holyfoot@mysql.com +1 -0
    Bug #25097 mysql_server_init fails silently if no errmsg.sys is present.
    
    Show the error message on std_error

  include/sql_common.h@1.20, 2008-02-27 12:42:41+04:00, holyfoot@mysql.com +1 -0
    Bug #25097 mysql_server_init fails silently if no errmsg.sys is present.
    
    cant_connect_sqlstate constant declared

  libmysql/libmysql.c@1.249.1.1, 2008-02-27 12:42:41+04:00, holyfoot@mysql.com +1 -1
    Bug #25097 mysql_server_init fails silently if no errmsg.sys is present.
    
    mysql_sqlstate(NULL) returns 'unknown_sqlstate'

  libmysqld/lib_sql.cc@1.130.1.1, 2008-02-27 12:42:41+04:00, holyfoot@mysql.com +10 -0
    Bug #25097 mysql_server_init fails silently if no errmsg.sys is present.
    
    EMBEDDED_SERVER version of the vprint_msg_to_log() implemented

  sql-common/client.c@1.120, 2008-02-27 12:42:41+04:00, holyfoot@mysql.com +21 -6
    Bug #25097 mysql_server_init fails silently if no errmsg.sys is present.
    
    mysql_server_last_errno and mysql_server_last_error introduced
    to store errors not related to particular connections.
    
    mysql_error(NULL) and mysql_errno(NULL) now returns these
    mysql_server_last_error and errno respectively

  sql/log.cc@1.222.1.1, 2008-02-27 12:42:41+04:00, holyfoot@mysql.com +1 -6
    Bug #25097 mysql_server_init fails silently if no errmsg.sys is present.
    
    EMBEDDED_LIBRARY implementation of the vprint_msg_to_log() moved
    to lib_sql.cc

ChangeSet@1.2577, 2008-02-26 18:36:06+01:00, kent@mysql.com +5 -0
  Makefile.am, Info.plist.sh:
    Use MYSQL_NUMERIC_VERSION, only three numbers separated with dot
  misc.m4, character_sets.m4, openssl.m4:
    Removed unneded semicolon

  config/ac-macros/character_sets.m4@1.10, 2008-02-26 18:32:08+01:00, kent@mysql.com +3 -3
    Removed unneded semicolon

  config/ac-macros/misc.m4@1.17, 2008-02-26 18:32:08+01:00, kent@mysql.com +1 -1
    Removed unneded semicolon

  config/ac-macros/openssl.m4@1.9, 2008-02-26 18:32:08+01:00, kent@mysql.com +2 -2
    Removed unneded semicolon

  support-files/MacOSX/Info.plist.sh@1.4, 2008-02-26 18:35:40+01:00, kent@mysql.com +1 -1
    Use MYSQL_NUMERIC_VERSION, only three numbers separated with dot

  support-files/MacOSX/Makefile.am@1.12, 2008-02-26 18:35:40+01:00, kent@mysql.com +1 -1
    Use MYSQL_NUMERIC_VERSION, only three numbers separated with dot

ChangeSet@1.1616.3091.27, 2008-02-26 18:18:03+01:00, kent@mysql.com +2 -0
  configure.in:
    Corrected calculation of version id, incorrect last two digits if < 10
    Keep "sp1" or "a" in MYSQL_NO_DASH_VERSION, to set correct version in
    RPM spec file
    Added MYSQL_NUMERIC_VERSION that is like MYSQL_NO_DASH_VERSION before
    Added clear doc how the different version variables differ
  SocketServer.cpp:
    Corrected typo in debug error message

  configure.in@1.201.64.32, 2008-02-26 18:16:05+01:00, kent@mysql.com +13 -3
    Corrected calculation of version id, incorrect last two digits if < 10
    Keep "sp1" or "a" in MYSQL_NO_DASH_VERSION, to set correct version in
    RPM spec file
    Added MYSQL_NUMERIC_VERSION that is like MYSQL_NO_DASH_VERSION before
    Added clear doc how the different version variables differ

  ndb/src/common/util/SocketServer.cpp@1.10.1.4, 2008-02-26 18:15:28+01:00, kent@mysql.com +1 -1
    Corrected typo in debug error message

ChangeSet@1.2559.52.1, 2008-02-25 13:25:57+03:00, kaa@kaamos.(none) +3 -0
  Fix for bug #33834: FRAC_SECOND: Applicability not clear in 
                      documentation
  
  While the manual mentions FRAC_SECOND only for the TIMESTAMPADD()
  function, it was also possible to use FRAC_SECOND with DATE_ADD(),
  DATE_SUB() and +/- INTERVAL.
  
  Fixed the parser to match the manual, i.e. using FRAC_SECOND for 
  anything other than TIMESTAMPADD()/TIMESTAMPDIFF() now produces a 
  syntax error.
  
  Additionally, the patch allows MICROSECOND to be used in TIMESTAMPADD/
  TIMESTAMPDIFF and marks FRAC_SECOND as deprecated.

  mysql-test/r/func_time.result@1.87, 2008-02-25 13:25:55+03:00, kaa@kaamos.(none) +23 -0
    Added a test case for bug #33834.

  mysql-test/t/func_time.test@1.74, 2008-02-25 13:25:55+03:00, kaa@kaamos.(none) +19 -0
    Added a test case for bug #33834.

  sql/sql_yacc.yy@1.544.1.2, 2008-02-25 13:25:55+03:00, kaa@kaamos.(none) +27 -6
    Reject FRAC_SECOND for anything other than TIMESTAMPADD() or
    TIMESTAMPDIFF().
    Allow MICROSECOND to be used with TIMESTAMPADD()/TIMESTAMPDIFF().
    Warn about FRAC_SECOND being a deprecated unit.

ChangeSet@1.2559.51.2, 2008-02-25 07:50:55+01:00, tnurnberg@mysql.com +1 -0
  Bug#29645: Link failure when using the embedded server
  
  mysql_config --cflags gave a flag that forced the HP/UX
  C++ compiler into C-mode; as a result, C++ sources could
  not be compiled correctly.
  
  We now filter out the offending flag (like we do for Sun)
  so that --cflags will work for both C and C++.

  scripts/mysql_config.sh@1.29.1.1, 2008-02-25 07:50:54+01:00, tnurnberg@mysql.com +3 -1
    Add -AC99 (for HP/UX) to the list of flags we need to remove
    from "mysql_config --cflags" so they work for C and C++ both. 

ChangeSet@1.2567.21.1, 2008-02-22 19:07:07+04:00, svoj@mysql.com +6 -0
  BUG#13861 - START SLAVE UNTIL may stop 1 evnt too late if
              log-slave-updates and circul repl
  
  Slave SQL thread may execute one extra event when there are events
  skipped by slave I/O thread (e.g. originated by the same server).
  Whereas it was requested not to do so by the UNTIL condition.
  
  This happens because we compare with the end position of previously
  executed event. This is fine when there are no skipped by slave I/O
  thread events, as end position of previous event equals to start
  position of to be executed event. Otherwise this position equals to
  start position of skipped event.
  
  This is fixed by:
  - reading the event to be executed before checking if the until condition
    is satisfied.
  - comparing the start position of the event to be executed. Since we do
    not have the start position available, we compute it by subtracting
    event length from end position (which is available).
  - if there are no events on the event queue at the slave sql starting
    time, that meet until condition, we stop immediately, as in this
    case we do not want to wait for next event.

  mysql-test/r/rpl_dual_pos_advance.result@1.3, 2008-02-22 19:07:06+04:00, svoj@mysql.com +42 -1
    A test case for BUG#13861.

  mysql-test/t/rpl_dual_pos_advance-slave.opt@1.1, 2008-02-22 19:07:06+04:00, svoj@mysql.com +1 -0
    New BitKeeper file ``mysql-test/t/rpl_dual_pos_advance-slave.opt''

  mysql-test/t/rpl_dual_pos_advance-slave.opt@1.0, 2008-02-22 19:07:06+04:00, svoj@mysql.com +0 -0

  mysql-test/t/rpl_dual_pos_advance.test@1.4, 2008-02-22 19:07:06+04:00, svoj@mysql.com +38 -18
    A test case for BUG#13861.

  sql/log_event.cc@1.246, 2008-02-22 19:07:06+04:00, svoj@mysql.com +2 -1
    Store length of event. This is needed for further calculation of
    the beginning of event.

  sql/slave.cc@1.305.1.1, 2008-02-22 19:07:06+04:00, svoj@mysql.com +44 -24
    Slave SQL thread may execute one extra event when there are events
    skipped by slave I/O thread (e.g. originated by the same server).
    Whereas it was requested not to do so by the UNTIL condition.
    
    This happens because we compare with the end position of previously
    executed event. This is fine when there are no skipped by slave I/O
    thread events, as end position of previous event equals to start
    position of to be executed event. Otherwise this position equals to
    start position of skipped event.
    
    This is fixed by:
    - reading the event to be executed before checking if the until condition
      is satisfied.
    - comparing the start position of the event to be executed. Since we do
      not have the start position available, we compute it by subtracting
      event length from end position (which is available).
    - if there are no events on the event queue at the slave sql starting
      time, that meet until condition, we stop immediately, as in this
      case we do not want to wait for next event.

  sql/slave.h@1.102, 2008-02-22 19:07:06+04:00, svoj@mysql.com +1 -1
    Added master_log_pos parametr to is_until_satisfied().

ChangeSet@1.2559.51.1, 2008-02-22 11:34:18+03:00, kaa@kaamos.(none) +3 -0
  Fix for bug #33049: Assert while running test-as3ap test(mysql-bench 
                      suite)
  
  Under some circumstances a combination of aggregate functions and
  GROUP BY in a SELECT query over a VIEW could lead to incorrect
  calculation of the result type of the aggregate function. This in
  turn could result in incorrect results, or assertion failures on debug
  builds.
  
  Fixed by changing the logic in Item_sum_hybrid::fix_fields() so that
  the argument's item is dereferenced before calling its type() method.

  mysql-test/r/view.result@1.209.1.3, 2008-02-22 11:34:17+03:00, kaa@kaamos.(none) +8 -0
    Added a test case for bug #33049.

  mysql-test/t/view.test@1.193, 2008-02-22 11:34:17+03:00, kaa@kaamos.(none) +13 -0
    Added a test case for bug #33049.

  sql/item_sum.cc@1.219, 2008-02-22 11:34:17+03:00, kaa@kaamos.(none) +1 -0
    When calculating the result type of an aggregate function, dereference
    the argument's item before calling its type() method.

ChangeSet@1.2567.20.1, 2008-02-22 12:30:17+04:00, gluh@mysql.com +3 -0
  Bug#23588 SHOW COLUMNS on a temporary table causes locking issues
  skip lock_type update for temporary tables

  mysql-test/r/tablelock.result@1.6, 2008-02-22 12:30:16+04:00, gluh@mysql.com +9 -0
    test result

  mysql-test/t/tablelock.test@1.7, 2008-02-22 12:30:16+04:00, gluh@mysql.com +13 -0
    test case

  sql/sql_base.cc@1.399, 2008-02-22 12:30:16+04:00, gluh@mysql.com +6 -2
    skip lock_type update for temporary tables

ChangeSet@1.2567.17.1, 2008-02-20 17:41:39+03:00, evgen@moonbone.local +2 -0
  Bug#33266: Incorrect test case for the bug#31048 failing on some platforms.
  
  The test case for the bug#31048 checks that there is no crash on stack
  overrun. But due to different stack sizes on different platforms it failed
  on some of them.
  
  The new test case check that a query with at least 4 level subquery nesting
  works without the stack overrun nesting and other levels of nesting doesn't
  cause a crash.

  mysql-test/r/subselect.result@1.206, 2008-02-20 17:40:52+03:00, evgen@moonbone.local +31 -97
    Corrected test case for the bug#31048.

  mysql-test/t/subselect.test@1.164, 2008-02-20 17:40:40+03:00, evgen@moonbone.local +38 -86
    Corrected test case for the bug#31048.

ChangeSet@1.2567.8.7, 2008-02-19 17:27:18+02:00, gkodinov@magare.gmz +4 -0
  Bug #30604: different flagging of time_zone_used in normal 
    and ps-protocol
  Finding a routine should be a transparent operation as 
  far as the binary log is concerned.
  But it was influencing the binary log because of the TIMESTAMP
  column in the proc table.
  
  Fixed by preserving and restoring the time_zone usage flag when
  searching for a stored routine in the proc table.

  mysql-test/r/binlog_innodb.result@1.2, 2008-02-19 17:27:17+02:00, gkodinov@magare.gmz +16 -0
    Bug #30604: test case

  mysql-test/r/ctype_cp932_binlog.result@1.9, 2008-02-19 17:27:17+02:00, gkodinov@magare.gmz +3 -3
    Bug #30604: updated test results (a procedure call before that)

  mysql-test/t/binlog_innodb.test@1.2, 2008-02-19 17:27:17+02:00, gkodinov@magare.gmz +25 -0
    Bug #30604: test case

  sql/sp.cc@1.138, 2008-02-19 17:27:17+02:00, gkodinov@magare.gmz +6 -0
    Bug #30604: finding a routine should be a transparent operation as 
    far as the binary log is concerned.
    Fixed by preserving and restoring the time_zone usage flag.

ChangeSet@1.2567.1.8, 2008-02-19 18:16:17+04:00, svoj@mysql.com +3 -0
  BUG#34289 - Incorrect NAME_CONST substitution in stored procedures
              breaks replication
  
  NAME_CONST() didn't replicate constant character set and collation
  correctly.
  
  With this fix NAME_CONST() inherits collation from the value argument.

  mysql-test/r/func_misc.result@1.32, 2008-02-19 18:16:15+04:00, svoj@mysql.com +3 -0
    A test case for BUG#34289.

  mysql-test/t/func_misc.test@1.26, 2008-02-19 18:16:15+04:00, svoj@mysql.com +6 -0
    A test case for BUG#34289.

  sql/item.cc@1.297.1.2, 2008-02-19 18:16:15+04:00, svoj@mysql.com +1 -0
    Inherit collation from value argument.

ChangeSet@1.2559.50.1, 2008-02-17 15:48:17+04:00, holyfoot@mysql.com +3 -0
  Bug #32942 now() - interval '7200' second NOT pre-calculated, causing "full table scan"
  
  Problem is not about intervals and doesn't actually cause 'full table scan'.
  We have an optimization for DISTINCT when we have
  'DISTINCT field_from_first_join_table' we don't need to read all the
  rows from the JOIN-ed table if we found one conforming row.
  It stopped working in 5.0 as we return NESTED_LOOP_OK if we came upon
  that case in the evaluate_join_record() and that doesn't break the
  recordreading loop in sub_select().
  
  Fixed by returning NESTED_LOOP_NO_MORE_ROWS in this case.

  mysql-test/r/select.result@1.161.1.1, 2008-02-17 15:48:15+04:00, holyfoot@mysql.com +21 -0
    Bug #32942 now() - interval '7200' second is NOT pre-calculated, causing "full table scan".
    
    test result

  mysql-test/t/select.test@1.137.1.1, 2008-02-17 15:48:15+04:00, holyfoot@mysql.com +18 -0
    Bug #32942 now() - interval '7200' second is NOT pre-calculated, causing "full table scan"
    
    test case

  sql/sql_select.cc@1.550.2.1, 2008-02-17 15:48:15+04:00, holyfoot@mysql.com +1 -1
    Bug #32942 now() - interval '7200' second NOT pre-calculated, causing "full table scan"
    
    return NESTED_LOOP_NO_MORE_ROWS when we don't need to read rows from
    this table anymore

ChangeSet@1.2541.82.2, 2008-02-15 15:47:32+02:00, gkodinov@magare.gmz +4 -0
  Bug #31887: DML Select statement not returning same results 
  when executed in version 5
  
  Zero fill is a field attribute only. So we can't always 
  propagate  constants for zerofill fields : the values and 
  expression results don't have that flag.
  
  Fixed by converting the const value to a string and 
  using that in const propagation when the context allows it. 
  Disable const propagation for fields with ZEROFILL flag in
  all the other cases.

  mysql-test/r/compare.result@1.13, 2008-02-15 15:47:31+02:00, gkodinov@magare.gmz +38 -0
    Bug #31887: test case

  mysql-test/t/compare.test@1.11, 2008-02-15 15:47:31+02:00, gkodinov@magare.gmz +31 -0
    Bug #31887: test case

  sql/item.cc@1.292.1.1, 2008-02-15 15:47:31+02:00, gkodinov@magare.gmz +31 -0
    Bug #31887: If the context allows conversion
    of an int constant to a zero-filled string constant
    put the string constant instead of the int constant
    when doing const propagation

  sql/mysql_priv.h@1.464.2.1, 2008-02-15 15:47:32+02:00, gkodinov@magare.gmz +1 -0
    Bug #31887: a macro to get all the Field_num
    descendant fields.

ChangeSet@1.2567.13.1, 2008-02-15 16:03:54+04:00, ramil@mysql.com +1 -0
  Fix for bug #33304: Test 'func_group' hangs on Mac OS X 10.4 PowerPC 64-bit
  
  Problem: SLEEP(0) never returns on 64-bit Mac OS X due to a bug in 
  pthread_cond_timedwait().
  
  Fix: when given a very short timeout just return immediately.

  sql/item_func.cc@1.364.1.1, 2008-02-15 16:03:53+04:00, ramil@mysql.com +12 -0
    Fix for bug #33304: Test 'func_group' hangs on Mac OS X 10.4 PowerPC 64-bit
    
    - if given a very short timeout (< 10 mcs) just return from SLEEP().

ChangeSet@1.2567.12.1, 2008-02-14 16:28:32+02:00, aelkin@mysql1000.dsl.inet.fi +2 -0
  bug#33329 extraneous ROLLBACK in binlog on connection does not use trans tables
  
  changes for an assert and an updated results file.

  mysql-test/r/mix_innodb_myisam_binlog.result@1.40, 2008-02-14 16:28:30+02:00, aelkin@mysql1000.dsl.inet.fi +1 -1
    results file changed as there is no ROLLBACK query in binlog as it must be.

  sql/sql_update.cc@1.228, 2008-02-14 16:28:31+02:00, aelkin@mysql1000.dsl.inet.fi +1 -1
    refining assert as the initial value of transactional_tables has been
    changed to zero.

ChangeSet@1.2567.10.2, 2008-02-14 16:27:01+04:00, svoj@mysql.com +3 -0
  BUG#33946 - Join on Federated tables with Unique index gives error 1430
              from storage engine
  
  Federated may crash a server, return wrong result set, return
  "ERROR 1030 (HY000): Got error 1430 from storage engine" message
  when local (engine=federated) table has a key against nullable
  column.
  
  The problem was wrong implementation of function that creates
  WHERE clause for remote query from key.

  mysql-test/r/federated.result@1.48, 2008-02-14 16:26:58+04:00, svoj@mysql.com +24 -0
    A test case for BUG#33946.

  mysql-test/t/federated.test@1.42, 2008-02-14 16:26:58+04:00, svoj@mysql.com +21 -0
    A test case for BUG#33946.

  sql/ha_federated.cc@1.87, 2008-02-14 16:26:58+04:00, svoj@mysql.com +19 -3
    Fixed that federated adds " IS NULL " condition to a remote query,
    whereas "IS NOT NULL" requested by original query.
    
    Fixed that federated didn't check for end of key buffer, didn't
    setup key buffer pointer and remaining lenght of key buffer,
    didn't add " AND " between conditions in case original query
    has IS [NOT] NULL condition against nullable column.
    
    Fixed that federated wrongly shifts key buffer pointer by extra
    one byte when key part may be null (was: store_length + 1,
    now: store_length).

ChangeSet@1.2559.42.4, 2008-02-13 19:34:12+04:00, gshchepa@host.loc +3 -0
  Fixed bug#31194: Privilege ordering does not order properly
                   for wildcard values.
  The server ignored escape character before wildcards during
  the calculation of priority values for sorting of a privilege
  list. (Actually the server counted an escape character as an
  ordinary wildcard like % or _). I.e. the table name template
  with a wildcard character like 'tbl_1' had higher priority in
  a privilege list than concrete table name without wildcards
  like 'tbl\_1', and some privileges of 'tbl\_1' was hidden
  by privileges for 'tbl_1'.
  
  The get_sort function has been modified to ignore escaped
  wildcards as usual.
  

  mysql-test/r/grant3.result@1.5, 2008-02-13 19:33:19+04:00, gshchepa@host.loc +17 -0
    Added test case for bug#31194.

  mysql-test/t/grant3.test@1.6, 2008-02-13 19:33:20+04:00, gshchepa@host.loc +26 -0
    Added test case for bug#31194.

  sql/sql_acl.cc@1.224.3.1, 2008-02-13 19:33:20+04:00, gshchepa@host.loc +3 -1
    Fixed bug#31194.
    The server used the wild_prefix escape character (usually \-character)
    like % and _ wildcards in the get_sort function for sorting weights
    calculation.
    
    The get_sort function has been modified to ignore escaped wildcards
    and alone escapes like in the wild_case_compare function.

ChangeSet@1.2559.42.3, 2008-02-13 19:32:19+04:00, gshchepa@host.loc +3 -0
  Fixed bug#33764: Wrong result with IN(), CONCAT() and implicit
                   type conversion.
  
  Instead of copying of whole character string from a temporary
  buffer, the server copied a short-living pointer to that string
  into a long-living structure. That has been fixed.

  mysql-test/r/select.result@1.162, 2008-02-13 19:31:33+04:00, gshchepa@host.loc +6 -0
    Added test case for bug#33764.

  mysql-test/t/select.test@1.138, 2008-02-13 19:31:34+04:00, gshchepa@host.loc +11 -0
    Added test case for bug#33764.

  sql/item_cmpfunc.cc@1.271.1.1, 2008-02-13 19:31:35+04:00, gshchepa@host.loc +4 -1
    Fixed bug#33764.
    Copying of a pointer has been replaced with an optional copying of
    a whole array to a newly allocated memory space in case of a
    functional source item.

ChangeSet@1.2567.11.1, 2008-02-13 14:09:41+02:00, aelkin@mysql1000.dsl.inet.fi +4 -0
  Bug #33931 assertion at write_ignored_events_info_to_relay_log if init_slave_thread() fails
  and
  bug#33932  assertion at handle_slave_sql if init_slave_thread() fails
  
  the asserts were caused by 
    bug33931: having thd deleted at time of executing err: code plus
              a missed initialization;
    bug33932: initialization of slave_is_running member was missed;
  
  fixed with relocating mi members initialization and removing delete thd
  It is safe to do as deletion happens later explicitly in the caller of
  init_slave_thread().
  
  Todo: at merging the test is better to be moved into suite/bugs for 5.x (when x>0).

  mysql-test/r/rpl_bug33931.result@1.1, 2008-02-13 14:09:40+02:00, aelkin@mysql1000.dsl.inet.fi +38 -0
    the new result file

  mysql-test/r/rpl_bug33931.result@1.0, 2008-02-13 14:09:40+02:00, aelkin@mysql1000.dsl.inet.fi +0 -0

  mysql-test/t/rpl_bug33931-slave.opt@1.1, 2008-02-13 14:09:40+02:00, aelkin@mysql1000.dsl.inet.fi +1 -0
    option to spark the simulation code

  mysql-test/t/rpl_bug33931-slave.opt@1.0, 2008-02-13 14:09:40+02:00, aelkin@mysql1000.dsl.inet.fi +0 -0

  mysql-test/t/rpl_bug33931.test@1.1, 2008-02-13 14:09:40+02:00, aelkin@mysql1000.dsl.inet.fi +37 -0
    tests check that slave does not crash as before.
    Slave threads must be in NO running state in the end.
    

  mysql-test/t/rpl_bug33931.test@1.0, 2008-02-13 14:09:40+02:00, aelkin@mysql1000.dsl.inet.fi +0 -0

  sql/slave.cc@1.304.1.1, 2008-02-13 14:09:40+02:00, aelkin@mysql1000.dsl.inet.fi +14 -4
    adding the bugs simulating code;
    relocating some assignments to satisfy the asserts;

ChangeSet@1.2567.10.1, 2008-02-12 15:12:45+04:00, ramil@mysql.com +1 -0
  Fix for bug #33758: Got query result when using ORDER BY ASC, but 
  empty result when using DESC
  
  Problem: fetching MyISAM keys we copy a key block pointer to the end of the key buffer.
  However, we don't take into account the pointer length calculatig the buffer size,
  that may leads to memory overwriting and in turn to unpredictable results.
  
  Fix: increase key buffer size by length of the key block pointer.
  
  Note: no simple test case.

  myisam/mi_open.c@1.111, 2008-02-12 15:12:44+04:00, ramil@mysql.com +3 -0
    Fix for bug #33758: Got query result when using ORDER BY ASC, but 
    empty result when using DESC
      - increase possible maximum key length by size of the key block pointer,
        as it's copied into the key buffer in the get_key() MyISAM functions.

ChangeSet@1.2559.48.1, 2008-02-12 12:43:55+03:00, kaa@mbp. +3 -0
  Fix for bug #33389: Selecting from a view into a table from within SP
                      or trigger crashes server
  
  Under some circumstances a combination of VIEWs, subselects with outer
  references and PS/SP/triggers could lead to use of uninitialized memory
  and server crash as a result.
  
  Fixed by changing the code in Item_field::fix_fields() so that in cases
  when the field is a VIEW reference, we first check whether the field
  is also an outer reference, and mark it appropriately before returning.

  mysql-test/r/view.result@1.209.1.2, 2008-02-12 12:43:53+03:00, kaa@mbp. +16 -0
    Added a test case for bug #33389.

  mysql-test/t/view.test@1.192, 2008-02-12 12:43:53+03:00, kaa@mbp. +22 -0
    Added a test case for bug #33389.

  sql/item.cc@1.297.2.1, 2008-02-12 12:43:54+03:00, kaa@mbp. +12 -12
    In cases when in Item_field::fix_fields() from_field is a view reference,
    do not return too early, i.e. before marking the reference as an outer
    one when needed.

ChangeSet@1.1616.3127.1, 2008-02-10 23:41:57+04:00, holyfoot@mysql.com +2 -0
  Bug #33796 Memory leak for prepared statements in embedded server.
  
  Field data for a query was stored to the stmt->alloc that is emptied
  with mysql_stmt_close statement only. That means a lot of memory can
  be occupied without a reason if used doesn't call mysql_stmt_close often.

  libmysql/libmysql.c@1.156.27.1, 2008-02-10 23:38:47+04:00, holyfoot@mysql.com +5 -8
    Bug #33796 Memory leak for prepared statements in embedded server.
    
    Clean up result->alloc even if there's no 'data' created

  libmysqld/lib_sql.cc@1.75.1.66, 2008-02-10 23:38:47+04:00, holyfoot@mysql.com +1 -1
    Bug #33796 Memory leak for prepared statements in embedded server.
    
    alloc 'fields' in the 'result.alloc' as the 'mem_root' is only cleaned with
    mysql_stmt_close'

ChangeSet@1.2567.3.11, 2008-02-08 21:03:10+02:00, aelkin@mysql1000.dsl.inet.fi +1 -0
  bug#34427 slave misses rendezvous in rpl_variables
  
  There was no instruction in the test that enforces the slave successfully connect
  to the master.
  The way the test was been written allowed the slave to had been late for rendezvous 
  so that about-connecting time queries to the master failed and are error-logged
  to had been seen in Warnings of pb.
  
  Fixed with adding a sychronization primitive to the test.
  No test case is possible, observe error logs on pb.
  
  Todo: revise need of rpl_report.pl's rules due to failing execution of
  queries from get_master_verion_and_clock().
  Any test should try to use a synchornization primitive like the current fix
  makes and do not let the slave to miss successful connecting.

  mysql-test/t/rpl_variables.test@1.6, 2008-02-08 21:03:09+02:00, aelkin@mysql1000.dsl.inet.fi +7 -0
    Completing the test's body with a synch macro to not let
    the slave to miss the successful connecting to the master.

ChangeSet@1.2559.45.2, 2008-02-08 16:04:01+04:00, gshchepa@host.loc +3 -0
  Fixed bug#15409: Columns with 64-element SET may not be updated with integers.
  
  SET column storing procedure has been modified to be 64bit-clean.

  mysql-test/r/type_set.result@1.15, 2008-02-08 16:03:45+04:00, gshchepa@host.loc +8 -0
    Added test case for bug#15409.

  mysql-test/t/type_set.test@1.12, 2008-02-08 16:03:47+04:00, gshchepa@host.loc +20 -0
    Added test case for bug#15409.

  sql/field.cc@1.372, 2008-02-08 16:03:48+04:00, gshchepa@host.loc +3 -3
    Fixed bug#15409.
    The Field_set::store(longlong nr,...) method incompletely
    calculates a bit mask for the comparison with a given number:
    if that number is greater than 0x7F00 0000 0000 0000 (LONGLONG_MAX),
    it uses zero bit mask instead of 0xFFFF FFFF FFFF FFFF (ULONGLONG_MAX).
    
    Incomplete expression has been replaced with a set_bits macro call.

ChangeSet@1.2559.46.1, 2008-02-08 13:35:00+03:00, evgen@sunlight.local +3 -0
  Bug#31590: Wrong error message on sort buffer being too small.
  
  The out of memory error was thrown when the sort buffer size were too small.
  This led to a user confusion.
  
  Now filesort throws the error message about sort buffer being too small.

  mysql-test/r/order_by.result@1.67, 2008-02-08 13:33:12+03:00, evgen@sunlight.local +12 -0
    Added a test case for the bug#31590: Wrong error message on sort buffer being too small.

  mysql-test/t/order_by.test@1.50, 2008-02-08 13:32:47+03:00, evgen@sunlight.local +12 -0
    Added a test case for the bug#31590: Wrong error message on sort buffer being too small.

  sql/filesort.cc@1.126.1.1, 2008-02-08 13:33:31+03:00, evgen@sunlight.local +1 -2
    Bug#31590: Wrong error message on sort buffer being too small.
    Now filesort throws the error message about sort buffer being too small
    instead of out of memory error.

ChangeSet@1.2559.44.2, 2008-02-07 11:12:49+04:00, gshchepa@host.loc +4 -0
  innodb_mysql.test, variables.result, variables.test, innodb_mysql.result:
    Minor post-fix for bug#34223.

  mysql-test/r/innodb_mysql.result@1.37, 2008-02-07 11:11:31+04:00, gshchepa@host.loc +6 -0
    Minor post-fix for bug#34223.

  mysql-test/r/variables.result@1.96.1.2, 2008-02-07 11:11:44+04:00, gshchepa@host.loc +0 -6
    Minor post-fix for bug#34223.

  mysql-test/t/innodb_mysql.test@1.36, 2008-02-07 11:11:49+04:00, gshchepa@host.loc +14 -0
    Minor post-fix for bug#34223.

  mysql-test/t/variables.test@1.74.1.2, 2008-02-07 11:11:51+04:00, gshchepa@host.loc +0 -13
    Minor post-fix for bug#34223.

ChangeSet@1.2559.38.7, 2008-02-07 05:10:04+03:00, sergefp@mysql.com +1 -0
  BUG#27732 "Possible memory leak with index_merge"
  The bug was that handler::clone/handler::ha_open() call caused allocation of 
  cloned_copy->ref on the handler->table->mem_root. The allocated memory could not 
  be reclaimed until the table is flushed, so it was possible to exhaust memory by 
  repeatedly running index_merge queries without doing table flushes.  
  
  The fix:
  - make handler::clone() allocate new_handler->ref on the passed mem_root 
  - make handler::ha_open() not allocate this->ref if it has already been allocated
  There is no testcase as it is not possible to check small leaks from testsuite.

  sql/handler.cc@1.241, 2008-02-07 05:09:59+03:00, sergefp@mysql.com +10 -2
    BUG#27732 "Possible memory leak with index_merge"
    - make handler::clone() allocate new_handler->ref on the passed mem_root 
    - make handler::ha_open() not allocate this->ref if it has already been allocated

ChangeSet@1.2559.38.5, 2008-02-07 04:54:58+04:00, gshchepa@host.loc +1 -0
  bdb.result:
    Minor post-fix for bug#30059.

  mysql-test/r/bdb.result@1.57, 2008-02-07 04:54:13+04:00, gshchepa@host.loc +1 -0
    Minor post-fix for bug#30059.

ChangeSet@1.2559.44.1, 2008-02-07 04:14:50+04:00, gshchepa@host.loc +3 -0
  Fixed bug#34223: Failure on assignment to my_innodb_autoextend_increment
  and my_innodb_commit_concurrency global variables.
  
  Type of the my_innodb_autoextend_increment and the
  my_innodb_commit_concurrency variables has been changed to
  GET_ULONG.
  

  mysql-test/r/variables.result@1.96.1.1, 2008-02-07 04:10:08+04:00, gshchepa@host.loc +6 -0
    Added test case for bug#34223.

  mysql-test/t/variables.test@1.74.1.1, 2008-02-07 04:10:10+04:00, gshchepa@host.loc +13 -0
    Added test case for bug#34223.

  sql/mysqld.cc@1.634, 2008-02-07 04:10:10+04:00, gshchepa@host.loc +2 -2
    Fixed bug#34223.
    Last update of the getopt_ull_limit_value function introduced
    a sanity check for a variable type (only GET_UINT or GET_ULONG
    are valid types).
    However, my_innodb_autoextend_increment and
    my_innodb_commit_concurrency are declared as GET_LONG.
    Call stack is: 
            sys_var_long_ptr_global::update()
            fix_unsigned()
            getopt_ull_limit_value()
    
    Type of the my_innodb_autoextend_increment and the
    my_innodb_commit_concurrency variables has been changed to
    GET_ULONG.

ChangeSet@1.2559.38.4, 2008-02-07 02:33:21+04:00, gshchepa@host.loc +9 -0
  Fixed bug#30059.
  Server handles truncation for assignment of too-long values
  into CHAR/VARCHAR/TEXT columns in a different ways when the
  truncated characters are spaces:
  1. CHAR(N) columns silently ignore end-space truncation;
  2. TEXT columns post a truncation warning/error in the
     non-strict/strict mode.
  3. VARCHAR columns always post a truncation note in
     any mode.
  
  Space truncation processing has been synchronised over
  CHAR/VARCHAR/TEXT columns: current behavior of VARCHAR
  columns has been propagated as standard.
  
  Binary-encoded string/BLOB columns are not affected.

  mysql-test/r/heap.result@1.51, 2008-02-07 02:32:57+04:00, gshchepa@host.loc +1 -0
    Updated test case for bug#30059.

  mysql-test/r/innodb.result@1.173, 2008-02-07 02:32:59+04:00, gshchepa@host.loc +1 -0
    Updated test case for bug#30059.

  mysql-test/r/myisam.result@1.103.1.1, 2008-02-07 02:32:59+04:00, gshchepa@host.loc +1 -0
    Updated test case for bug#30059.

  mysql-test/r/strict.result@1.37, 2008-02-07 02:33:00+04:00, gshchepa@host.loc +2 -0
    Updated test case for bug#30059.

  mysql-test/r/type_binary.result@1.5, 2008-02-07 02:33:00+04:00, gshchepa@host.loc +1 -0
    Updated test case for bug#30059.

  mysql-test/r/warnings.result@1.42, 2008-02-07 02:33:01+04:00, gshchepa@host.loc +38 -0
    Added test case for bug#30059.

  mysql-test/t/warnings.test@1.27, 2008-02-07 02:33:02+04:00, gshchepa@host.loc +33 -0
    Added test case for bug#30059.

  sql/field.cc@1.371, 2008-02-07 02:33:02+04:00, gshchepa@host.loc +31 -43
    Fixed bug#30059.
    The report_data_too_long function was replaced with the
    Field_longstr::report_if_important_data method.
    
    The Field_string::store and the Field_blob::store
    methods was synchronized with the Field_varstring::store
    method.
    Changes:
    1. to CHAR(N): posting of space truncation note has been added
       in both (strict and non-strict) modes;
    2. to BLOBs: a check for space truncation has been added,
       a warning in the non-strict mode and an error message in
       the strict mode have been replaced with a truncation note.
    
    Similar parts of Field_string::store, Field_blob::store and
    Field_varstring::store have been moved to the
    Field_longstr::report_if_important_data method.

  sql/field.h@1.216, 2008-02-07 02:33:03+04:00, gshchepa@host.loc +2 -0
    Fixed bug#30059.
    The Field_longstr::report_if_important_data method has been declared.

ChangeSet@1.2521.79.2, 2008-02-05 12:56:49+01:00, tnurnberg@blasphemy.intern.azundris.com +1 -0
  Bug#21567: mysqld doesn't react to Ctrl-C when run under GDB even with the --gdb option
  
  Don't block SIGINT (Control-C) when --gdb is passed to mysqld.
  Was broken at least on OS X.
  
  (kudos to Mattias Jonsson)

  sql/mysqld.cc@1.622.7.1, 2008-02-05 12:56:43+01:00, tnurnberg@blasphemy.intern.azundris.com +3 -5
    Don't block SIGINT when TEST_SIGINT (--gdb) is used, even if
    thr_kill_signal is some other signal (SIGUSR2) and
    pthread_sigmask() in signal_hand() isn't good enough.

ChangeSet@1.2541.110.1, 2008-02-04 16:37:41+02:00, aelkin@koti.dsl.inet.fi +2 -0
  Bug#33329  extraneous ROLLBACK in binlog on connection 
              does not use trans tables
  
  There had been two issues.
  Rollback statement was recorded in binlog even though a multi-update
  had not modified any non-transactional table.
  The reason for this artifact was a false initial value of multi_update::transactional_tables.
  Yet another artifact that explained on the bug page is that 
  `ha_autocommit_or_rollback' works differently depending on whether
  a transaction engine has been compiled in. 
  
  Fixed: with setting multi_update::transactional_tables to zero at initialization
  time. Multi-update on non-trans table won't cause ROLLBACK in binlog with
  either compilation option.
  
  The 2nd mentioned artifact comprises a self-standing issue (to be reported
  separately).

  mysql-test/r/multi_update.result@1.49, 2008-02-04 16:37:38+02:00, aelkin@koti.dsl.inet.fi +2 -2
    results changed - there is no ROLLBACK in binlog anymore as it should be

  sql/sql_update.cc@1.227, 2008-02-04 16:37:38+02:00, aelkin@koti.dsl.inet.fi +1 -1
    A wrong assumption on that there were modified transactional table,
    which is nonsense at the very beginning of the query execution.

ChangeSet@1.2541.109.1, 2008-02-04 16:35:41+02:00, aelkin@koti.dsl.inet.fi +1 -0
  Bug #32790 crash in trigger.test with InnoDB for a table
  
  the reason for the failure were incorrect asserts.
  
  Removing asserts altogether as there is no the implication does not hold
  (as explained in the comments for the file).

  sql/sql_delete.cc@1.203, 2008-02-04 16:35:38+02:00, aelkin@koti.dsl.inet.fi +0 -4
    removing two asserts because they can not hold basing on the definition
    of `normal_tables'. The one does not specify in a non-transactional table,
    which must be in the list of tables to be deleted, is modified indeed.
    So, it's possible to have normal_tables == true and deleted == true both
    but that would be yet a transactional table got modified (and then
    thd->transaction.stmt.modified_non_trans_table remains false default).

ChangeSet@1.2541.41.15, 2008-02-04 11:10:40+04:00, bar@mysql.com +26 -0
  Bug#32510 LIKE search fails with indexed 'eucjpms' and 'ujis' char column
  Problem: some collation handlers called incorrect version
  of my_like_range_xxx(), which led to wrong min_str and max_str,
  so like range optimizer threw away good records.
  Fix: changing the wrong handlers to call proper version of
  my_like_range_xxx().

  mysql-test/include/ctype_like_range_f1f2.inc@1.1, 2008-02-04 11:10:38+04:00, bar@mysql.com +25 -0
    New BitKeeper file ``mysql-test/include/ctype_like_range_f1f2.inc''

  mysql-test/include/ctype_like_range_f1f2.inc@1.0, 2008-02-04 11:10:38+04:00, bar@mysql.com +0 -0

  mysql-test/r/ctype_big5.result@1.15.1.1, 2008-02-04 11:10:37+04:00, bar@mysql.com +34 -0
    Adding test

  mysql-test/r/ctype_cp932.result@1.11.1.1, 2008-02-04 11:10:37+04:00, bar@mysql.com +34 -0
    Adding test

  mysql-test/r/ctype_eucjpms.result@1.7, 2008-02-04 11:10:37+04:00, bar@mysql.com +34 -0
    Adding test

  mysql-test/r/ctype_euckr.result@1.3.2.1, 2008-02-04 11:10:37+04:00, bar@mysql.com +34 -0
    Adding test

  mysql-test/r/ctype_gb2312.result@1.4.1.1, 2008-02-04 11:10:37+04:00, bar@mysql.com +34 -0
    Adding test

  mysql-test/r/ctype_gbk.result@1.6.1.1, 2008-02-04 11:10:37+04:00, bar@mysql.com +34 -0
    Adding test

  mysql-test/r/ctype_sjis.result@1.11, 2008-02-04 11:10:37+04:00, bar@mysql.com +34 -0
    Adding test

  mysql-test/r/ctype_uca.result@1.22.1.1, 2008-02-04 11:10:37+04:00, bar@mysql.com +17 -0
    Adding test

  mysql-test/r/ctype_ucs.result@1.57.1.1, 2008-02-04 11:10:37+04:00, bar@mysql.com +34 -0
    Adding test

  mysql-test/r/ctype_ujis.result@1.19, 2008-02-04 11:10:37+04:00, bar@mysql.com +34 -0
    Adding test

  mysql-test/t/ctype_big5.test@1.14, 2008-02-04 11:10:37+04:00, bar@mysql.com +2 -0
    Adding test

  mysql-test/t/ctype_cp932.test@1.13.1.1, 2008-02-04 11:10:37+04:00, bar@mysql.com +2 -0
    Adding test

  mysql-test/t/ctype_eucjpms.test@1.10, 2008-02-04 11:10:37+04:00, bar@mysql.com +2 -1
    Adding test

  mysql-test/t/ctype_euckr.test@1.3, 2008-02-04 11:10:37+04:00, bar@mysql.com +2 -0
    Adding test

  mysql-test/t/ctype_gb2312.test@1.2, 2008-02-04 11:10:37+04:00, bar@mysql.com +2 -0
    Adding test

  mysql-test/t/ctype_gbk.test@1.6, 2008-02-04 11:10:37+04:00, bar@mysql.com +2 -0
    Adding test

  mysql-test/t/ctype_sjis.test@1.12, 2008-02-04 11:10:37+04:00, bar@mysql.com +2 -0
    Adding test

  mysql-test/t/ctype_uca.test@1.19.1.1, 2008-02-04 11:10:37+04:00, bar@mysql.com +2 -1
    Adding test

  mysql-test/t/ctype_ucs.test@1.55.1.1, 2008-02-04 11:10:37+04:00, bar@mysql.com +2 -0
    Adding test

  mysql-test/t/ctype_ujis.test@1.19, 2008-02-04 11:10:37+04:00, bar@mysql.com +2 -0
    Adding test

  strings/ctype-euc_kr.c@1.72, 2008-02-04 11:10:38+04:00, bar@mysql.com +1 -1
    Changing like_range function

  strings/ctype-eucjpms.c@1.18, 2008-02-04 11:10:38+04:00, bar@mysql.com +1 -1
    Changing like_range function

  strings/ctype-gb2312.c@1.68, 2008-02-04 11:10:38+04:00, bar@mysql.com +1 -1
    Changing like_range function

  strings/ctype-ucs2.c@1.67.1.1, 2008-02-04 11:10:38+04:00, bar@mysql.com +1 -1
    Changing like_range function

  strings/ctype-ujis.c@1.75, 2008-02-04 11:10:38+04:00, bar@mysql.com +1 -1
    Changing like_range function

ChangeSet@1.2559.28.8, 2008-02-01 14:10:46+01:00, thek@adventure.(none) +3 -0
  Bug#33201 Crash occurs when granting update privilege on one column of a view
  
  When issuing a column level grant on a table which require pre-locking the 
  server crashed.
  
  The reason behind the crash was that data structures used by the lock api
  wasn't properly reinitialized in the case of a column level grant.

  mysql-test/r/grant.result@1.71, 2008-02-01 14:10:44+01:00, thek@adventure.(none) +22 -0
    * Added test case

  mysql-test/t/grant.test@1.60, 2008-02-01 14:10:44+01:00, thek@adventure.(none) +22 -0
    * Added test case

  sql/sql_acl.cc@1.224.2.1, 2008-02-01 14:10:44+01:00, thek@adventure.(none) +7 -0
    * The lock api is dending on the thd->lex object and this variable needs to 
      be re-initialized when opened with a new set of tables than specified in the
      original statement.

ChangeSet@1.2559.42.1, 2008-02-01 13:00:40+05:00, kaa@mbp.local +3 -0
  Fix for bug #25162: Backing up DB from 5.1 adds 'USING BTREE' to KEYs 
                      on table creates
  
  The problem was in incompatible syntax for key definition in CREATE
  TABLE.
  
  5.0 supports only the following syntax for key definition (see "CREATE
  TABLE syntax" in the manual):
  
  {INDEX|KEY} [index_name] [index_type] (index_col_name,...)
  
  While 5.1 parser supports the above syntax, the "preferred" syntax was
  changed to:
  
  {INDEX|KEY} [index_name] (index_col_name,...) [index_type]
  
  The above syntax is used in 5.1 for the SHOW CREATE TABLE output, which
  led to dumps generated by 5.1 being incompatible with 5.0.
  
  Fixed by changing the parser in 5.0 to support both 5.0 and 5.1 syntax
  for key definition.

  mysql-test/r/create.result@1.137, 2008-02-01 13:00:39+05:00, kaa@mbp.local +14 -0
    Added a test case for bug #25162.

  mysql-test/t/create.test@1.94, 2008-02-01 13:00:39+05:00, kaa@mbp.local +24 -0
    Added a test case for bug #25162.

  sql/sql_yacc.yy@1.544.1.1, 2008-02-01 13:00:39+05:00, kaa@mbp.local +3 -3
    Changed the parser to support both 5.0 and 5.1 syntax for index type
    specification in CREATE TABLE.

ChangeSet@1.2559.38.2, 2008-01-31 23:46:26+03:00, evgen@moonbone.local +3 -0
  Bug#30787: Stored function ignores user defined alias.
  
  Simple subselects are pulled into upper selects. This operation substitutes the
  pulled subselect for the first item from the select list of the subselect.
  If an alias is defined for a subselect it is inherited by the replacement item.
  As this is done after fix_fields phase this alias isn't showed if the
  replacement item is a stored function. This happens because the Item_func_sp::make_field
  function makes send field from its result_field and ignores the defined alias.
  
  Now when an alias is defined the Item_func_sp::make_field function sets it for
  the returned field.

  mysql-test/r/sp.result@1.244.2.1, 2008-01-31 23:45:40+03:00, evgen@moonbone.local +17 -0
    Added a test case for the bug#30787: Stored function ignores user defined alias.

  mysql-test/t/sp.test@1.232.2.1, 2008-01-31 23:45:38+03:00, evgen@moonbone.local +19 -0
    Added a test case for the bug#30787: Stored function ignores user defined alias.

  sql/item_func.cc@1.365, 2008-01-31 23:45:51+03:00, evgen@moonbone.local +2 -0
    Bug#30787: Stored function ignores user defined alias.
    Now when an alias is defined the Item_func_sp::make_field function sets it for
    the returned field.

ChangeSet@1.2567.1.2, 2008-01-31 18:51:20+04:00, svoj@mysql.com +1 -0
  BUG#22989 - START SLAVE causes Error on COM_REGISTER_SLAVE: 1105
              'Wrong parameters to functi
  
  START SLAVE reports vague error when it fails to register on master:
  "Wrong parameters to function register_slave".
  
  If master failed to register slave because of too long
  'report-host'/'report-user'/'report-password', return better error
  messages:
  "Failed to register slave: too long 'report-host'"
  "Failed to register slave: too long 'report-user'"
  "Failed to register slave; too long 'report-password'"
  
  No test case for this fix.

  sql/repl_failsafe.cc@1.67, 2008-01-31 18:51:18+04:00, svoj@mysql.com +9 -6
    Report descriptive error when master fails to register slave.

ChangeSet@1.2559.38.1, 2008-01-26 21:45:35-08:00, igor@olga.mysql.com +5 -0
  Fixed bug #33833.
  Two disjuncts containing equalities of the form key=const1 and key=const2 can
  be merged into one if const1 is equal to const2. To check it the common 
  collation of the constants were used rather than the collation of the field key.
  For example when the default collation of the constants was cases insensitive
  while the collation of the field was case sensitive, then two or-ed equality 
  predicates key='b' and key='B' incorrectly were merged into one f='b'. As a 
  result ref access was used instead of range access and wrong result sets were 
  returned in many cases. 
  Fixed the problem by comparing constant in the or-ed predicate with collation of
  the key field.

  mysql-test/r/range.result@1.60, 2008-01-26 21:45:30-08:00, igor@olga.mysql.com +13 -0
    Added a test case for bug #33833.

  mysql-test/t/range.test@1.50, 2008-01-26 21:45:30-08:00, igor@olga.mysql.com +17 -0
    Added a test case for bug #33833.

  sql/item.cc@1.298, 2008-01-26 21:45:30-08:00, igor@olga.mysql.com +43 -0
    Fixed bug #33833.
    Added the method eq_by_collation that compares two items almost as 
    the method Item::eq, but it rather enforces a given collation for
    the comparison.

  sql/item.h@1.249, 2008-01-26 21:45:30-08:00, igor@olga.mysql.com +1 -0
    Fixed bug #33833.
    Added the method eq_by_collation that compares two items almost as 
    the method Item::eq, but it rather enforces a given collation for
    the comparison.

  sql/sql_select.cc@1.550.1.8, 2008-01-26 21:45:30-08:00, igor@olga.mysql.com +3 -1
    Fixed bug #33833.
    Two disjuncts containing equalities of the form key=const1 and key=const2 can
    be merged into one if const1 is equal to const2. To check it the common 
    collation of the constants were used rather than the collation of the field key.
    For example when the default collation of the constants was cases insensitive
    while the collation of the field was case sensitive, then two or-ed equality 
    predicates key='b' and key='B' incorrectly were merged into one f='b'. As a 
    result ref access was used instead of range access and wrong result sets were 
    returned in many cases. 
    Fixed the problem by comparing constant in the or-ed predicate with collation of
    the key field.

ChangeSet@1.2559.18.2, 2008-01-16 11:48:04+01:00, istruewing@stella.local +4 -0
  Bug#32705 - myisam corruption: Key in wrong position
              at page 1024 with ucs2_bin
  Post-pushbuild fix.
  Moved test from myisam.test to ctype_ucs2_def.test.
  UCS2 is not always available.

  mysql-test/r/ctype_ucs2_def.result@1.6, 2008-01-16 11:48:03+01:00, istruewing@stella.local +10 -0
    Bug#32705 - myisam corruption: Key in wrong position
                at page 1024 with ucs2_bin
    Moved test result from myisam.result to here.

  mysql-test/r/myisam.result@1.102.1.2, 2008-01-16 11:48:03+01:00, istruewing@stella.local +0 -10
    Bug#32705 - myisam corruption: Key in wrong position
                at page 1024 with ucs2_bin
    Moved test result from here to ctype_ucs2_def.result.

  mysql-test/t/ctype_ucs2_def.test@1.7, 2008-01-16 11:48:03+01:00, istruewing@stella.local +13 -0
    Bug#32705 - myisam corruption: Key in wrong position
                at page 1024 with ucs2_bin
    Moved test from myisam.test to here.
    UCS2 is not always available.

  mysql-test/t/myisam.test@1.83.1.2, 2008-01-16 11:48:03+01:00, istruewing@stella.local +0 -13
    Bug#32705 - myisam corruption: Key in wrong position
                at page 1024 with ucs2_bin
    Moved test from here to ctype_ucs2_def.test.
    UCS2 is not always available.

ChangeSet@1.1346.895.5, 2008-01-03 21:38:05+01:00, kent@mysql.com +2 -0
  configure.in, acinclude.m4:
    Minor cleanup, removed semicolons not needed

  acinclude.m4@1.77.1.26, 2008-01-03 21:37:47+01:00, kent@mysql.com +2 -2
    Minor cleanup, removed semicolons not needed

  configure.in@1.191.1.154, 2008-01-03 21:37:47+01:00, kent@mysql.com +15 -15
    Minor cleanup, removed semicolons not needed

ChangeSet@1.2559.18.1, 2007-12-18 12:29:50+01:00, istruewing@stella.local +3 -0
  Bug#32705 - myisam corruption: Key in wrong position
              at page 1024 with ucs2_bin
  
  Inserting strings with a common prefix into a table with
  characterset UCS2 corrupted the table.
  
  An efficient search method was used, which compares end space
  with ASCII blank. This doesn't work for character sets like UCS2,
  which do not encode blank like ASCII does.
  
  Use the less efficient search method _mi_seq_search()
  for charsets with mbminlen > 1.

  myisam/mi_open.c@1.110, 2007-12-18 12:29:47+01:00, istruewing@stella.local +10 -1
    Bug#32705 - myisam corruption: Key in wrong position
                at page 1024 with ucs2_bin
    Use _mi_seq_search() for charsets with mbminlen > 1.

  mysql-test/r/myisam.result@1.102.1.1, 2007-12-18 12:29:47+01:00, istruewing@stella.local +10 -0
    Bug#32705 - myisam corruption: Key in wrong position
                at page 1024 with ucs2_bin
    Added test result.

  mysql-test/t/myisam.test@1.83.1.1, 2007-12-18 12:29:47+01:00, istruewing@stella.local +13 -0
    Bug#32705 - myisam corruption: Key in wrong position
                at page 1024 with ucs2_bin
    Added test.

ChangeSet@1.2521.23.10, 2007-10-08 12:46:38+05:00, bar@mysql.com +11 -0
  Bug#27580 SPACE() function collation bug?
  Problem: when character_set_connection=utf8,
  mixing SPACE() with a non-Unicode column (e.g. for concat)
  produced "illegal mix of collations" error.
  Fix: Item_string() corresponding to space character
  is now created using "ASCII" repertoire. Previously
  it was incorrectly created using "UNICODE" repertoure, which
  didn't allow to convert results of SPACE() to a non-Unicode
  character set.

  mysql-test/include/ctype_common.inc@1.2.1.1, 2007-10-08 12:46:36+05:00, bar@mysql.com +16 -0
    - Adding test for bug#27580
    - Restoring previous values of character_set_client and character_set_results,
    because ctype_common.inc now changes them when doing "set names utf8"
    in the test for bug#27580
    

  mysql-test/r/ctype_big5.result@1.13.1.1, 2007-10-08 12:46:36+05:00, bar@mysql.com +19 -0
    Adding test

  mysql-test/r/ctype_cp1250_ch.result@1.7, 2007-10-08 12:46:36+05:00, bar@mysql.com +152 -0
    Adding test

  mysql-test/r/ctype_euckr.result@1.4, 2007-10-08 12:46:36+05:00, bar@mysql.com +19 -0
    Adding test

  mysql-test/r/ctype_gb2312.result@1.2.1.1, 2007-10-08 12:46:36+05:00, bar@mysql.com +19 -0
    Adding test

  mysql-test/r/ctype_gbk.result@1.4.1.1, 2007-10-08 12:46:36+05:00, bar@mysql.com +19 -0
    Adding test

  mysql-test/r/ctype_uca.result@1.19.2.1, 2007-10-08 12:46:37+05:00, bar@mysql.com +19 -0
    Adding test

  mysql-test/r/ctype_ucs.result@1.55.1.1, 2007-10-08 12:46:37+05:00, bar@mysql.com +76 -0
    Adding test

  mysql-test/t/ctype_cp1250_ch.test@1.7, 2007-10-08 12:46:37+05:00, bar@mysql.com +10 -0
    Adding test

  mysql-test/t/ctype_ucs.test@1.53.1.1, 2007-10-08 12:46:37+05:00, bar@mysql.com +4 -0
    Adding test

  sql/item_create.cc@1.68, 2007-10-08 12:46:37+05:00, bar@mysql.com +2 -2
    Item for SQL function SPACE() is now created with ASCII repertoire,
    to allow automatic conversion from UTF8 to column's character
    set e.g. for CONCAT().

