ChangeSet@1.2468, 2007-04-20 15:52:49+02:00, kent@mysql.com +1 -0
  Makefile.am:
    Typo

  mysql-test/Makefile.am@1.91, 2007-04-20 15:52:41+02:00, kent@mysql.com +1 -1
    Typo

ChangeSet@1.2467, 2007-04-20 15:49:35+02:00, kent@mysql.com +1 -0
  Makefile.am:
    Added the 'suite' directory to the source TAR and install

  mysql-test/Makefile.am@1.90, 2007-04-20 15:49:25+02:00, kent@mysql.com +8 -1
    Added the 'suite' directory to the source TAR and install

ChangeSet@1.2466, 2007-04-20 12:37:32+02:00, tomas@whalegate.ndb.mysql.com +2 -0
  Construction does not work on hpux aCC, so some refactoring

  ndb/include/ndbapi/Ndb.hpp@1.50, 2007-04-20 12:37:29+02:00, tomas@whalegate.ndb.mysql.com +1 -12
    Construction does not work on hpux aCC, so some refactoring

  ndb/src/ndbapi/NdbImpl.hpp@1.17, 2007-04-20 12:37:30+02:00, tomas@whalegate.ndb.mysql.com +12 -3
    Construction does not work on hpux aCC, so some refactoring

ChangeSet@1.2465, 2007-04-20 11:53:53+02:00, kent@mysql.com +1 -0
  testScanFilter.cpp:
    Corrected copyright header

  ndb/test/ndbapi/testScanFilter.cpp@1.2, 2007-04-20 11:53:08+02:00, kent@mysql.com +2 -3
    Corrected copyright header

ChangeSet@1.2464, 2007-04-19 22:56:04+02:00, kent@mysql.com +2 -0
  mysql.sln:
    Enable 'mysys' build if target 'Enterprise'
  item_subselect.h:
    Fixed bug #27870. The bug that causes crashes manifests itself at some
    conditions when executing an equijoin query with WHERE condition
    containing a subquery predicate of the form join_attr NOT IN (SELECT ...).

  VC++Files/mysql.sln@1.18, 2007-04-19 10:48:20+02:00, kent@mysql.com +1 -0
    Enable 'mysys' build if target 'Enterprise'

  sql/item_subselect.h@1.89, 2007-04-19 22:54:44+02:00, kent@mysql.com +5 -1
    Fixed bug #27870. The bug that causes crashes manifests itself at some
    conditions when executing an equijoin query with WHERE condition
    containing a subquery predicate of the form join_attr NOT IN (SELECT ...).

ChangeSet@1.2455.1.3, 2007-04-18 16:41:38+02:00, joerg@trift2. +1 -0
  sql/ha_ndbcluster.cc
      Hex constants that exceed 32 bit need to be marked "LL" for the compile to work.

  sql/ha_ndbcluster.cc@1.310, 2007-04-18 16:41:33+02:00, joerg@trift2. +4 -4
    Hex constants that exceed 32 bit need to be marked "LL" for the compile to work
    (discovered on a Debian PPC box, 32-bit big-endian, running gcc 3.3.6).

ChangeSet@1.2462, 2007-04-17 11:23:49-07:00, omer@linux.localdomain +1 -0
  Added funcs_1 and funcs_2 to the test-bt option

  Makefile.am@1.100, 2007-04-17 11:23:41-07:00, omer@linux.localdomain +4 -0
    Added funcs_1 and funcs_2 to the test-bt option

ChangeSet@1.2461, 2007-04-17 15:40:38+02:00, kent@mysql.com +1 -0
  Dbdict.cpp:
    Bug #27710 Creating unique index fails during single user mode
    - enable indexes to be used always, if in single user, reject will happen before, and if it is kerlel doing stuff, it should always be allowed

  ndb/src/kernel/blocks/dbdict/Dbdict.cpp@1.78, 2007-04-17 15:36:30+02:00, kent@mysql.com +1 -0
    Bug #27710 Creating unique index fails during single user mode
    - enable indexes to be used always, if in single user, reject will happen before, and if it is kerlel doing stuff, it should always be allowed

ChangeSet@1.2460, 2007-04-17 15:20:48+02:00, kent@mysql.com +3 -0
  Bug#27783 mysql_install_db should be able to install again, preserving existing files.
   - Allow mysql_install_db to be run a second time in the same
     datadir to create and fill any missing system tables

  scripts/mysql_install_db.sh@1.73, 2007-04-17 15:18:34+02:00, kent@mysql.com +0 -11
    Remove check that dissallowed running mysql_install_db a second time
    in same directory

  scripts/mysql_system_tables.sql@1.5, 2007-04-17 15:19:17+02:00, kent@mysql.com +5 -0
    Save information about if tables db and user already existed

  scripts/mysql_system_tables_data.sql@1.2, 2007-04-17 15:19:36+02:00, kent@mysql.com +15 -7
    Fill tables db and user with initial data if tables
    didn't already exist.

ChangeSet@1.2455.1.2, 2007-04-17 14:41:07+02:00, joerg@trift2. +1 -0
  Cleanup: The temporary file could be left around if nothing was excluded.

  configure.in@1.438, 2007-04-17 14:41:03+02:00, joerg@trift2. +1 -1
    Cleanup: The temporary file could be left around if nothing was excluded.

ChangeSet@1.2456.1.1, 2007-04-17 12:32:01+02:00, serg@janus.mylan +4 -0
  reverted the fix for Bug#5507

  mysql-test/r/truncate.result@1.13, 2007-04-17 12:31:58+02:00, serg@janus.mylan +3 -23
    reverted the fix for Bug#5507

  mysql-test/t/truncate.test@1.14, 2007-04-17 12:31:58+02:00, serg@janus.mylan +8 -23
    reverted the fix for Bug#5507

  sql/sql_delete.cc@1.197, 2007-04-17 12:31:58+02:00, serg@janus.mylan +3 -6
    reverted the fix for Bug#5507

  sql/sql_lex.cc@1.219, 2007-04-17 12:31:58+02:00, serg@janus.mylan +0 -1
    reverted the fix for Bug#5507

ChangeSet@1.2455.1.1, 2007-04-17 12:18:17+02:00, joerg@trift2. +1 -0
  Let the "configure" options that control table handlers (NDB, InnoDB) or features ("embedded")
  also control the list of man pages installed, so that they correspond better to the binaries.
  
  This is the second version of this fix, including review comments.

  configure.in@1.437, 2007-04-17 12:18:13+02:00, joerg@trift2. +54 -22
    Several of our man pages are specific to parts (table handlers, features, ...)
    which are controlled by "configure" options, so there are builds which do not
    include these parts.
    For such builds, remove those specific man pages from the list of man pages
    to be installed, so that the man pages correspond better to the binaries.
    
    In this patch, do it for NDB (modify Kent's approach), "embedded", and InnoDB.
    
    Ensure that the handling of the man pages is determined only after the options
    have been processed, the old nandling (NDB only) was done too early.
    
    This is the second version of this fix, including review comments.

ChangeSet@1.2455, 2007-04-15 09:54:16+04:00, evgen@moonbone.local +1 -0
  item.cc:
    Fix warning after fix for bug#27321.
  TAG: clone-5.0.40-build

  sql/item.cc@1.262, 2007-04-15 09:53:24+04:00, evgen@moonbone.local +1 -1
    Fix warning after fix for bug#27321.

ChangeSet@1.2454, 2007-04-15 09:22:45+04:00, evgen@moonbone.local +2 -0
  subselect.test, subselect.result:
    After merge fix.

  mysql-test/r/subselect.result@1.184, 2007-04-15 09:22:28+04:00, evgen@moonbone.local +1 -0
    After merge fix.

  mysql-test/t/subselect.test@1.149, 2007-04-15 09:22:35+04:00, evgen@moonbone.local +1 -0
    After merge fix.

ChangeSet@1.2410.28.1, 2007-04-15 08:31:34+04:00, evgen@moonbone.local +8 -0
  Bug#27321: Wrong subquery result in a grouping select.
  
  The Item_outer_ref class based on the Item_direct_ref class was always used
  to represent an outer field. But if the outer select is a grouping one and the 
  outer field isn't under an aggregate function which is aggregated in that
  outer select an Item_ref object should be used to represent such a field.
  If the outer select in which the outer field is resolved isn't grouping then
  the Item_field class should be used to represent such a field.
  This logic also should be used for an outer field resolved through its alias
  name.
  
  Now the Item_field::fix_outer_field() uses Item_outer_field objects to
  represent aliased and non-aliased outer fields for grouping outer selects
  only.
  Now the fix_inner_refs() function chooses which class to use to access outer
  field - the Item_ref or the Item_direct_ref. An object of the chosen class
  substitutes the original field in the Item_outer_ref object.
  The direct_ref and the found_in_select_list fields were added to the
  Item_outer_ref class.

  mysql-test/r/subselect.result@1.181.1.1, 2007-04-15 08:31:15+04:00, evgen@moonbone.local +68 -3
    Added a test case for the bug#27321: Wrong subquery result in a grouping select.
    Some test cases were corrected after this fix.

  mysql-test/r/subselect3.result@1.6.1.1, 2007-04-15 08:31:14+04:00, evgen@moonbone.local +2 -8
    Some test cases were corrected after the fix for the bug#27321.

  mysql-test/t/subselect.test@1.146.1.1, 2007-04-15 08:31:14+04:00, evgen@moonbone.local +37 -0
    Added a test case for the bug#27321: Wrong subquery result in a grouping select.

  mysql-test/t/subselect3.test@1.6.1.1, 2007-04-15 08:31:12+04:00, evgen@moonbone.local +0 -2
    Some test cases were corrected after the fix for the bug#27321.

  sql/item.cc@1.259.1.1, 2007-04-15 08:31:18+04:00, evgen@moonbone.local +39 -44
    Bug#27321: Wrong subquery result in a grouping select.
    Now the Item_field::fix_outer_field() uses Item_outer_field objects to
    represent aliased and non-aliased outer fields for grouping outer selects
    only.

  sql/item.h@1.224.1.1, 2007-04-15 08:31:18+04:00, evgen@moonbone.local +31 -13
    Bug#27321: Wrong subquery result in a grouping select.
    The direct_ref and the found_in_select_list fields were added to the
    Item_outer_ref class.

  sql/sql_select.cc@1.502.3.1, 2007-04-15 08:31:16+04:00, evgen@moonbone.local +70 -22
    Bug#27321: Wrong subquery result in a grouping select.
    Now the fix_inner_refs() function chooses which class to use to access outer
    field - the Item_ref or the Item_direct_ref. An object of the chosen class
    substitutes the original field in the Item_outer_ref object.
    A comment is corrected.

  sql/sql_union.cc@1.141, 2007-04-15 08:31:15+04:00, evgen@moonbone.local +1 -0
    Bug#27321: Wrong subquery result in a grouping select.
    Cleanup of the inner_refs_list.

ChangeSet@1.2446.1.2, 2007-04-13 01:37:24+02:00, tomas@whalegate.ndb.mysql.com +4 -0
  Bug#27775 mediumint auto_increment with ndb_restore
  - autoincrement column of size medium int not handled in ndb_restore
  - added testcase also for other types, tiny, small... etc

  mysql-test/r/ndb_restore.result@1.7, 2007-04-13 01:37:22+02:00, tomas@whalegate.ndb.mysql.com +24 -5
    Bug#27775 mediumint auto_increment with ndb_restore
    - autoincrement column of size medium int not handled in ndb_restore
    - added testcase also for other types, tiny, small... etc

  mysql-test/t/ndb_restore.test@1.12, 2007-04-13 01:37:22+02:00, tomas@whalegate.ndb.mysql.com +28 -5
    Bug#27775 mediumint auto_increment with ndb_restore
    - autoincrement column of size medium int not handled in ndb_restore
    - added testcase also for other types, tiny, small... etc

  ndb/tools/restore/Restore.hpp@1.25, 2007-04-13 01:37:22+02:00, tomas@whalegate.ndb.mysql.com +3 -0
    Bug#27775 mediumint auto_increment with ndb_restore
    - autoincrement column of size medium int not handled in ndb_restore
    - added testcase also for other types, tiny, small... etc

  ndb/tools/restore/consumer_restore.cpp@1.29, 2007-04-13 01:37:22+02:00, tomas@whalegate.ndb.mysql.com +2 -2
    Bug#27775 mediumint auto_increment with ndb_restore
    - autoincrement column of size medium int not handled in ndb_restore
    - added testcase also for other types, tiny, small... etc

ChangeSet@1.2441.1.4, 2007-04-12 21:50:56+02:00, joerg@trift2. +1 -0
  Header file "decimal.h" needs to be delivered with binary packages:
  
  Bug#27456    decimal.h is not installed with public include files

  include/Makefile.am@1.68, 2007-04-12 21:50:53+02:00, joerg@trift2. +2 -2
    Header file "decimal.h" needs to be delivered with binary packages:
    
    Bug#27456    decimal.h is not installed with public include files

ChangeSet@1.2446.1.1, 2007-04-12 21:34:25+02:00, tomas@whalegate.ndb.mysql.com +2 -0
  remove inline NdbRecAttr functions for medium int as not to depend in my_global

  ndb/include/ndbapi/NdbRecAttr.hpp@1.21, 2007-04-12 21:34:23+02:00, tomas@whalegate.ndb.mysql.com +0 -14
    remove inline NdbRecAttr functions for medium int as not to depend in my_global

  ndb/src/ndbapi/NdbRecAttr.cpp@1.35, 2007-04-12 21:34:23+02:00, tomas@whalegate.ndb.mysql.com +12 -0
    remove inline NdbRecAttr functions for medium int as not to depend in my_global

ChangeSet@1.2448, 2007-04-12 23:21:37+05:00, gshchepa@gshchepa.localdomain +6 -0
  Bug#5507: TRUNCATE does not work with views.
  Support of views wasn't implemented for the TRUNCATE statement.
  Now TRUNCATE on views has the same semantics as DELETE FROM view:
  mysql_truncate() checks whether the table is a view and falls back
  to delete if so.
  In order to initialize properly the LEX::updatable for a view
  st_lex::can_use_merged() now allows usage of merged views for the
  TRUNCATE statement.

  mysql-test/r/truncate.result@1.12, 2007-04-12 23:16:18+05:00, gshchepa@gshchepa.localdomain +27 -0
    Added a test case for the Bug#5507: TRUNCATE does not work with views.

  mysql-test/r/view.result@1.198, 2007-04-12 23:20:46+05:00, gshchepa@gshchepa.localdomain +10 -0
    Updated test case for Bug#14540: OPTIMIZE, ANALYZE, REPAIR applied 
    to not a view.

  mysql-test/t/truncate.test@1.13, 2007-04-12 23:17:05+05:00, gshchepa@gshchepa.localdomain +32 -0
    Added a test case for the Bug#5507: TRUNCATE does not work with views.

  mysql-test/t/view.test@1.181, 2007-04-12 23:19:34+05:00, gshchepa@gshchepa.localdomain +2 -0
    Updated test case for Bug#14540: OPTIMIZE, ANALYZE, REPAIR applied 
    to not a view.

  sql/sql_delete.cc@1.196, 2007-04-12 23:18:27+05:00, gshchepa@gshchepa.localdomain +6 -3
    Bug#5507: TRUNCATE does not work with views.
    1.mysql_truncate() was lacking of check whether the table is view. Added.
    2.mysql_truncate() calls mysql_delete(), but mysql_delete() always reports
    errors as "DELETE" errors. Fixed.

  sql/sql_lex.cc@1.218, 2007-04-12 23:17:23+05:00, gshchepa@gshchepa.localdomain +1 -0
    Bug#5507: TRUNCATE does not work with views.
    can_use_merged() was denying of usage of merged views for a
    TRUNCATE statement. This results in improper initialization
    of view LEX::updatable. Fixed.

ChangeSet@1.2441.2.5, 2007-04-12 11:07:30+02:00, tomas@whalegate.ndb.mysql.com +5 -0
  Bug #27758 Restoring NDB backups makes table usable in SQL nodes
  - parse indexname using "split" instead of sscanf, as not to break at space
  - test case with space in key
  - enclose names in printout

  mysql-test/r/ndb_restore.result@1.6, 2007-04-12 11:07:28+02:00, tomas@whalegate.ndb.mysql.com +40 -40
    Bug #27758 Restoring NDB backups makes table usable in SQL nodes
    - change to using an index with space to reproduce bug

  mysql-test/t/ndb_restore.test@1.11, 2007-04-12 11:07:28+02:00, tomas@whalegate.ndb.mysql.com +44 -41
    Bug #27758 Restoring NDB backups makes table usable in SQL nodes
    - change to using an index with space to reproduce bug

  ndb/tools/restore/consumer_restore.cpp@1.28, 2007-04-12 11:07:28+02:00, tomas@whalegate.ndb.mysql.com +31 -25
    Bug #27758 Restoring NDB backups makes table usable in SQL nodes
    - parse indexname using "split" instead of sscanf, as not to break at space
    - enclose names in printout

  ndb/tools/restore/restore_main.cpp@1.41, 2007-04-12 11:07:28+02:00, tomas@whalegate.ndb.mysql.com +2 -2
    Bug #27758 Restoring NDB backups makes table usable in SQL nodes
    - enclose names in printout

  sql/ha_ndbcluster.cc@1.309, 2007-04-12 11:07:28+02:00, tomas@whalegate.ndb.mysql.com +4 -2
    Bug #27758 Restoring NDB backups makes table usable in SQL nodes
    - correct error message

ChangeSet@1.2443.1.2, 2007-04-11 12:45:27-07:00, igor@olga.mysql.com +2 -0
  Post-merge fix.

  mysql-test/r/row.result@1.27, 2007-04-11 12:45:25-07:00, igor@olga.mysql.com +6 -0
    Post-merge fix.

  sql/item_cmpfunc.cc@1.244, 2007-04-11 12:45:25-07:00, igor@olga.mysql.com +3 -3
    Post-merge fix.

ChangeSet@1.1616.3014.1, 2007-04-11 11:41:12-07:00, igor@olga.mysql.com +3 -0
  Fixed bug #27484: a crash when incompatible row expressions with nested rows
  are used as arguments of the IN predicate.
  Added a function to check compatibility of row expressions. Made sure that this
  function to be called for Item_func_in objects by fix_length_and_dec().

  mysql-test/r/row.result@1.18.1.1, 2007-04-11 11:41:11-07:00, igor@olga.mysql.com +18 -0
    Added a test case for bug #27484.

  mysql-test/t/row.test@1.16.1.2, 2007-04-11 11:41:11-07:00, igor@olga.mysql.com +25 -0
    Added a test case for bug #27484.

  sql/item_cmpfunc.cc@1.111.23.18, 2007-04-11 11:41:11-07:00, igor@olga.mysql.com +61 -4
    Fixed bug #27484: a crash when incompatible row expressions with nested rows
    are used as arguments of the IN predicate.
    Added a function to check compatibility of row expressions. Made sure that this
    function to be called for Item_func_in objects by fix_length_and_dec().

ChangeSet@1.2441.2.4, 2007-04-11 20:22:31+02:00, tomas@whalegate.ndb.mysql.com +1 -0
  remove warning

  ndb/src/ndbapi/Ndbif.cpp@1.38, 2007-04-11 20:22:29+02:00, tomas@whalegate.ndb.mysql.com +1 -1
    remove warning

ChangeSet@1.2441.2.3, 2007-04-11 19:29:32+02:00, tomas@whalegate.ndb.mysql.com +1 -0
  missing return

  ndb/src/ndbapi/Ndb.cpp@1.69, 2007-04-11 19:29:30+02:00, tomas@whalegate.ndb.mysql.com +1 -0
    missing return

ChangeSet@1.2441.3.1, 2007-04-11 15:21:11+02:00, tomas@whalegate.ndb.mysql.com +29 -0
  Bug#26176 NdbObjectIdMap::expand unable to expand!! mysqld got signal 11
  - try to catch as many malloc failures as possible and give error messages

  ndb/include/ndbapi/Ndb.hpp@1.49, 2007-04-11 15:21:08+02:00, tomas@whalegate.ndb.mysql.com +16 -4
    Bug#26176 NdbObjectIdMap::expand unable to expand!! mysqld got signal 11
    - try to catch as many malloc failures as possible and give error messages

  ndb/include/ndbapi/NdbDictionary.hpp@1.59, 2007-04-11 15:21:08+02:00, tomas@whalegate.ndb.mysql.com +12 -12
    Bug#26176 NdbObjectIdMap::expand unable to expand!! mysqld got signal 11
    - try to catch as many malloc failures as possible and give error messages

  ndb/include/ndbapi/NdbReceiver.hpp@1.19, 2007-04-11 15:21:08+02:00, tomas@whalegate.ndb.mysql.com +2 -2
    Bug#26176 NdbObjectIdMap::expand unable to expand!! mysqld got signal 11
    - try to catch as many malloc failures as possible and give error messages

  ndb/include/ndbapi/NdbTransaction.hpp@1.47, 2007-04-11 15:21:08+02:00, tomas@whalegate.ndb.mysql.com +1 -1
    Bug#26176 NdbObjectIdMap::expand unable to expand!! mysqld got signal 11
    - try to catch as many malloc failures as possible and give error messages

  ndb/include/util/BaseString.hpp@1.9, 2007-04-11 15:21:08+02:00, tomas@whalegate.ndb.mysql.com +7 -0
    Bug#26176 NdbObjectIdMap::expand unable to expand!! mysqld got signal 11
    - try to catch as many malloc failures as possible and give error messages

  ndb/include/util/Vector.hpp@1.7, 2007-04-11 15:21:08+02:00, tomas@whalegate.ndb.mysql.com +54 -14
    Bug#26176 NdbObjectIdMap::expand unable to expand!! mysqld got signal 11
    - try to catch as many malloc failures as possible and give error messages

  ndb/src/common/util/BaseString.cpp@1.9, 2007-04-11 15:21:08+02:00, tomas@whalegate.ndb.mysql.com +132 -13
    Bug#26176 NdbObjectIdMap::expand unable to expand!! mysqld got signal 11
    - try to catch as many malloc failures as possible and give error messages

  ndb/src/ndbapi/DictCache.cpp@1.21, 2007-04-11 15:21:08+02:00, tomas@whalegate.ndb.mysql.com +11 -2
    Bug#26176 NdbObjectIdMap::expand unable to expand!! mysqld got signal 11
    - try to catch as many malloc failures as possible and give error messages

  ndb/src/ndbapi/DictCache.hpp@1.13, 2007-04-11 15:21:08+02:00, tomas@whalegate.ndb.mysql.com +1 -1
    Bug#26176 NdbObjectIdMap::expand unable to expand!! mysqld got signal 11
    - try to catch as many malloc failures as possible and give error messages

  ndb/src/ndbapi/Makefile.am@1.17, 2007-04-11 15:21:08+02:00, tomas@whalegate.ndb.mysql.com +2 -1
    Bug#26176 NdbObjectIdMap::expand unable to expand!! mysqld got signal 11
    - try to catch as many malloc failures as possible and give error messages

  ndb/src/ndbapi/Ndb.cpp@1.68, 2007-04-11 15:21:08+02:00, tomas@whalegate.ndb.mysql.com +35 -12
    Bug#26176 NdbObjectIdMap::expand unable to expand!! mysqld got signal 11
    - try to catch as many malloc failures as possible and give error messages

  ndb/src/ndbapi/NdbDictionary.cpp@1.42, 2007-04-11 15:21:08+02:00, tomas@whalegate.ndb.mysql.com +55 -25
    Bug#26176 NdbObjectIdMap::expand unable to expand!! mysqld got signal 11
    - try to catch as many malloc failures as possible and give error messages

  ndb/src/ndbapi/NdbDictionaryImpl.cpp@1.101, 2007-04-11 15:21:08+02:00, tomas@whalegate.ndb.mysql.com +208 -54
    Bug#26176 NdbObjectIdMap::expand unable to expand!! mysqld got signal 11
    - try to catch as many malloc failures as possible and give error messages

  ndb/src/ndbapi/NdbDictionaryImpl.hpp@1.43, 2007-04-11 15:21:08+02:00, tomas@whalegate.ndb.mysql.com +5 -5
    Bug#26176 NdbObjectIdMap::expand unable to expand!! mysqld got signal 11
    - try to catch as many malloc failures as possible and give error messages

  ndb/src/ndbapi/NdbImpl.hpp@1.16, 2007-04-11 15:21:08+02:00, tomas@whalegate.ndb.mysql.com +26 -8
    Bug#26176 NdbObjectIdMap::expand unable to expand!! mysqld got signal 11
    - try to catch as many malloc failures as possible and give error messages

  ndb/src/ndbapi/NdbOperation.cpp@1.19, 2007-04-11 15:21:08+02:00, tomas@whalegate.ndb.mysql.com +5 -1
    Bug#26176 NdbObjectIdMap::expand unable to expand!! mysqld got signal 11
    - try to catch as many malloc failures as possible and give error messages

  ndb/src/ndbapi/NdbRecAttr.cpp@1.34, 2007-04-11 15:21:08+02:00, tomas@whalegate.ndb.mysql.com +12 -1
    Bug#26176 NdbObjectIdMap::expand unable to expand!! mysqld got signal 11
    - try to catch as many malloc failures as possible and give error messages

  ndb/src/ndbapi/NdbReceiver.cpp@1.18, 2007-04-11 15:21:08+02:00, tomas@whalegate.ndb.mysql.com +21 -10
    Bug#26176 NdbObjectIdMap::expand unable to expand!! mysqld got signal 11
    - try to catch as many malloc failures as possible and give error messages

  ndb/src/ndbapi/NdbScanFilter.cpp@1.14, 2007-04-11 15:21:08+02:00, tomas@whalegate.ndb.mysql.com +10 -2
    Bug#26176 NdbObjectIdMap::expand unable to expand!! mysqld got signal 11
    - try to catch as many malloc failures as possible and give error messages

  ndb/src/ndbapi/NdbScanOperation.cpp@1.86, 2007-04-11 15:21:08+02:00, tomas@whalegate.ndb.mysql.com +6 -3
    Bug#26176 NdbObjectIdMap::expand unable to expand!! mysqld got signal 11
    - try to catch as many malloc failures as possible and give error messages

  ndb/src/ndbapi/NdbTransaction.cpp@1.58, 2007-04-11 15:21:08+02:00, tomas@whalegate.ndb.mysql.com +13 -1
    Bug#26176 NdbObjectIdMap::expand unable to expand!! mysqld got signal 11
    - try to catch as many malloc failures as possible and give error messages

  ndb/src/ndbapi/Ndbif.cpp@1.37, 2007-04-11 15:21:08+02:00, tomas@whalegate.ndb.mysql.com +2 -1
    Bug#26176 NdbObjectIdMap::expand unable to expand!! mysqld got signal 11
    - try to catch as many malloc failures as possible and give error messages

  ndb/src/ndbapi/Ndblist.cpp@1.20, 2007-04-11 15:21:08+02:00, tomas@whalegate.ndb.mysql.com +8 -2
    Bug#26176 NdbObjectIdMap::expand unable to expand!! mysqld got signal 11
    - try to catch as many malloc failures as possible and give error messages

  ndb/src/ndbapi/ObjectMap.cpp@1.1, 2007-04-11 15:21:09+02:00, tomas@whalegate.ndb.mysql.com +62 -0
    New BitKeeper file ``ndb/src/ndbapi/ObjectMap.cpp''

  ndb/src/ndbapi/ObjectMap.cpp@1.0, 2007-04-11 15:21:09+02:00, tomas@whalegate.ndb.mysql.com +0 -0

  ndb/src/ndbapi/ObjectMap.hpp@1.11, 2007-04-11 15:21:08+02:00, tomas@whalegate.ndb.mysql.com +5 -46
    Bug#26176 NdbObjectIdMap::expand unable to expand!! mysqld got signal 11
    - try to catch as many malloc failures as possible and give error messages

  ndb/src/ndbapi/SignalSender.cpp@1.14, 2007-04-11 15:21:08+02:00, tomas@whalegate.ndb.mysql.com +8 -2
    Bug#26176 NdbObjectIdMap::expand unable to expand!! mysqld got signal 11
    - try to catch as many malloc failures as possible and give error messages

  ndb/src/ndbapi/ndb_cluster_connection.cpp@1.41, 2007-04-11 15:21:09+02:00, tomas@whalegate.ndb.mysql.com +11 -4
    Bug#26176 NdbObjectIdMap::expand unable to expand!! mysqld got signal 11
    - try to catch as many malloc failures as possible and give error messages

  ndb/src/ndbapi/ndb_cluster_connection_impl.hpp@1.6, 2007-04-11 15:21:09+02:00, tomas@whalegate.ndb.mysql.com +1 -1
    Bug#26176 NdbObjectIdMap::expand unable to expand!! mysqld got signal 11
    - try to catch as many malloc failures as possible and give error messages

  sql/ha_ndbcluster.cc@1.308, 2007-04-11 15:21:09+02:00, tomas@whalegate.ndb.mysql.com +145 -31
    Bug#26176 NdbObjectIdMap::expand unable to expand!! mysqld got signal 11
    - try to catch as many malloc failures as possible and give error messages

ChangeSet@1.2392.136.1, 2007-04-11 13:01:11+02:00, df@pippilotta.erinye.com +1 -0
  make configure handle service pack version strings

  configure.in@1.426.1.1, 2007-04-11 13:01:10+02:00, df@pippilotta.erinye.com +1 -1
    recognize service pack version strings

ChangeSet@1.1616.2765.17, 2007-04-11 08:23:16+02:00, jonas@perch.ndb.mysql.com +1 -0
  ndb - bug#27748
    fix commit trigger on multi-update

  ndb/src/kernel/blocks/dbtup/DbtupCommit.cpp@1.3.1.2, 2007-04-11 08:23:14+02:00, jonas@perch.ndb.mysql.com +6 -0
    fix commit trigger on multi-update

ChangeSet@1.2437.1.2, 2007-04-11 01:47:42+02:00, kent@mysql.com +3 -0
  my_memmem.c:
    Back port of include change and copyright from 5.1
  Makefile.am, zlib.m4:
    Use separate libtool convenience library for the bundled
    zlib to embed into executables and shared libraries created,
    and one to install into the pkglib directory

  config/ac-macros/zlib.m4@1.11, 2007-04-11 01:46:23+02:00, kent@mysql.com +1 -1
    Use separate libtool convenience library for the bundled
    zlib to embed into executables and shared libraries created,
    and one to install into the pkglib directory

  mysys/my_memmem.c@1.3, 2007-04-11 01:47:31+02:00, kent@mysql.com +17 -1
    Back port of include change and copyright from 5.1

  zlib/Makefile.am@1.16, 2007-04-11 01:44:48+02:00, kent@mysql.com +9 -8
    Use separate libtool convenience library for the bundled
    zlib to embed into executables and shared libraries created,
    and one to install into the pkglib directory

ChangeSet@1.2430.12.1, 2007-04-10 19:08:08+03:00, gkodinov@magare.gmz +2 -0
  Bug #19372:
  Added a test case.
  The problem was fixed by the fix for bug #17379.
  The problem was that because of some conditions 
  the optimizer always preferred range or full index
  scan access methods to lookup access methods even
  when the latter were much cheaper.

  mysql-test/r/select.result@1.155, 2007-04-10 19:08:06+03:00, gkodinov@magare.gmz +9 -0
    Bug #19372: test case.
    The problem was fixed by the patch for bug #17379

  mysql-test/t/select.test@1.129, 2007-04-10 19:08:06+03:00, gkodinov@magare.gmz +13 -0
    Bug #19372: test case.
    The problem was fixed by the patch for bug #17379

ChangeSet@1.2430.11.1, 2007-04-10 16:55:48+03:00, gkodinov@magare.gmz +3 -0
  Bug #27659: 
  The optimizer transforms DISTINCT into a GROUP BY
  when possible.
  It does that by constructing the same structure
  (a list of ORDER instances) the parser makes when
  parsing GROUP BY.
  While doing that it also eliminates duplicates.
  But if a duplicate is found it doesn't advance the
  pointer to ref_pointer array, so the next 
  (and subsequent) ORDER structures point to the wrong
  element in the SELECT list.
  Fixed by advancing the pointer in ref_pointer_array
  even in the case of a duplicate.

  mysql-test/r/distinct.result@1.52, 2007-04-10 16:55:47+03:00, gkodinov@magare.gmz +14 -0
    Bug #27659: test case

  mysql-test/t/distinct.test@1.31, 2007-04-10 16:55:47+03:00, gkodinov@magare.gmz +13 -0
    Bug #27659: test case

  sql/sql_select.cc@1.508, 2007-04-10 16:55:47+03:00, gkodinov@magare.gmz +2 -3
    Bug #27659: use correct ref_pointer_array element

ChangeSet@1.2440.1.1, 2007-04-10 15:01:04+05:00, gluh@mysql.com +3 -0
  Bug#27069 set with identical elements are created(additional fix)
  issue an error in strict mode
  if enum|set column has duplicates members in 'create table'

  mysql-test/r/strict.result@1.34, 2007-04-10 15:01:02+05:00, gluh@mysql.com +5 -0
    test case

  mysql-test/t/strict.test@1.27, 2007-04-10 15:01:02+05:00, gluh@mysql.com +9 -0
    test case

  sql/sql_table.cc@1.335.1.4, 2007-04-10 15:01:02+05:00, gluh@mysql.com +19 -8
    issue an error in strict mode
    if enum|set has duplicates members 

ChangeSet@1.2430.7.5, 2007-04-07 04:14:44+02:00, kent@mysql.com +1 -0
  mysql.spec.sh:
    Removed man page for "mysql_create_system_tables"

  support-files/mysql.spec.sh@1.172, 2007-04-07 04:14:27+02:00, kent@mysql.com +4 -1
    Removed man page for "mysql_create_system_tables"

ChangeSet@1.2430.10.1, 2007-04-07 00:13:27+04:00, evgen@moonbone.local +3 -0
  Bug#27586: Wrong autoinc value assigned by LOAD DATA in the
  NO_AUTO_VALUE_ON_ZERO mode.
  
  The table->auto_increment_field_not_null variable wasn't reset after
  reading a row which may lead to inserting a wrong value to the auto-increment
  field to the following row.
  
  The table->auto_increment_field_not_null variable is reset now right after a
  row is being written in the read_fixed_length() and the read_sep_field()
  functions.
  Removed wrong setting of the table->auto_increment_field_not_null variable in
  the read_sep_field() function.

  mysql-test/r/loaddata.result@1.27, 2007-04-07 00:10:58+04:00, evgen@moonbone.local +9 -0
    Added a test case for the bug#27586: Wrong autoinc value assigned by LOAD DATA in the
    NO_AUTO_VALUE_ON_ZERO mode.

  mysql-test/t/loaddata.test@1.21, 2007-04-07 00:10:56+04:00, evgen@moonbone.local +16 -0
    Added a test case for the bug#27586: Wrong autoinc value assigned by LOAD DATA in the
    NO_AUTO_VALUE_ON_ZERO mode.

  sql/sql_load.cc@1.110.1.1, 2007-04-07 00:11:45+04:00, evgen@moonbone.local +8 -7
    Bug#27586: Wrong autoinc value assigned by LOAD DATA in the
    NO_AUTO_VALUE_ON_ZERO mode.
    The table->auto_increment_field_not_null variable is reset now right after a
    row is being written in the read_fixed_length() and the read_sep_field()
    functions.
    Remove wrong setting of the table->auto_increment_field_not_null variable in
    the read_sep_field() function.

ChangeSet@1.2434.1.2, 2007-04-06 20:21:30+04:00, anozdrin@ibm. +1 -0
  Polishing: note added.

  sql/sp_head.cc@1.240, 2007-04-06 20:21:28+04:00, anozdrin@ibm. +6 -0
    Polishing: note added.

ChangeSet@1.2434.1.1, 2007-04-06 18:56:39+04:00, anozdrin@ibm. +1 -0
  Polishing: add comments.

  sql/parse_file.cc@1.22, 2007-04-06 18:56:37+04:00, anozdrin@ibm. +13 -2
    Add comments.

ChangeSet@1.2430.7.4, 2007-04-05 16:04:31+02:00, hhunger@hh-nb.hungers +83 -0
  test of row locking.

  mysql-test/suite/row_lock/include/row_lock.inc@1.1, 2007-04-05 16:00:48+02:00, hhunger@hh-nb.hungers +83 -0
    test of row locking.

  mysql-test/suite/row_lock/include/row_lock.inc@1.0, 2007-04-05 16:00:48+02:00, hhunger@hh-nb.hungers +0 -0

  mysql-test/suite/row_lock/include/row_lock_big_tab.inc@1.1, 2007-04-05 16:00:48+02:00, hhunger@hh-nb.hungers +94 -0
    test of row locking.

  mysql-test/suite/row_lock/include/row_lock_big_tab.inc@1.0, 2007-04-05 16:00:48+02:00, hhunger@hh-nb.hungers +0 -0

  mysql-test/suite/row_lock/include/row_lock_big_tab_1.inc@1.1, 2007-04-05 16:00:48+02:00, hhunger@hh-nb.hungers +93 -0
    test of row locking.

  mysql-test/suite/row_lock/include/row_lock_big_tab_1.inc@1.0, 2007-04-05 16:00:48+02:00, hhunger@hh-nb.hungers +0 -0

  mysql-test/suite/row_lock/include/row_lock_big_tab_2.inc@1.1, 2007-04-05 16:00:48+02:00, hhunger@hh-nb.hungers +93 -0
    test of row locking.

  mysql-test/suite/row_lock/include/row_lock_big_tab_2.inc@1.0, 2007-04-05 16:00:48+02:00, hhunger@hh-nb.hungers +0 -0

  mysql-test/suite/row_lock/include/row_lock_trig.inc@1.1, 2007-04-05 16:00:48+02:00, hhunger@hh-nb.hungers +96 -0
    test of row locking.

  mysql-test/suite/row_lock/include/row_lock_trig.inc@1.0, 2007-04-05 16:00:48+02:00, hhunger@hh-nb.hungers +0 -0

  mysql-test/suite/row_lock/include/row_lock_view.inc@1.1, 2007-04-05 16:00:48+02:00, hhunger@hh-nb.hungers +89 -0
    test of row locking.

  mysql-test/suite/row_lock/include/row_lock_view.inc@1.0, 2007-04-05 16:00:48+02:00, hhunger@hh-nb.hungers +0 -0

  mysql-test/suite/row_lock/include/row_lock_view_mix.inc@1.1, 2007-04-05 16:00:48+02:00, hhunger@hh-nb.hungers +92 -0
    test of row locking.

  mysql-test/suite/row_lock/include/row_lock_view_mix.inc@1.0, 2007-04-05 16:00:48+02:00, hhunger@hh-nb.hungers +0 -0

  mysql-test/suite/row_lock/include/row_lock_view_storedp.inc@1.1, 2007-04-05 16:00:48+02:00, hhunger@hh-nb.hungers +126 -0
    test of row locking.

  mysql-test/suite/row_lock/include/row_lock_view_storedp.inc@1.0, 2007-04-05 16:00:48+02:00, hhunger@hh-nb.hungers +0 -0

  mysql-test/suite/row_lock/include/row_lock_view_trig.inc@1.1, 2007-04-05 16:00:48+02:00, hhunger@hh-nb.hungers +99 -0
    test of row locking.

  mysql-test/suite/row_lock/include/row_lock_view_trig.inc@1.0, 2007-04-05 16:00:48+02:00, hhunger@hh-nb.hungers +0 -0

  mysql-test/suite/row_lock/r/innodb_row_lock_1.result@1.1, 2007-04-05 16:00:48+02:00, hhunger@hh-nb.hungers +142 -0
    test of row locking.

  mysql-test/suite/row_lock/r/innodb_row_lock_1.result@1.0, 2007-04-05 16:00:48+02:00, hhunger@hh-nb.hungers +0 -0

  mysql-test/suite/row_lock/r/innodb_row_lock_2.result@1.1, 2007-04-05 16:00:48+02:00, hhunger@hh-nb.hungers +32 -0
    test of row locking.

  mysql-test/suite/row_lock/r/innodb_row_lock_2.result@1.0, 2007-04-05 16:00:48+02:00, hhunger@hh-nb.hungers +0 -0

  mysql-test/suite/row_lock/r/innodb_row_lock_3.result@1.1, 2007-04-05 16:00:48+02:00, hhunger@hh-nb.hungers +32 -0
    test of row locking.

  mysql-test/suite/row_lock/r/innodb_row_lock_3.result@1.0, 2007-04-05 16:00:48+02:00, hhunger@hh-nb.hungers +0 -0

  mysql-test/suite/row_lock/r/innodb_row_lock_4.result@1.1, 2007-04-05 16:00:48+02:00, hhunger@hh-nb.hungers +142 -0
    test of row locking.

  mysql-test/suite/row_lock/r/innodb_row_lock_4.result@1.0, 2007-04-05 16:00:48+02:00, hhunger@hh-nb.hungers +0 -0

  mysql-test/suite/row_lock/r/innodb_row_lock_5.result@1.1, 2007-04-05 16:00:48+02:00, hhunger@hh-nb.hungers +32 -0
    test of row locking.

  mysql-test/suite/row_lock/r/innodb_row_lock_5.result@1.0, 2007-04-05 16:00:48+02:00, hhunger@hh-nb.hungers +0 -0

  mysql-test/suite/row_lock/r/innodb_row_lock_big_tab.result@1.1, 2007-04-05 16:00:48+02:00, hhunger@hh-nb.hungers +97 -0
    test of row locking.

  mysql-test/suite/row_lock/r/innodb_row_lock_big_tab.result@1.0, 2007-04-05 16:00:48+02:00, hhunger@hh-nb.hungers +0 -0

  mysql-test/suite/row_lock/r/innodb_row_lock_big_tab_1.result@1.1, 2007-04-05 16:00:48+02:00, hhunger@hh-nb.hungers +145 -0
    test of row locking.

  mysql-test/suite/row_lock/r/innodb_row_lock_big_tab_1.result@1.0, 2007-04-05 16:00:48+02:00, hhunger@hh-nb.hungers +0 -0

  mysql-test/suite/row_lock/r/innodb_row_lock_big_tab_2.result@1.1, 2007-04-05 16:00:48+02:00, hhunger@hh-nb.hungers +113 -0
    test of row locking.

  mysql-test/suite/row_lock/r/innodb_row_lock_big_tab_2.result@1.0, 2007-04-05 16:00:48+02:00, hhunger@hh-nb.hungers +0 -0

  mysql-test/suite/row_lock/r/innodb_row_lock_trig_1.result@1.1, 2007-04-05 16:00:48+02:00, hhunger@hh-nb.hungers +151 -0
    test of row locking.

  mysql-test/suite/row_lock/r/innodb_row_lock_trig_1.result@1.0, 2007-04-05 16:00:48+02:00, hhunger@hh-nb.hungers +0 -0

  mysql-test/suite/row_lock/r/innodb_row_lock_trig_2.result@1.1, 2007-04-05 16:00:48+02:00, hhunger@hh-nb.hungers +37 -0
    test of row locking.

  mysql-test/suite/row_lock/r/innodb_row_lock_trig_2.result@1.0, 2007-04-05 16:00:48+02:00, hhunger@hh-nb.hungers +0 -0

  mysql-test/suite/row_lock/r/innodb_row_lock_view_1.result@1.1, 2007-04-05 16:00:48+02:00, hhunger@hh-nb.hungers +34 -0
    test of row locking.

  mysql-test/suite/row_lock/r/innodb_row_lock_view_1.result@1.0, 2007-04-05 16:00:48+02:00, hhunger@hh-nb.hungers +0 -0

  mysql-test/suite/row_lock/r/innodb_row_lock_view_2.result@1.1, 2007-04-05 16:00:48+02:00, hhunger@hh-nb.hungers +40 -0
    test of row locking.

  mysql-test/suite/row_lock/r/innodb_row_lock_view_2.result@1.0, 2007-04-05 16:00:48+02:00, hhunger@hh-nb.hungers +0 -0

  mysql-test/suite/row_lock/r/innodb_row_lock_view_mix_1.result@1.1, 2007-04-05 16:00:48+02:00, hhunger@hh-nb.hungers +48 -0
    test of row locking.

  mysql-test/suite/row_lock/r/innodb_row_lock_view_mix_1.result@1.0, 2007-04-05 16:00:48+02:00, hhunger@hh-nb.hungers +0 -0

  mysql-test/suite/row_lock/r/innodb_row_lock_view_mix_2.result@1.1, 2007-04-05 16:00:49+02:00, hhunger@hh-nb.hungers +40 -0
    test of row locking.

  mysql-test/suite/row_lock/r/innodb_row_lock_view_mix_2.result@1.0, 2007-04-05 16:00:49+02:00, hhunger@hh-nb.hungers +0 -0

  mysql-test/suite/row_lock/r/innodb_row_lock_view_storedp_1.result@1.1, 2007-04-05 16:00:49+02:00, hhunger@hh-nb.hungers +312 -0
    test of row locking.

  mysql-test/suite/row_lock/r/innodb_row_lock_view_storedp_1.result@1.0, 2007-04-05 16:00:49+02:00, hhunger@hh-nb.hungers +0 -0

  mysql-test/suite/row_lock/r/innodb_row_lock_view_storedp_2.result@1.1, 2007-04-05 16:00:49+02:00, hhunger@hh-nb.hungers +47 -0
    test of row locking.

  mysql-test/suite/row_lock/r/innodb_row_lock_view_storedp_2.result@1.0, 2007-04-05 16:00:49+02:00, hhunger@hh-nb.hungers +0 -0

  mysql-test/suite/row_lock/r/innodb_row_lock_view_trig_1.result@1.1, 2007-04-05 16:00:49+02:00, hhunger@hh-nb.hungers +183 -0
    test of row locking.

  mysql-test/suite/row_lock/r/innodb_row_lock_view_trig_1.result@1.0, 2007-04-05 16:00:49+02:00, hhunger@hh-nb.hungers +0 -0

  mysql-test/suite/row_lock/r/innodb_row_lock_view_trig_2.result@1.1, 2007-04-05 16:00:49+02:00, hhunger@hh-nb.hungers +38 -0
    test of row locking.

  mysql-test/suite/row_lock/r/innodb_row_lock_view_trig_2.result@1.0, 2007-04-05 16:00:49+02:00, hhunger@hh-nb.hungers +0 -0

  mysql-test/suite/row_lock/r/ndb_row_lock_1.result@1.1, 2007-04-05 16:00:49+02:00, hhunger@hh-nb.hungers +139 -0
    test of row locking.

  mysql-test/suite/row_lock/r/ndb_row_lock_1.result@1.0, 2007-04-05 16:00:49+02:00, hhunger@hh-nb.hungers +0 -0

  mysql-test/suite/row_lock/r/ndb_row_lock_2.result@1.1, 2007-04-05 16:00:49+02:00, hhunger@hh-nb.hungers +31 -0
    test of row locking.

  mysql-test/suite/row_lock/r/ndb_row_lock_2.result@1.0, 2007-04-05 16:00:49+02:00, hhunger@hh-nb.hungers +0 -0

  mysql-test/suite/row_lock/r/ndb_row_lock_3.result@1.1, 2007-04-05 16:00:49+02:00, hhunger@hh-nb.hungers +30 -0
    test of row locking.

  mysql-test/suite/row_lock/r/ndb_row_lock_3.result@1.0, 2007-04-05 16:00:49+02:00, hhunger@hh-nb.hungers +0 -0

  mysql-test/suite/row_lock/r/ndb_row_lock_4.result@1.1, 2007-04-05 16:00:49+02:00, hhunger@hh-nb.hungers +139 -0
    test of row locking.

  mysql-test/suite/row_lock/r/ndb_row_lock_4.result@1.0, 2007-04-05 16:00:49+02:00, hhunger@hh-nb.hungers +0 -0

  mysql-test/suite/row_lock/r/ndb_row_lock_5.result@1.1, 2007-04-05 16:00:49+02:00, hhunger@hh-nb.hungers +30 -0
    test of row locking.

  mysql-test/suite/row_lock/r/ndb_row_lock_5.result@1.0, 2007-04-05 16:00:49+02:00, hhunger@hh-nb.hungers +0 -0

  mysql-test/suite/row_lock/r/ndb_row_lock_big_tab.result@1.1, 2007-04-05 16:00:49+02:00, hhunger@hh-nb.hungers +177 -0
    test of row locking.

  mysql-test/suite/row_lock/r/ndb_row_lock_big_tab.result@1.0, 2007-04-05 16:00:49+02:00, hhunger@hh-nb.hungers +0 -0

  mysql-test/suite/row_lock/r/ndb_row_lock_big_tab_1.result@1.1, 2007-04-05 16:00:49+02:00, hhunger@hh-nb.hungers +357 -0
    test of row locking.

  mysql-test/suite/row_lock/r/ndb_row_lock_big_tab_1.result@1.0, 2007-04-05 16:00:49+02:00, hhunger@hh-nb.hungers +0 -0

  mysql-test/suite/row_lock/r/ndb_row_lock_big_tab_2.result@1.1, 2007-04-05 16:00:49+02:00, hhunger@hh-nb.hungers +255 -0
    test of row locking.

  mysql-test/suite/row_lock/r/ndb_row_lock_big_tab_2.result@1.0, 2007-04-05 16:00:49+02:00, hhunger@hh-nb.hungers +0 -0

  mysql-test/suite/row_lock/r/ndb_row_lock_trig_1.result@1.1, 2007-04-05 16:00:49+02:00, hhunger@hh-nb.hungers +148 -0
    test of row locking.

  mysql-test/suite/row_lock/r/ndb_row_lock_trig_1.result@1.0, 2007-04-05 16:00:49+02:00, hhunger@hh-nb.hungers +0 -0

  mysql-test/suite/row_lock/r/ndb_row_lock_trig_2.result@1.1, 2007-04-05 16:00:49+02:00, hhunger@hh-nb.hungers +35 -0
    test of row locking.

  mysql-test/suite/row_lock/r/ndb_row_lock_trig_2.result@1.0, 2007-04-05 16:00:49+02:00, hhunger@hh-nb.hungers +0 -0

  mysql-test/suite/row_lock/r/ndb_row_lock_view_1.result@1.1, 2007-04-05 16:00:49+02:00, hhunger@hh-nb.hungers +194 -0
    test of row locking.

  mysql-test/suite/row_lock/r/ndb_row_lock_view_1.result@1.0, 2007-04-05 16:00:49+02:00, hhunger@hh-nb.hungers +0 -0

  mysql-test/suite/row_lock/r/ndb_row_lock_view_2.result@1.1, 2007-04-05 16:00:49+02:00, hhunger@hh-nb.hungers +200 -0
    test of row locking.

  mysql-test/suite/row_lock/r/ndb_row_lock_view_2.result@1.0, 2007-04-05 16:00:49+02:00, hhunger@hh-nb.hungers +0 -0

  mysql-test/suite/row_lock/r/ndb_row_lock_view_mix_1.result@1.1, 2007-04-05 16:00:49+02:00, hhunger@hh-nb.hungers +169 -0
    test of row locking.

  mysql-test/suite/row_lock/r/ndb_row_lock_view_mix_1.result@1.0, 2007-04-05 16:00:49+02:00, hhunger@hh-nb.hungers +0 -0

  mysql-test/suite/row_lock/r/ndb_row_lock_view_mix_2.result@1.1, 2007-04-05 16:00:49+02:00, hhunger@hh-nb.hungers +38 -0
    test of row locking.

  mysql-test/suite/row_lock/r/ndb_row_lock_view_mix_2.result@1.0, 2007-04-05 16:00:49+02:00, hhunger@hh-nb.hungers +0 -0

  mysql-test/suite/row_lock/r/ndb_row_lock_view_storedp_1.result@1.1, 2007-04-05 16:00:49+02:00, hhunger@hh-nb.hungers +309 -0
    test of row locking.

  mysql-test/suite/row_lock/r/ndb_row_lock_view_storedp_1.result@1.0, 2007-04-05 16:00:49+02:00, hhunger@hh-nb.hungers +0 -0

  mysql-test/suite/row_lock/r/ndb_row_lock_view_storedp_2.result@1.1, 2007-04-05 16:00:49+02:00, hhunger@hh-nb.hungers +46 -0
    test of row locking.

  mysql-test/suite/row_lock/r/ndb_row_lock_view_storedp_2.result@1.0, 2007-04-05 16:00:49+02:00, hhunger@hh-nb.hungers +0 -0

  mysql-test/suite/row_lock/r/ndb_row_lock_view_trig_1.result@1.1, 2007-04-05 16:00:49+02:00, hhunger@hh-nb.hungers +180 -0
    test of row locking.

  mysql-test/suite/row_lock/r/ndb_row_lock_view_trig_1.result@1.0, 2007-04-05 16:00:49+02:00, hhunger@hh-nb.hungers +0 -0

  mysql-test/suite/row_lock/r/ndb_row_lock_view_trig_2.result@1.1, 2007-04-05 16:00:49+02:00, hhunger@hh-nb.hungers +36 -0
    test of row locking.

  mysql-test/suite/row_lock/r/ndb_row_lock_view_trig_2.result@1.0, 2007-04-05 16:00:49+02:00, hhunger@hh-nb.hungers +0 -0

  mysql-test/suite/row_lock/readme.txt@1.1, 2007-04-05 16:00:48+02:00, hhunger@hh-nb.hungers +9 -0
    test of row locking.

  mysql-test/suite/row_lock/readme.txt@1.0, 2007-04-05 16:00:48+02:00, hhunger@hh-nb.hungers +0 -0

  mysql-test/suite/row_lock/summary_of_sel_test.txt@1.1, 2007-04-05 16:00:48+02:00, hhunger@hh-nb.hungers +36 -0
    test of row locking.

  mysql-test/suite/row_lock/summary_of_sel_test.txt@1.0, 2007-04-05 16:00:48+02:00, hhunger@hh-nb.hungers +0 -0

  mysql-test/suite/row_lock/t/innodb_row_lock_1.test@1.1, 2007-04-05 16:00:49+02:00, hhunger@hh-nb.hungers +9 -0
    test of row locking.

  mysql-test/suite/row_lock/t/innodb_row_lock_1.test@1.0, 2007-04-05 16:00:49+02:00, hhunger@hh-nb.hungers +0 -0

  mysql-test/suite/row_lock/t/innodb_row_lock_2.test@1.1, 2007-04-05 16:00:49+02:00, hhunger@hh-nb.hungers +9 -0
    test of row locking.

  mysql-test/suite/row_lock/t/innodb_row_lock_2.test@1.0, 2007-04-05 16:00:49+02:00, hhunger@hh-nb.hungers +0 -0

  mysql-test/suite/row_lock/t/innodb_row_lock_3.test@1.1, 2007-04-05 16:00:49+02:00, hhunger@hh-nb.hungers +9 -0
    test of row locking.

  mysql-test/suite/row_lock/t/innodb_row_lock_3.test@1.0, 2007-04-05 16:00:49+02:00, hhunger@hh-nb.hungers +0 -0

  mysql-test/suite/row_lock/t/innodb_row_lock_4.test@1.1, 2007-04-05 16:00:49+02:00, hhunger@hh-nb.hungers +9 -0
    test of row locking.

  mysql-test/suite/row_lock/t/innodb_row_lock_4.test@1.0, 2007-04-05 16:00:49+02:00, hhunger@hh-nb.hungers +0 -0

  mysql-test/suite/row_lock/t/innodb_row_lock_5.test@1.1, 2007-04-05 16:00:49+02:00, hhunger@hh-nb.hungers +9 -0
    test of row locking.

  mysql-test/suite/row_lock/t/innodb_row_lock_5.test@1.0, 2007-04-05 16:00:49+02:00, hhunger@hh-nb.hungers +0 -0

  mysql-test/suite/row_lock/t/innodb_row_lock_big_tab.test@1.1, 2007-04-05 16:00:49+02:00, hhunger@hh-nb.hungers +9 -0
    test of row locking.

  mysql-test/suite/row_lock/t/innodb_row_lock_big_tab.test@1.0, 2007-04-05 16:00:49+02:00, hhunger@hh-nb.hungers +0 -0

  mysql-test/suite/row_lock/t/innodb_row_lock_big_tab_1.test@1.1, 2007-04-05 16:00:49+02:00, hhunger@hh-nb.hungers +10 -0
    test of row locking.

  mysql-test/suite/row_lock/t/innodb_row_lock_big_tab_1.test@1.0, 2007-04-05 16:00:49+02:00, hhunger@hh-nb.hungers +0 -0

  mysql-test/suite/row_lock/t/innodb_row_lock_big_tab_2.test@1.1, 2007-04-05 16:00:49+02:00, hhunger@hh-nb.hungers +10 -0
    test of row locking.

  mysql-test/suite/row_lock/t/innodb_row_lock_big_tab_2.test@1.0, 2007-04-05 16:00:49+02:00, hhunger@hh-nb.hungers +0 -0

  mysql-test/suite/row_lock/t/innodb_row_lock_trig_1.test@1.1, 2007-04-05 16:00:50+02:00, hhunger@hh-nb.hungers +9 -0
    test of row locking.

  mysql-test/suite/row_lock/t/innodb_row_lock_trig_1.test@1.0, 2007-04-05 16:00:50+02:00, hhunger@hh-nb.hungers +0 -0

  mysql-test/suite/row_lock/t/innodb_row_lock_trig_2.test@1.1, 2007-04-05 16:00:50+02:00, hhunger@hh-nb.hungers +9 -0
    test of row locking.

  mysql-test/suite/row_lock/t/innodb_row_lock_trig_2.test@1.0, 2007-04-05 16:00:50+02:00, hhunger@hh-nb.hungers +0 -0

  mysql-test/suite/row_lock/t/innodb_row_lock_view_1.test@1.1, 2007-04-05 16:00:50+02:00, hhunger@hh-nb.hungers +9 -0
    test of row locking.

  mysql-test/suite/row_lock/t/innodb_row_lock_view_1.test@1.0, 2007-04-05 16:00:50+02:00, hhunger@hh-nb.hungers +0 -0

  mysql-test/suite/row_lock/t/innodb_row_lock_view_2.test@1.1, 2007-04-05 16:00:50+02:00, hhunger@hh-nb.hungers +9 -0
    test of row locking.

  mysql-test/suite/row_lock/t/innodb_row_lock_view_2.test@1.0, 2007-04-05 16:00:50+02:00, hhunger@hh-nb.hungers +0 -0

  mysql-test/suite/row_lock/t/innodb_row_lock_view_mix_1.test@1.1, 2007-04-05 16:00:50+02:00, hhunger@hh-nb.hungers +9 -0
    test of row locking.

  mysql-test/suite/row_lock/t/innodb_row_lock_view_mix_1.test@1.0, 2007-04-05 16:00:50+02:00, hhunger@hh-nb.hungers +0 -0

  mysql-test/suite/row_lock/t/innodb_row_lock_view_mix_2.test@1.1, 2007-04-05 16:00:50+02:00, hhunger@hh-nb.hungers +10 -0
    test of row locking.

  mysql-test/suite/row_lock/t/innodb_row_lock_view_mix_2.test@1.0, 2007-04-05 16:00:50+02:00, hhunger@hh-nb.hungers +0 -0

  mysql-test/suite/row_lock/t/innodb_row_lock_view_storedp_1.test@1.1, 2007-04-05 16:00:50+02:00, hhunger@hh-nb.hungers +9 -0
    test of row locking.

  mysql-test/suite/row_lock/t/innodb_row_lock_view_storedp_1.test@1.0, 2007-04-05 16:00:50+02:00, hhunger@hh-nb.hungers +0 -0

  mysql-test/suite/row_lock/t/innodb_row_lock_view_storedp_2.test@1.1, 2007-04-05 16:00:50+02:00, hhunger@hh-nb.hungers +9 -0
    test of row locking.

  mysql-test/suite/row_lock/t/innodb_row_lock_view_storedp_2.test@1.0, 2007-04-05 16:00:50+02:00, hhunger@hh-nb.hungers +0 -0

  mysql-test/suite/row_lock/t/innodb_row_lock_view_trig_1.test@1.1, 2007-04-05 16:00:50+02:00, hhunger@hh-nb.hungers +9 -0
    test of row locking.

  mysql-test/suite/row_lock/t/innodb_row_lock_view_trig_1.test@1.0, 2007-04-05 16:00:50+02:00, hhunger@hh-nb.hungers +0 -0

  mysql-test/suite/row_lock/t/innodb_row_lock_view_trig_2.test@1.1, 2007-04-05 16:00:50+02:00, hhunger@hh-nb.hungers +9 -0
    test of row locking.

  mysql-test/suite/row_lock/t/innodb_row_lock_view_trig_2.test@1.0, 2007-04-05 16:00:50+02:00, hhunger@hh-nb.hungers +0 -0

  mysql-test/suite/row_lock/t/ndb_row_lock_1.test@1.1, 2007-04-05 16:00:50+02:00, hhunger@hh-nb.hungers +6 -0
    test of row locking.

  mysql-test/suite/row_lock/t/ndb_row_lock_1.test@1.0, 2007-04-05 16:00:50+02:00, hhunger@hh-nb.hungers +0 -0

  mysql-test/suite/row_lock/t/ndb_row_lock_2.test@1.1, 2007-04-05 16:00:50+02:00, hhunger@hh-nb.hungers +6 -0
    test of row locking.

  mysql-test/suite/row_lock/t/ndb_row_lock_2.test@1.0, 2007-04-05 16:00:50+02:00, hhunger@hh-nb.hungers +0 -0

  mysql-test/suite/row_lock/t/ndb_row_lock_3.test@1.1, 2007-04-05 16:00:50+02:00, hhunger@hh-nb.hungers +6 -0
    test of row locking.

  mysql-test/suite/row_lock/t/ndb_row_lock_3.test@1.0, 2007-04-05 16:00:50+02:00, hhunger@hh-nb.hungers +0 -0

  mysql-test/suite/row_lock/t/ndb_row_lock_4.test@1.1, 2007-04-05 16:00:50+02:00, hhunger@hh-nb.hungers +6 -0
    test of row locking.

  mysql-test/suite/row_lock/t/ndb_row_lock_4.test@1.0, 2007-04-05 16:00:50+02:00, hhunger@hh-nb.hungers +0 -0

  mysql-test/suite/row_lock/t/ndb_row_lock_5.test@1.1, 2007-04-05 16:00:50+02:00, hhunger@hh-nb.hungers +6 -0
    test of row locking.

  mysql-test/suite/row_lock/t/ndb_row_lock_5.test@1.0, 2007-04-05 16:00:50+02:00, hhunger@hh-nb.hungers +0 -0

  mysql-test/suite/row_lock/t/ndb_row_lock_big_tab.test@1.1, 2007-04-05 16:00:50+02:00, hhunger@hh-nb.hungers +6 -0
    test of row locking.

  mysql-test/suite/row_lock/t/ndb_row_lock_big_tab.test@1.0, 2007-04-05 16:00:50+02:00, hhunger@hh-nb.hungers +0 -0

  mysql-test/suite/row_lock/t/ndb_row_lock_big_tab_1.test@1.1, 2007-04-05 16:00:50+02:00, hhunger@hh-nb.hungers +7 -0
    test of row locking.

  mysql-test/suite/row_lock/t/ndb_row_lock_big_tab_1.test@1.0, 2007-04-05 16:00:50+02:00, hhunger@hh-nb.hungers +0 -0

  mysql-test/suite/row_lock/t/ndb_row_lock_big_tab_2.test@1.1, 2007-04-05 16:00:50+02:00, hhunger@hh-nb.hungers +7 -0
    test of row locking.

  mysql-test/suite/row_lock/t/ndb_row_lock_big_tab_2.test@1.0, 2007-04-05 16:00:50+02:00, hhunger@hh-nb.hungers +0 -0

  mysql-test/suite/row_lock/t/ndb_row_lock_trig_1.test@1.1, 2007-04-05 16:00:50+02:00, hhunger@hh-nb.hungers +6 -0
    test of row locking.

  mysql-test/suite/row_lock/t/ndb_row_lock_trig_1.test@1.0, 2007-04-05 16:00:50+02:00, hhunger@hh-nb.hungers +0 -0

  mysql-test/suite/row_lock/t/ndb_row_lock_trig_2.test@1.1, 2007-04-05 16:00:50+02:00, hhunger@hh-nb.hungers +6 -0
    test of row locking.

  mysql-test/suite/row_lock/t/ndb_row_lock_trig_2.test@1.0, 2007-04-05 16:00:50+02:00, hhunger@hh-nb.hungers +0 -0

  mysql-test/suite/row_lock/t/ndb_row_lock_view_1.test@1.1, 2007-04-05 16:00:50+02:00, hhunger@hh-nb.hungers +7 -0
    test of row locking.

  mysql-test/suite/row_lock/t/ndb_row_lock_view_1.test@1.0, 2007-04-05 16:00:50+02:00, hhunger@hh-nb.hungers +0 -0

  mysql-test/suite/row_lock/t/ndb_row_lock_view_2.test@1.1, 2007-04-05 16:00:50+02:00, hhunger@hh-nb.hungers +6 -0
    test of row locking.

  mysql-test/suite/row_lock/t/ndb_row_lock_view_2.test@1.0, 2007-04-05 16:00:50+02:00, hhunger@hh-nb.hungers +0 -0

  mysql-test/suite/row_lock/t/ndb_row_lock_view_mix_1.test@1.1, 2007-04-05 16:00:50+02:00, hhunger@hh-nb.hungers +6 -0
    test of row locking.

  mysql-test/suite/row_lock/t/ndb_row_lock_view_mix_1.test@1.0, 2007-04-05 16:00:50+02:00, hhunger@hh-nb.hungers +0 -0

  mysql-test/suite/row_lock/t/ndb_row_lock_view_mix_2.test@1.1, 2007-04-05 16:00:50+02:00, hhunger@hh-nb.hungers +6 -0
    test of row locking.

  mysql-test/suite/row_lock/t/ndb_row_lock_view_mix_2.test@1.0, 2007-04-05 16:00:50+02:00, hhunger@hh-nb.hungers +0 -0

  mysql-test/suite/row_lock/t/ndb_row_lock_view_storedp_1.test@1.1, 2007-04-05 16:00:50+02:00, hhunger@hh-nb.hungers +6 -0
    test of row locking.

  mysql-test/suite/row_lock/t/ndb_row_lock_view_storedp_1.test@1.0, 2007-04-05 16:00:50+02:00, hhunger@hh-nb.hungers +0 -0

  mysql-test/suite/row_lock/t/ndb_row_lock_view_storedp_2.test@1.1, 2007-04-05 16:00:50+02:00, hhunger@hh-nb.hungers +6 -0
    test of row locking.

  mysql-test/suite/row_lock/t/ndb_row_lock_view_storedp_2.test@1.0, 2007-04-05 16:00:50+02:00, hhunger@hh-nb.hungers +0 -0

  mysql-test/suite/row_lock/t/ndb_row_lock_view_trig_1.test@1.1, 2007-04-05 16:00:50+02:00, hhunger@hh-nb.hungers +6 -0
    test of row locking.

  mysql-test/suite/row_lock/t/ndb_row_lock_view_trig_1.test@1.0, 2007-04-05 16:00:50+02:00, hhunger@hh-nb.hungers +0 -0

  mysql-test/suite/row_lock/t/ndb_row_lock_view_trig_2.test@1.1, 2007-04-05 16:00:50+02:00, hhunger@hh-nb.hungers +6 -0
    test of row locking.

  mysql-test/suite/row_lock/t/ndb_row_lock_view_trig_2.test@1.0, 2007-04-05 16:00:50+02:00, hhunger@hh-nb.hungers +0 -0

ChangeSet@1.2430.9.2, 2007-04-05 09:16:16+02:00, tomas@whalegate.ndb.mysql.com +7 -0
  set name for ndb tools

  ndb/tools/delete_all.cpp@1.23, 2007-04-05 09:16:14+02:00, tomas@whalegate.ndb.mysql.com +1 -0
    set name for ndb tools

  ndb/tools/desc.cpp@1.25, 2007-04-05 09:16:14+02:00, tomas@whalegate.ndb.mysql.com +1 -0
    set name for ndb tools

  ndb/tools/drop_index.cpp@1.20, 2007-04-05 09:16:14+02:00, tomas@whalegate.ndb.mysql.com +1 -0
    set name for ndb tools

  ndb/tools/drop_tab.cpp@1.20, 2007-04-05 09:16:14+02:00, tomas@whalegate.ndb.mysql.com +1 -0
    set name for ndb tools

  ndb/tools/listTables.cpp@1.26, 2007-04-05 09:16:14+02:00, tomas@whalegate.ndb.mysql.com +1 -0
    set name for ndb tools

  ndb/tools/select_all.cpp@1.27, 2007-04-05 09:16:14+02:00, tomas@whalegate.ndb.mysql.com +1 -0
    set name for ndb tools

  ndb/tools/select_count.cpp@1.24, 2007-04-05 09:16:14+02:00, tomas@whalegate.ndb.mysql.com +1 -0
    set name for ndb tools

ChangeSet@1.2430.9.1, 2007-04-05 09:12:30+02:00, tomas@whalegate.ndb.mysql.com +1 -0
  Bug#27644 ndb: connecting api node/mysqld may "steal" node_id from running mysqld
  - test case workaround to avoid random failures

  mysql-test/t/ndb_autodiscover3.test@1.2, 2007-04-05 09:12:28+02:00, tomas@whalegate.ndb.mysql.com +9 -3
    Bug#27644 ndb: connecting api node/mysqld may "steal" node_id from running mysqld
    - test case workaround to avoid random failures

ChangeSet@1.2430.7.3, 2007-04-05 08:36:56+02:00, kent@mysql.com +4 -0
  zlib.m4:
    Only require the more recent zlibCompileFlags() when
    building the server, client zlib don't need it.
  Makefile.am:
    Always build the bundled zlib static only
  configure.in:
    Look for dlopen() even if --with-mysqld-ldflags constains "-static",
    as this is not the same as the flag to "ld", it just informs
    "libtool" to link static with libraries created part of the build,
    even if there exists shared versions.
  make_binary_distribution.sh:
    Real "mysqlmanager" executable might be in ".libs"

  config/ac-macros/zlib.m4@1.10, 2007-04-05 08:34:14+02:00, kent@mysql.com +11 -2
    Only require the more recent zlibCompileFlags() when
    building the server, client zlib don't need it.

  configure.in@1.435, 2007-04-05 08:24:06+02:00, kent@mysql.com +2 -2
    Look for dlopen() even if --with-mysqld-ldflags constains "-static",
    as this is not the same as the flag to "ld", it just informs
    "libtool" to link static with libraries created part of the build,
    even if there exists shared versions.

  scripts/make_binary_distribution.sh@1.125, 2007-04-05 08:35:34+02:00, kent@mysql.com +7 -1
    Real "mysqlmanager" executable might be in ".libs"

  zlib/Makefile.am@1.15, 2007-04-05 08:36:09+02:00, kent@mysql.com +2 -1
    Always build the bundled zlib static only

ChangeSet@1.1616.3011.1, 2007-04-05 08:30:16+02:00, kent@mysql.com +5 -0
  Deleted reject files accidently checked in
    configure.in.rej
    include/my_global.h.rej
    BUILD/SETUP.sh.rej
    mysys/thr_alarm.c.rej
    include/my_pthread.h.rej

  BitKeeper/deleted/.del-SETUP.sh.rej@1.2, 2007-04-05 08:28:26+02:00, kent@mysql.com +0 -0
    Delete: BUILD/SETUP.sh.rej

  BitKeeper/deleted/.del-configure.in.rej@1.2, 2007-04-05 08:28:26+02:00, kent@mysql.com +0 -0
    Delete: configure.in.rej

  BitKeeper/deleted/.del-my_global.h.rej@1.2, 2007-04-05 08:28:26+02:00, kent@mysql.com +0 -0
    Delete: include/my_global.h.rej

  BitKeeper/deleted/.del-my_pthread.h.rej@1.2, 2007-04-05 08:28:26+02:00, kent@mysql.com +0 -0
    Delete: include/my_pthread.h.rej

  BitKeeper/deleted/.del-thr_alarm.c.rej@1.2, 2007-04-05 08:28:26+02:00, kent@mysql.com +0 -0
    Delete: mysys/thr_alarm.c.rej

ChangeSet@1.2281.4.20, 2007-04-05 07:28:09+02:00, mskold@mysql.com +1 -0
  Removed compiler warnings

  sql/ha_ndbcluster.cc@1.285.1.13, 2007-04-05 07:27:44+02:00, mskold@mysql.com +2 -0
    Removed compiler warnings

ChangeSet@1.2281.4.19, 2007-04-05 06:49:43+02:00, mskold@mysql.com +1 -0
  Fixed compilation error on Windows

  sql/sql_trigger.h@1.22.3.2, 2007-04-05 06:49:12+02:00, mskold@mysql.com +1 -1
    Fixed compilation error on Windows

ChangeSet@1.2281.4.18, 2007-04-04 12:50:39+02:00, mskold@mysql.com +11 -0
  Bug #26242  UPDATE with subquery and triggers failing with cluster tables
  
  In certain cases AFTER UPDATE/DELETE triggers on NDB tables that referenced
  subject table didn't see the results of operation which caused invocation
  of those triggers. In other words AFTER trigger invoked as result of update
  (or deletion) of particular row saw version of this row before update (or
  deletion).
  
  The problem occured because NDB handler in those cases postponed actual
  update/delete operations to be able to perform them later as one batch.
  
  This fix solves the problem by disabling this optimization for particular
  operation if subject table has AFTER trigger for this operation defined.
  To achieve this we introduce two new flags for handler::extra() method:
  HA_EXTRA_DELETE_CANNOT_BATCH and HA_EXTRA_UPDATE_CANNOT_BATCH.
  These are called if there exists AFTER DELETE/UPDATE triggers during a
  statement that potentially can generate calls to delete_row()/update_row().
  This includes multi_delete/multi_update statements as well as insert statements
  that do delete/update as part of an ON DUPLICATE statement.

  include/my_base.h@1.81.1.1, 2007-04-04 12:50:30+02:00, mskold@mysql.com +9 -1
    Added HA_EXTRA_DELETE_CANNOT_BATCH and HA_EXTRA_UPDATE_CANNOT_BATCH to inform handler when batching of delete/update is not possible.

  mysql-test/r/ndb_trigger.result@1.2, 2007-04-04 12:50:30+02:00, mskold@mysql.com +171 -0
    Bug #26242  UPDATE with subquery and triggers failing with cluster tables
    ---
    Added new test cases

  mysql-test/t/ndb_trigger.test@1.2, 2007-04-04 12:50:30+02:00, mskold@mysql.com +108 -0
    Bug #26242  UPDATE with subquery and triggers failing with cluster tables
    ---
    Added new test cases

  sql/ha_ndbcluster.cc@1.285.1.12, 2007-04-04 12:50:30+02:00, mskold@mysql.com +20 -3
    Bug #26242  UPDATE with subquery and triggers failing with cluster tables: Use HA_EXTRA_DELETE_CANNOT_BATCH and HA_EXTRA_UPDATE_CANNOT_BATCH to inform handler when batching of delete/update is not possible

  sql/ha_ndbcluster.h@1.107.1.3, 2007-04-04 12:50:30+02:00, mskold@mysql.com +2 -0
    Bug #26242  UPDATE with subquery and triggers failing with cluster tables: Added member variables for handling of HA_EXTRA_DELETE_CANNOT_BATCH and HA_EXTRA_UPDATE_CANNOT_BATCH to inform handler when batching of delete/update is not possible

  sql/mysql_priv.h@1.417.2.1, 2007-04-04 12:50:31+02:00, mskold@mysql.com +2 -0
    Added new method prepare_triggers_for_insert_stmt to check if batching of delete/update must be disallowed.

  sql/sql_delete.cc@1.181.1.1, 2007-04-04 12:50:31+02:00, mskold@mysql.com +24 -0
    Use HA_EXTRA_DELETE_CANNOT_BATCH to inform handler when batching of delete is not possible

  sql/sql_insert.cc@1.205.2.1, 2007-04-04 12:50:31+02:00, mskold@mysql.com +48 -3
    Added method prepare_triggers_for_insert_stmt to check if batching of delete/update must be dissallowed.
    Use HA_EXTRA_DELETE_CANNOT_BATCH and HA_EXTRA_UPDATE_CANNOT_BATCH to inform handler
     when batching of delete/update is not possible

  sql/sql_load.cc@1.99.1.1, 2007-04-04 12:50:31+02:00, mskold@mysql.com +1 -1
    Call prepare_triggers_for_insert_stmt to check if batching of delete/update must be dissallowed and
    mark fields used by triggers for the insert statement.

  sql/sql_trigger.h@1.22.3.1, 2007-04-04 12:50:31+02:00, mskold@mysql.com +5 -0
    Added has_triggers to support what particular triggers exist on a table.

  sql/sql_update.cc@1.200.1.2, 2007-04-04 12:50:31+02:00, mskold@mysql.com +26 -0
    Use HA_EXTRA_UPDATE_CANNOT_BATCH to inform handler when batching of update is not possible

ChangeSet@1.2430.6.1, 2007-04-04 13:38:19+03:00, gkodinov@magare.gmz +2 -0
  BUG 27513: fixed left-over sql mode from a test case.

  mysql-test/r/errors.result@1.11, 2007-04-04 13:38:18+03:00, gkodinov@magare.gmz +1 -6
    BUG 27513: fixed left-over sql mode from a test case.

  mysql-test/t/errors.test@1.17, 2007-04-04 13:38:18+03:00, gkodinov@magare.gmz +1 -0
    BUG 27513: fixed left-over sql mode from a test case.

ChangeSet@1.1616.3010.2, 2007-04-03 19:45:37-07:00, igor@olga.mysql.com +2 -0
  Improved coverage for the code added to fix bug 27532.

  mysql-test/r/order_by.result@1.40.1.12, 2007-04-03 19:45:35-07:00, igor@olga.mysql.com +25 -0
    Improved coverage for the code added to fix bug 27532.

  mysql-test/t/order_by.test@1.29.1.10, 2007-04-03 19:45:35-07:00, igor@olga.mysql.com +6 -0
    Improved coverage for the code added to fix bug 27532.

ChangeSet@1.2430.5.2, 2007-04-03 17:09:41-07:00, igor@olga.mysql.com +1 -0
  Fix after manual merge

  mysql-test/r/order_by.result@1.65, 2007-04-03 17:09:39-07:00, igor@olga.mysql.com +2 -2
    Fix after manual merge

ChangeSet@1.1616.3010.1, 2007-04-03 14:32:16-07:00, igor@olga.mysql.com +4 -0
  Fixed bug #27532: wrong results with ORDER/GROUP BY queries containing
  IN/BETWEEN predicates in sorting expressions.
  Wrong results may occur when the select list contains an expression
  with IN/BETWEEN predicate that differs from a sorting expression by
  an additional NOT only.
   
  Added the method Item_func_opt_neg::eq to compare correctly expressions
  containing [NOT] IN/BETWEEN.
  The eq method inherited from the Item_func returns TRUE when comparing
  'a IN (1,2)' with 'a NOT IN (1,2)' that is not, of course, correct.  

  mysql-test/r/order_by.result@1.40.1.11, 2007-04-03 14:32:15-07:00, igor@olga.mysql.com +59 -0
    Added a test case for bug #27532.

  mysql-test/t/order_by.test@1.29.1.9, 2007-04-03 14:32:15-07:00, igor@olga.mysql.com +29 -0
    Added a test case for bug #27532.

  sql/item_cmpfunc.cc@1.111.23.17, 2007-04-03 14:32:15-07:00, igor@olga.mysql.com +20 -0
    Fixed bug #27532.
    Added the method Item_func_opt_neg::eq to compare correctly expressions
    containing [NOT] IN/BETWEEN.
    The eq method inherited from the Item_func returns TRUE when comparing
    'a IN (1,2)' with 'a NOT IN (1,2)' that is not, of course, correct.  

  sql/item_cmpfunc.h@1.73.1.49, 2007-04-03 14:32:15-07:00, igor@olga.mysql.com +1 -0
    Added the method Item_func_opt_neg::eq to compare correctly expressions
    containing [NOT] IN/BETWEEN.
    The eq method inherited from the Item_func returns TRUE when comparing
    'a IN (1,2)' with 'a NOT IN (1,2)' that is not, of course, correct.  

ChangeSet@1.2392.86.3, 2007-04-03 18:04:24+02:00, df@pippilotta.erinye.com +1 -0
  no Max rpms anymore, but a debug binary

  support-files/mysql.spec.sh@1.169.1.1, 2007-04-03 18:04:23+02:00, df@pippilotta.erinye.com +64 -115
    remove Max rpms and add a debug server

ChangeSet@1.2430.1.2, 2007-04-03 18:00:57+03:00, gkodinov@magare.gmz +2 -0
  Bug #27513: test case added to make sure this 
  crash bug doesn't reappear.

  mysql-test/r/errors.result@1.10, 2007-04-03 18:00:55+03:00, gkodinov@magare.gmz +18 -0
    Bug #27513: test case

  mysql-test/t/errors.test@1.16, 2007-04-03 18:00:55+03:00, gkodinov@magare.gmz +11 -0
    Bug #27513: test case

ChangeSet@1.2392.93.5, 2007-04-03 18:44:29+08:00, gni@dev3-221.dev.cn.tlan +4 -0
  BUG#18676 when cluster storage engine is down, misleading error message on create table with 4009.

  mysql-test/r/ndb_autodiscover.result@1.27, 2007-04-03 18:44:27+08:00, gni@dev3-221.dev.cn.tlan +1 -1
    changes ndbd error code to mysqld error code when no cluster connection

  sql/ha_ndbcluster.cc@1.299.3.1, 2007-04-03 18:44:27+08:00, gni@dev3-221.dev.cn.tlan +5 -6
    map 4009 error code to mysql not connected error

  sql/handler.cc@1.228.1.1, 2007-04-03 18:44:27+08:00, gni@dev3-221.dev.cn.tlan +4 -4
    define return codes to ha_table_exists_in_engine to something useful
      NOTE: in 5.1 this should call a handlerton method, not horrible ifdef ndb stuff

  sql/sql_table.cc@1.333.2.1, 2007-04-03 18:44:27+08:00, gni@dev3-221.dev.cn.tlan +19 -6
    clearly define what happens on create table if exits/not exists/not connected to engine

ChangeSet@1.2410.2.34, 2007-04-02 16:21:12-04:00, iggy@recycle.(none) +1 -0
  Minor test cleanup.

  mysql-test/t/mysqldump.test@1.114, 2007-04-02 16:21:10-04:00, iggy@recycle.(none) +3 -3
    Fix for failing Windows test.

ChangeSet@1.2377.51.6, 2007-04-02 18:21:05+02:00, tomas@whalegate.ndb.mysql.com +1 -0
  BUG#27560: Memory usage of mysqld grows while doing nothing
    
  The query-cache watch thread was continually allocating new thread entries on the
  THD MEM_ROOT, not freed until server exit.
    
  Fixed by using a simple array, auto-expanded as necessary.

  sql/ha_ndbcluster.cc@1.291.5.4, 2007-04-02 18:21:03+02:00, tomas@whalegate.ndb.mysql.com +25 -10
    Use a fixed array (auto-expanded as necessary) for temporary copy of open shares,
    don't keep pushing list entries on the THD mem root.

ChangeSet@1.2377.53.1, 2007-04-02 17:26:39+05:00, svoj@mysql.com +4 -0
  BUG#25729 - boolean full text search is confused by NULLs produced by
              LEFT JOIN
  Fixed that in certain situations MATCH ... AGAINST returns false hits
  for NULLs produced by LEFT JOIN when there is no fulltext index
  available.

  mysql-test/r/fulltext_left_join.result@1.15, 2007-04-02 17:26:38+05:00, svoj@mysql.com +7 -0
    A test case for BUG#25729.

  mysql-test/t/fulltext_left_join.test@1.16, 2007-04-02 17:26:38+05:00, svoj@mysql.com +11 -0
    A test case for BUG#25729.

  sql/item_func.cc@1.317.4.2, 2007-04-02 17:26:38+05:00, svoj@mysql.com +4 -4
    concat_ws(NULL) returns empty string instead of NULL. There is not much
    sense to calculate relevance for empty strings, thus return 0 immediately
    if we got NULL or empty string from concat_ws.

  sql/item_func.h@1.160.1.1, 2007-04-02 17:26:38+05:00, svoj@mysql.com +4 -4
    Item_func_match::concat renamed to concat_ws.

ChangeSet@1.2430.1.1, 2007-04-02 15:01:19+05:00, gluh@mysql.com +4 -0
  Bug#27069 set with identical elements are created
  added the check for unique elements count in SET

  mysql-test/r/type_set.result@1.14, 2007-04-02 15:01:18+05:00, gluh@mysql.com +19 -0
    test result

  mysql-test/t/type_set.test@1.11, 2007-04-02 15:01:18+05:00, gluh@mysql.com +17 -0
    test case

  sql/field.cc@1.344.1.1, 2007-04-02 15:01:18+05:00, gluh@mysql.com +0 -5
    removed the check for elements count in SET

  sql/sql_table.cc@1.335.1.2, 2007-04-02 15:01:18+05:00, gluh@mysql.com +13 -3
    added the check for unique elements count in SET

ChangeSet@1.1616.2997.5, 2007-04-02 10:39:23+02:00, msvensson@pilot.blaudden +4 -0
  Cset exclude: tsmith@siva.hindu.god|ChangeSet|20070328212513|13373

  myisam/mi_open.c@1.80.2.12, 2007-04-02 10:39:23+02:00, msvensson@pilot.blaudden +0 -0
    Exclude

  mysql-test/r/create.result@1.75.1.15, 2007-04-02 10:39:23+02:00, msvensson@pilot.blaudden +0 -0
    Exclude

  mysql-test/t/create.test@1.48.1.15, 2007-04-02 10:39:23+02:00, msvensson@pilot.blaudden +0 -0
    Exclude

  sql/table.cc@1.111.4.13, 2007-04-02 10:39:23+02:00, msvensson@pilot.blaudden +0 -0
    Exclude

ChangeSet@1.2410.2.32, 2007-04-02 10:17:29+02:00, msvensson@pilot.blaudden +1 -0
  Fix spelling error

  mysql-test/mysql-test-run.pl@1.211.1.8, 2007-04-02 10:17:27+02:00, msvensson@pilot.blaudden +1 -1
    Fix spelling error

ChangeSet@1.2410.2.31, 2007-04-02 10:14:45+02:00, msvensson@pilot.blaudden +1 -0
  Bug#27049 Race condition in test mysqlbinlog.test
  Remove the setting of --local-load parameter for mysqlbinlog and leave that to the testcases
  to decide what params to use.

  mysql-test/mysql-test-run.pl@1.211.1.7, 2007-04-02 10:14:44+02:00, msvensson@pilot.blaudden +1 -1
    Remove the setting of --local-load parameter for mysqlbinlog and leave that to the testcases
    to decide what params to use.

ChangeSet@1.2216.71.59, 2007-04-02 09:07:15+02:00, jonas@perch.ndb.mysql.com +1 -0
  ndb - bug#27581
    make sure not to leave partially initialized pagerage-records

  ndb/src/kernel/blocks/dbtup/DbtupPageMap.cpp@1.3.1.1, 2007-04-02 09:07:14+02:00, jonas@perch.ndb.mysql.com +7 -0
    make sure not to leave partially initialized pagerage-records

ChangeSet@1.2216.71.58, 2007-04-02 08:36:00+02:00, jonas@perch.ndb.mysql.com +1 -0
  ndb - fix bug in my.cnf config handling
    put64 for 64-bit variables

  ndb/src/mgmsrv/InitConfigFileParser.cpp@1.26.2.2, 2007-04-02 08:35:59+02:00, jonas@perch.ndb.mysql.com +1 -1
    put64

ChangeSet@1.2410.2.30, 2007-03-31 17:18:03+02:00, msvensson@pilot.blaudden +2 -0
  Add correct replace

  mysql-test/r/mysqlbinlog.result@1.34, 2007-03-31 17:18:01+02:00, msvensson@pilot.blaudden +7 -7
    Add correct replace

  mysql-test/t/mysqlbinlog.test@1.46, 2007-03-31 17:18:02+02:00, msvensson@pilot.blaudden +1 -1
    Add correct replace

ChangeSet@1.2410.2.29, 2007-03-31 15:07:48+02:00, msvensson@pilot.blaudden +1 -0
  Bug#27049 Race condition in test mysqlbinlog.test
   - Add --local-load option to avoidthat the load data file requested
     by mysqlbinlog end up in local var/tmp dir and not in system global
     tmpdir

  mysql-test/t/mysqlbinlog.test@1.45, 2007-03-31 15:07:47+02:00, msvensson@pilot.blaudden +1 -1
    Add --local-load option to avoidthat the load data file requested
    by mysqlbinlog end up in local var/tmp dir and not in system global
    tmpdir

ChangeSet@1.2425.1.2, 2007-03-31 00:23:03-07:00, igor@olga.mysql.com +3 -0
  Fixed bug #27154: memory corruption when using row equalities in where
  conditions.
  When allocating memory for KEY_FIELD/SARGABLE_PARAM structures the
  function update_ref_and_keys did not take into account the fact that
  a single row equality could be replaced by several simple equalities.
  Fixed by adjusting the counter cond_count accordingly for each subquery
  when performing substitution of a row equality for simple equalities. 
   

  mysql-test/r/row.result@1.25, 2007-03-31 00:23:00-07:00, igor@olga.mysql.com +13 -0
    Added a test case for bug #27154.

  mysql-test/t/row.test@1.22, 2007-03-31 00:23:00-07:00, igor@olga.mysql.com +17 -0
    Added a test case for bug #27154.

  sql/sql_select.cc@1.506, 2007-03-31 00:23:00-07:00, igor@olga.mysql.com +30 -15
    Fixed bug #27154: memory corruption when using row equalities in where
    conditions.
    When allocating memory for KEY_FIELD/SARGABLE_PARAM structures the
    function update_ref_and_keys did not take into account the fact that
    a single row equality could be replaced by several simple equalities.
    Fixed by adjusting the counter cond_count accordingly for each subquery
    when performing substitution of a row equality for simple equalities. 
     

ChangeSet@1.1616.3007.6, 2007-03-31 00:29:18+04:00, sergefp@mysql.com +3 -0
  BUG#26624: high mem usage (crash) in range optimizer
  Pushbuild fixes: 
   - Make MAX_SEL_ARGS smaller (even 16K records_in_range() calls is 
     more than it makes sense to do in typical cases)
   - Don't call sel_arg->test_use_count() if we've already allocated 
     more than MAX_SEL_ARGs elements. The test will succeed but will take
     too much time for the test suite (and not provide much value).

  mysql-test/r/range.result@1.19.3.12, 2007-03-31 00:29:16+04:00, sergefp@mysql.com +130 -17
    BUG#26624: high mem usage (crash) in range optimizer
    Pushbuild fixes: make the test go faster

  mysql-test/t/range.test@1.12.2.15, 2007-03-31 00:29:16+04:00, sergefp@mysql.com +130 -19
    BUG#26624: high mem usage (crash) in range optimizer
    Pushbuild fixes: make the test go faster

  sql/opt_range.cc@1.98.2.55, 2007-03-31 00:29:16+04:00, sergefp@mysql.com +5 -3
    BUG#26624: high mem usage (crash) in range optimizer
    Pushbuild fixes: 
     - Make MAX_SEL_ARGS smaller (even 16K records_in_range() calls is 
       more than it makes sense to do in typical cases)
     - Don't call sel_arg->test_use_count() if we've already allocated 
       more than MAX_SEL_ARGs elements. The test will succeed but will take
       too much time for the test suite (and not provide much value).

ChangeSet@1.2377.46.2, 2007-03-30 15:01:03+00:00, lzhou@dev3-63.(none) +1 -0
  BUG#24793 Add SO_KEEPALIVE socket option to avoid cluster nodes keeping dead connections forever.

  ndb/src/common/transporter/TCP_Transporter.cpp@1.10.1.2, 2007-03-30 15:00:59+00:00, lzhou@dev3-63.(none) +7 -0
    Add SO_KEEPALIVE socket option

ChangeSet@1.2410.2.28, 2007-03-30 16:43:15+02:00, msvensson@shellback.(none) +2 -0
  Cset exclude: msvensson@shellback.(none)|ChangeSet|20070330134336|02280

  mysql-test/lib/mtr_process.pl@1.55, 2007-03-30 16:43:14+02:00, msvensson@shellback.(none) +0 -0
    Exclude

  mysql-test/mysql-test-run.pl@1.211.1.6, 2007-03-30 16:43:14+02:00, msvensson@shellback.(none) +0 -0
    Exclude

ChangeSet@1.2410.1.14, 2007-03-30 18:13:33+04:00, evgen@sunlight.local +9 -0
  Bug#23233: 0 as LAST_INSERT_ID() after INSERT .. ON DUPLICATE in the 
  NO_AUTO_VALUE_ON_ZERO mode.
  
  In the NO_AUTO_VALUE_ON_ZERO mode the table->auto_increment_field_not_null
  variable is used to indicate that a non-NULL value was specified by the user
  for an auto_increment column. When an INSERT .. ON DUPLICATE updates the
  auto_increment field this variable is set to true and stays unchanged for the
  next insert operation. This makes the next inserted row sometimes wrongly have
  0 as the value of the auto_increment field.
  
  Now the fill_record() function resets the table->auto_increment_field_not_null
  variable before filling the record.
  The table->auto_increment_field_not_null variable is also reset by the
  open_table() function for a case if we missed some auto_increment_field_not_null
  handling bug.
  Now the table->auto_increment_field_not_null is reset at the end of the
  mysql_load() function.
  
  Reset the table->auto_increment_field_not_null variable after each
  write_row() call in the copy_data_between_tables() function.
  
  

  mysql-test/r/insert_update.result@1.24, 2007-03-30 18:11:59+04:00, evgen@sunlight.local +78 -0
    Added the test case for the bug#23233: 0 as LAST_INSERT_ID() after
    INSERT .. ON DUPLICATE in the NO_AUTO_VALUE_ON_ZERO mode.

  mysql-test/t/insert_update.test@1.24, 2007-03-30 18:12:01+04:00, evgen@sunlight.local +52 -0
    Added the test case for the bug#23233: 0 as LAST_INSERT_ID() after
    INSERT .. ON DUPLICATE in the NO_AUTO_VALUE_ON_ZERO mode.

  sql/field_conv.cc@1.63, 2007-03-30 18:08:54+04:00, evgen@sunlight.local +1 -1
    Bug#23233: 0 as LAST_INSERT_ID() after INSERT .. ON DUPLICATE in the 
    NO_AUTO_VALUE_ON_ZERO mode.
    A comment is corrected.

  sql/handler.cc@1.230, 2007-03-30 18:09:20+04:00, evgen@sunlight.local +1 -5
    Bug#23233: 0 as LAST_INSERT_ID() after INSERT .. ON DUPLICATE in the 
    NO_AUTO_VALUE_ON_ZERO mode.
    Now the handler::update_auto_increment() function doesn't reset the
    table->auto_increment_field_not_null variable as it is done in the
    fill_record() function.

  sql/sql_base.cc@1.374, 2007-03-30 18:09:27+04:00, evgen@sunlight.local +62 -5
    Bug#23233: 0 as LAST_INSERT_ID() after INSERT .. ON DUPLICATE in the 
    NO_AUTO_VALUE_ON_ZERO mode.
    Now the fill_record() function resets the table->auto_increment_field_not_null
    variable before filling the record.
    The table->auto_increment_field_not_null variable is also reset by the
    open_table() function for a case if we missed some auto_increment_field_not_null
    handling bug.

  sql/sql_insert.cc@1.228, 2007-03-30 18:09:32+04:00, evgen@sunlight.local +2 -0
    Bug#23233: 0 as LAST_INSERT_ID() after INSERT .. ON DUPLICATE in the
    NO_AUTO_VALUE_ON_ZERO mode.
    Now the the table->auto_increment_field_not_null is reset at the end of the
    mysql_insert() an in the select_insert class destructor.

  sql/sql_load.cc@1.110, 2007-03-30 18:09:33+04:00, evgen@sunlight.local +1 -2
    Bug#23233: 0 as LAST_INSERT_ID() after INSERT .. ON DUPLICATE in the 
    NO_AUTO_VALUE_ON_ZERO mode.
    Now the table->auto_increment_field_not_null is reset at the end of the
    mysql_load() function.

  sql/sql_table.cc@1.335.1.1, 2007-03-30 18:09:34+04:00, evgen@sunlight.local +3 -1
    Bug#23233: 0 as LAST_INSERT_ID() after INSERT .. ON DUPLICATE in the
    NO_AUTO_VALUE_ON_ZERO mode.
    Reset the table->auto_increment_field_not_null variable after each
    write_row() call in the copy_data_between_tables() function.

  sql/table.h@1.139.1.1, 2007-03-30 18:09:35+04:00, evgen@sunlight.local +5 -0
    Bug#23233: 0 as LAST_INSERT_ID() after INSERT .. ON DUPLICATE in the
    NO_AUTO_VALUE_ON_ZERO mode.
    A comment added.

ChangeSet@1.2410.13.6, 2007-03-30 13:00:21+05:00, svoj@mysql.com +6 -0
  BUG#26138 - REPAIR TABLE with option USE_FRM erases all records in
              ARCHIVE table
  ARCHIVE table was truncated by REPAIR TABLE ... USE_FRM statement.
  The table handler returned its file name extensions in a wrong order.
  REPAIR TABLE believed it has to use the meta file to create a new table
  from it.
  
  With the fixed order, REPAIR TABLE does now use the data file to create
  a new table. So REPAIR TABLE ... USE_FRM works well with ARCHIVE engine
  now.
  
  This issue affects 5.0 only, since in 5.1 ARCHIVE engine stores meta
  information and data in the same file.

  mysql-test/r/archive.result@1.17, 2007-03-30 13:00:19+05:00, svoj@mysql.com +9 -0
    A test case for bug#26138.

  mysql-test/t/archive.test@1.18, 2007-03-30 13:00:20+05:00, svoj@mysql.com +10 -0
    A test case for bug#26138.

  sql/examples/ha_example.cc@1.23, 2007-03-30 13:00:20+05:00, svoj@mysql.com +6 -0
    Added a comment.

  sql/ha_archive.cc@1.84, 2007-03-30 13:00:20+05:00, svoj@mysql.com +1 -1
    First element of engine file name extentions array should be meta/index
    file extention. Second element - data file extention. This is true
    for engines that have separate meta/index file and data file.
    
    Reoder ha_archive_exts elements to meet described above requirement.

  sql/handler.h@1.183, 2007-03-30 13:00:20+05:00, svoj@mysql.com +11 -0
    Added a comment.

  sql/sql_table.cc@1.336, 2007-03-30 13:00:20+05:00, svoj@mysql.com +3 -1
    Added a comment.

ChangeSet@1.2410.26.1, 2007-03-29 19:19:31+03:00, gkodinov@magare.gmz +4 -0
  Bug #26815:
   When creating a temporary table the concise column type
   of a string expression is decided based on its length:
   - if its length is under 512 it is stored as either 
     varchar or char.
   - otherwise it is stored as a BLOB.
   
   There is a flag (convert_blob_length) to create_tmp_field 
   that, when >0 allows to force creation of a varchar if the
   max blob length is under convert_blob_length.
   However it must be verified that convert_blob_length 
   (settable through a SQL option in some cases) is 
   under the maximum that can be stored in a varchar column.
   While performing that check for expressions in 
   create_tmp_field_from_item the max length of the blob was
   used instead. This causes blob columns to be created in the
   heap temp table used by GROUP_CONCAT (where blobs must not
   be created in the temp table because of the constant 
   convert_blob_length that is passed to create_tmp_field() ).
   And since these blob columns are not expected in that place
   we get wrong results.
   Fixed by checking that the value of the flag variable is 
   in the limits that fit into VARCHAR instead of the max length
   of the blob column.

  mysql-test/r/func_gconcat.result@1.66.1.1, 2007-03-29 19:19:30+03:00, gkodinov@magare.gmz +10 -0
    Bug #26815: test case

  mysql-test/t/func_gconcat.test@1.53.1.1, 2007-03-29 19:19:30+03:00, gkodinov@magare.gmz +11 -1
    Bug #26815: test case

  sql/item_sum.cc@1.201.2.1, 2007-03-29 19:19:30+03:00, gkodinov@magare.gmz +1 -2
    Bug #26815: wrong length was checked

  sql/sql_select.cc@1.502.2.1, 2007-03-29 19:19:30+03:00, gkodinov@magare.gmz +1 -2
    Bug #26815: wrong length was checked

ChangeSet@1.2410.2.24, 2007-03-29 14:21:45+02:00, msvensson@pilot.blaudden +1 -0
  Update test result after merge

  mysql-test/r/rpl_ignore_table.result@1.4, 2007-03-29 14:21:44+02:00, msvensson@pilot.blaudden +4 -0
    Update test result after merge

ChangeSet@1.1616.2997.3, 2007-03-29 14:12:32+02:00, msvensson@pilot.blaudden +3 -0
  Bug#25482 GRANT statements are not replicated if you use "replicate-ignore-table"
   - GRANT and REVOKE statments didn't have the "updating" flag set and
     thus statements with a table specified would not replicate if
     slave filtering rules where turned on.
     For example "GRANT ... ON test.t1 TO ..." would not replicate.

  mysql-test/r/rpl_ignore_table.result@1.1.1.1, 2007-03-29 14:12:31+02:00, msvensson@pilot.blaudden +103 -0
    Add test results

  mysql-test/t/rpl_ignore_table.test@1.1.1.1, 2007-03-29 14:12:31+02:00, msvensson@pilot.blaudden +98 -0
    Add tests

  sql/sql_yacc.yy@1.203.1.201, 2007-03-29 14:12:31+02:00, msvensson@pilot.blaudden +2 -1
    Pass option TL_OPTION_UPDATING to 'add_table_to_list' when parsing a
    GRANT or REVOKE and a table specifier is found. This will set the
    property "updating" on the table and thus the slave filtering rules will 
    be applied.
    
    Without setting updating the statement will be not
    replicated - since "it's not updating anything" - an optimization
    to quickly skip SELECT's and similar.

ChangeSet@1.2410.2.16, 2007-03-29 11:31:50+02:00, msvensson@pilot.blaudden +2 -0
  Make the script detect --default-storage-engine=x and
  mark the test as requiring that storage engine(if we need to do that)
  Make --ndb and --with-ndbcluster and alias for
  --mysqld=--default-storage-engine=ndbcluster

  mysql-test/lib/mtr_cases.pl@1.37, 2007-03-29 11:31:48+02:00, msvensson@pilot.blaudden +11 -0
    Make the script detect --default-storage-engine=x and
    mark the test as requiring that storage engine(if we need to do that)
    Make --ndb and --with-ndbcluster and alias for
    --mysqld=--default-storage-engine=ndbcluster

  mysql-test/mysql-test-run.pl@1.211.1.4, 2007-03-29 11:31:48+02:00, msvensson@pilot.blaudden +23 -6
    Make the script detect --default-storage-engine=x and
    mark the test as requiring that storage engine(if we need to do that)
    Make --ndb and --with-ndbcluster and alias for
    --mysqld=--default-storage-engine=ndbcluster

ChangeSet@1.2410.21.2, 2007-03-29 11:20:08+02:00, tsmith@quadxeon.mysql.com +5 -0
  gis_generic test cases:
    Revert test case to NOT define any keys; the NDB warning can be handled, and ARCHIVE does not allow indexes

  mysql-test/include/gis_generic.inc@1.8, 2007-03-29 11:19:16+02:00, tsmith@quadxeon.mysql.com +22 -24
    Revert test case to NOT define any keys; the NDB warning can be handled, and ARCHIVE does not allow indexes

  mysql-test/r/archive_gis.result@1.8, 2007-03-29 11:19:17+02:00, tsmith@quadxeon.mysql.com +16 -16
    Revert test case to NOT define any keys; the NDB warning can be handled, and ARCHIVE does not allow indexes

  mysql-test/r/bdb_gis.result@1.8, 2007-03-29 11:19:17+02:00, tsmith@quadxeon.mysql.com +16 -16
    Revert test case to NOT define any keys; the NDB warning can be handled, and ARCHIVE does not allow indexes

  mysql-test/r/innodb_gis.result@1.8, 2007-03-29 11:19:17+02:00, tsmith@quadxeon.mysql.com +16 -16
    Revert test case to NOT define any keys; the NDB warning can be handled, and ARCHIVE does not allow indexes

  mysql-test/r/ndb_gis.result@1.9, 2007-03-29 11:19:17+02:00, tsmith@quadxeon.mysql.com +32 -32
    Revert test case to NOT define any keys; the NDB warning can be handled, and ARCHIVE does not allow indexes

ChangeSet@1.1616.3007.5, 2007-03-29 10:27:58+04:00, sergefp@mysql.com +1 -0
  BUG#26624: high mem usage (crash) in range optimizer
   - Post-review fixes

  sql/opt_range.cc@1.98.2.54, 2007-03-29 10:27:56+04:00, sergefp@mysql.com +15 -14
    BUG#26624: high mem usage (crash) in range optimizer
     - Post-review fixes

ChangeSet@1.2392.105.5, 2007-03-29 10:32:38+05:00, bar@mysql.com +1 -0
  Code layout fix for bug N 27079
  Thanks to Gluh for suggestion.

  strings/ctype-uca.c@1.45, 2007-03-29 10:32:35+05:00, bar@mysql.com +16 -17
    Code layout fix for bug N 27079
    Thanks to Gluh for suggestion.

ChangeSet@1.2410.19.1, 2007-03-28 22:41:21-06:00, tsmith@siva.hindu.god +3 -0
  Apply innodb-5.0-ss1372 snapshot
  
  Bug #27381: InnoDB exits when attempting to rename table to non-existant database
    Fix Bug#27381 by calling os_file_handle_error_no_exit() instead of
    os_file_handle_error().

  innobase/dict/dict0dict.c@1.84, 2007-03-28 22:41:16-06:00, tsmith@siva.hindu.god +2 -1
    Apply innodb-5.0-ss1372 snapshot
    
    Revision r1351:
    branches/5.0: Merge r1350 from trunk:
    
    Lock the data dictionary during rollback.  This removes the rare
    debug assertion failure ut_ad(mutex_own(&(dict_sys->mutex))) in
    dict_table_get_on_id() after the rollback following crash recovery.

  innobase/os/os0file.c@1.118, 2007-03-28 22:41:16-06:00, tsmith@siva.hindu.god +10 -10
    Apply innodb-5.0-ss1372 snapshot
    
    Revision r1354:
    branches/5.0: Merge r1352 from trunk:
    (also make indentation the same as in 5.1 to ease further merges)
    
    Fix typo in comment in os/os0file.c
    
    
    
    Revision r1370:
    branches/5.0: Merge r1366 from trunk:
    
    Fix Bug#27381 by calling os_file_handle_error_no_exit() instead of
    os_file_handle_error().

  innobase/row/row0undo.c@1.15, 2007-03-28 22:41:16-06:00, tsmith@siva.hindu.god +11 -11
    Apply innodb-5.0-ss1372 snapshot
    
    Revision r1351:
    branches/5.0: Merge r1350 from trunk:
    
    Lock the data dictionary during rollback.  This removes the rare
    debug assertion failure ut_ad(mutex_own(&(dict_sys->mutex))) in
    dict_table_get_on_id() after the rollback following crash recovery.

ChangeSet@1.2392.135.1, 2007-03-29 09:08:30+05:00, ramil@mysql.com +7 -0
  Fix for bugs
  #27176: Assigning a string to an year column has unexpected results
  #26359: Strings becoming truncated and converted to numbers under STRICT mode
  
  Problems: 
  1. storing a string to an integer field we don't check 
     if strntoull10rnd() returns MY_ERRNO_EDOM error.
     Fix: check for MY_ERRNO_EDOM.
  2. storing a string to an year field we use my_strntol() function.
     Fix: use strntoull10rnd() instead.

  mysql-test/r/strict.result@1.31.1.1, 2007-03-29 09:08:29+05:00, ramil@mysql.com +41 -0
    Fix for bugs
    #27176: Assigning a string to an year column has unexpected results
    #26359: Strings becoming truncated and converted to numbers under STRICT mode
      - test result.

  mysql-test/r/type_date.result@1.16, 2007-03-29 09:08:29+05:00, ramil@mysql.com +1 -1
    Fix for bugs
    #27176: Assigning a string to an year column has unexpected results
    #26359: Strings becoming truncated and converted to numbers under STRICT mode
      - test result.

  mysql-test/r/type_year.result@1.8, 2007-03-29 09:08:29+05:00, ramil@mysql.com +12 -0
    Fix for bugs
    #27176: Assigning a string to an year column has unexpected results
    #26359: Strings becoming truncated and converted to numbers under STRICT mode
      - test result.

  mysql-test/t/strict.test@1.24.1.1, 2007-03-29 09:08:29+05:00, ramil@mysql.com +50 -0
    Fix for bugs
    #27176: Assigning a string to an year column has unexpected results
    #26359: Strings becoming truncated and converted to numbers under STRICT mode
      - test case.

  mysql-test/t/type_year.test@1.8, 2007-03-29 09:08:29+05:00, ramil@mysql.com +9 -1
    Fix for bugs
    #27176: Assigning a string to an year column has unexpected results
    #26359: Strings becoming truncated and converted to numbers under STRICT mode

  sql/field.cc@1.342.1.1, 2007-03-29 09:08:29+05:00, ramil@mysql.com +141 -222
    Fix for bugs
    #27176: Assigning a string to an year column has unexpected results
    #26359: Strings becoming truncated and converted to numbers under STRICT mode
      - Field_num::get_int() method introduced. It converts a string to integer
        then check errors and bounds.
      - similar Field_tiny::store(const char...),  Field_short::store(const char...),
        Field_medium::store(const char...), Field_long::store(const char...)
        rewritten, now they just call Field_num::get_int() then store value returned.
      - Field_num::check_int() simplified.
      - Field_year::store(const char...) now uses strntoull10rnd() and properly checks
        errors returned.

  sql/field.h@1.196.2.1, 2007-03-29 09:08:29+05:00, ramil@mysql.com +5 -2
    Fix for bugs
    #27176: Assigning a string to an year column has unexpected results
    #26359: Strings becoming truncated and converted to numbers under STRICT mode
     - check_int() moved to Field_num.
     - get_int() introduced.

ChangeSet@1.2410.18.6, 2007-03-28 19:49:30-06:00, tsmith@siva.hindu.god +1 -0
  Fix warning on Windows

  sql/log.cc@1.209, 2007-03-28 19:49:25-06:00, tsmith@siva.hindu.god +2 -2
    Change print_buffer_to_nt_eventlog() to take size_t instead of int/uint for buffer sizes

ChangeSet@1.2410.18.5, 2007-03-28 19:39:43-06:00, tsmith@siva.hindu.god +5 -0
  Update test for bug #24563 (MBROverlaps does not seem to function propertly.); ARCHIVE doesn't support AUTO_INCREMENT, so specify PK values explicitly

  mysql-test/include/gis_generic.inc@1.7, 2007-03-28 19:39:38-06:00, tsmith@siva.hindu.god +24 -23
    Update test for bug #24563 (MBROverlaps does not seem to function propertly.); ARCHIVE doesn't support AUTO_INCREMENT, so specify PK values explicitly

  mysql-test/r/archive_gis.result@1.7, 2007-03-28 19:39:38-06:00, tsmith@siva.hindu.god +16 -16
    update test result

  mysql-test/r/bdb_gis.result@1.7, 2007-03-28 19:39:38-06:00, tsmith@siva.hindu.god +16 -16
    update test result

  mysql-test/r/innodb_gis.result@1.7, 2007-03-28 19:39:38-06:00, tsmith@siva.hindu.god +16 -16
    update test result

  mysql-test/r/ndb_gis.result@1.8, 2007-03-28 19:39:38-06:00, tsmith@siva.hindu.god +32 -32
    update test result

ChangeSet@1.2410.18.4, 2007-03-28 17:50:06-06:00, tsmith@siva.hindu.god +1 -0
  Remove warning when compiling libmysqld/log.cc

  sql/log.cc@1.208, 2007-03-28 17:50:01-06:00, tsmith@siva.hindu.god +31 -31
    define print_buffer_to_file only ifdef EMBEDDED_LIBRARY, to avoid "defined but not used" warning

ChangeSet@1.2410.18.3, 2007-03-28 17:40:42-06:00, tsmith@siva.hindu.god +5 -0
  Update test for bug #24563 (MBROverlaps does not seem to function propertly.):
  - Add primary key to test table, so NDB with binlog doesn't complain
  - Add extra results for bdb_gis.result

  mysql-test/include/gis_generic.inc@1.6, 2007-03-28 17:40:37-06:00, tsmith@siva.hindu.god +17 -16
    Update test for bug #24563 (MBROverlaps does not seem to function propertly.):
    - Add primary key to test table, so NDB with binlog doesn't complain

  mysql-test/r/archive_gis.result@1.6, 2007-03-28 17:40:37-06:00, tsmith@siva.hindu.god +16 -16
    update test results

  mysql-test/r/bdb_gis.result@1.6, 2007-03-28 17:40:37-06:00, tsmith@siva.hindu.god +41 -16
    update test results

  mysql-test/r/innodb_gis.result@1.6, 2007-03-28 17:40:37-06:00, tsmith@siva.hindu.god +16 -16
    update test results

  mysql-test/r/ndb_gis.result@1.7, 2007-03-28 17:40:37-06:00, tsmith@siva.hindu.god +32 -32
    update test results

ChangeSet@1.2410.5.7, 2007-03-28 23:00:50+02:00, kent@mysql.com +5 -0
  configure.in:
    Don't install ndb man pages if no ndb configured
  config-win.h, CMakeLists.txt, README, configure.js:
    Removed Cybozu patches

  CMakeLists.txt@1.7, 2007-03-28 23:00:25+02:00, kent@mysql.com +0 -3
    Removed Cybozu patches

  configure.in@1.434, 2007-03-28 14:55:42+02:00, kent@mysql.com +9 -3
    Don't install ndb man pages if no ndb configured

  include/config-win.h@1.85, 2007-03-28 23:00:25+02:00, kent@mysql.com +0 -14
    Removed Cybozu patches

  win/README@1.3, 2007-03-28 23:00:25+02:00, kent@mysql.com +0 -1
    Removed Cybozu patches

  win/configure.js@1.4, 2007-03-28 23:00:25+02:00, kent@mysql.com +0 -1
    Removed Cybozu patches

ChangeSet@1.2410.17.1, 2007-03-28 19:10:18+02:00, msvensson@pilot.blaudden +1 -0
  Import yaSSL

  extra/yassl/src/ssl.cpp@1.30, 2007-03-28 18:28:29+02:00, msvensson@pilot.blaudden +3 -0
    Import patch yassl.diff

ChangeSet@1.1616.3008.1, 2007-03-28 20:16:01+04:00, sergefp@mysql.com +3 -0
  BUG#26624: high mem usage (crash) in range optimizer
  - Added PARAM::alloced_sel_args where we count the # of SEL_ARGs
    created by SEL_ARG tree cloning operations.
  - Made the range analyzer to shortcut and not do any more cloning 
    if we've already created MAX_SEL_ARGS SEL_ARG objects in cloning.
  - Added comments about space complexity of SEL_ARG-graph 
    representation.

  mysql-test/r/range.result@1.19.3.11, 2007-03-28 20:15:59+04:00, sergefp@mysql.com +28 -0
    BUG#26624: Testcase

  mysql-test/t/range.test@1.12.2.14, 2007-03-28 20:15:59+04:00, sergefp@mysql.com +32 -0
    BUG#26624: Testcase

  sql/opt_range.cc@1.98.2.53, 2007-03-28 20:15:59+04:00, sergefp@mysql.com +131 -31
    BUG#26624: high mem usage (crash) in range optimizer
    - Added PARAM::alloced_sel_args where we count the # of SEL_ARGs
      created by SEL_ARG tree cloning operations.
    - Made the range analyzer to shortcut and not do any more cloning 
      if we've already created MAX_SEL_ARGS SEL_ARG objects in cloning.
    - Added comments about space complexity of SEL_ARG-graph 
      representation.

ChangeSet@1.2392.99.4, 2007-03-28 21:09:16+05:00, svoj@mysql.com +1 -0
  BUG#25521 - optimize table, delete, show table status leads to table
              losing it's .MYD
  
  When OPTIMIZE TABLE is completed it attempts to rename temporary
  file to original name. This step may fail on windows when a file
  is opened. As a result data file might be deleted and optimized
  copy of file (table_name.MYD) remains.
  
  This situation is handled properly by my_delete_allow_opened, so
  use it instead of my_delete when attempting to rename a file on
  windows.
  
  No suitable test case for this bug.

  mysys/my_redel.c@1.12, 2007-03-28 21:09:14+05:00, svoj@mysql.com +1 -1
    Attempting to delete an opened file and to immediately create
    a new one with the same name may result in my_redel failure on
    windows. It may fail because file is not deleted until it is
    closed.
    
    This situation is handled properly by my_delete_allow_opened, so
    use it instead of my_delete.

ChangeSet@1.1616.3007.3, 2007-03-28 19:05:30+04:00, sergefp@mysql.com +1 -0
  Delete: sql/mysqld.cc.rej

  BitKeeper/deleted/.del-mysqld.cc.rej@1.2, 2007-03-28 19:02:58+04:00, sergefp@mysql.com +0 -0
    Delete: sql/mysqld.cc.rej

ChangeSet@1.1616.3007.2, 2007-03-28 18:38:42+04:00, sergefp@mysql.com +1 -0
  BUG#26625: crash in range optimizer (out of mem) 
  - Define Sql_alloc::operator new() as thow() so that C++ compiler
    handles NULL return values
  (there is no testcase as there is no portable way to set limit on the 
  amount of memory that a process can allocate)

  sql/sql_list.h@1.21.3.12, 2007-03-28 18:38:40+04:00, sergefp@mysql.com +2 -2
    BUG#26625: crash in range optimizer (out of mem) 
    - Define Sql_alloc::operator new() as thow() so that C++ compiler
      handles NULL return values

ChangeSet@1.2392.134.1, 2007-03-28 18:57:30+05:00, bar@mysql.com +5 -0
  Bug#22638 SOUNDEX broken for international characters
  Problem: SOUNDEX returned an invalid string for international
  characters in multi-byte character sets.
  For example: for a Chinese/Japanese 3-byte long character
  _utf8 0xE99885 it took only the very first byte 0xE9,
  put it into the outout string and then appended with three 
  DIGIT ZERO characters, so the result was 0xE9303030 - which
  is an invalide utf8 string.
  Fix: make SOUNDEX() multi-byte aware and - put only complete
  characters into result, thus return only valid strings.
  This patch also makes SOUNDEX() compatible with UCS2.

  mysql-test/r/ctype_ucs.result@1.51, 2007-03-28 18:57:27+05:00, bar@mysql.com +18 -0
    Adding tests

  mysql-test/r/ctype_utf8.result@1.104, 2007-03-28 18:57:27+05:00, bar@mysql.com +12 -0
    Adding tests

  mysql-test/t/ctype_ucs.test@1.50, 2007-03-28 18:57:27+05:00, bar@mysql.com +14 -0
    Adding tests

  mysql-test/t/ctype_utf8.test@1.95, 2007-03-28 18:57:27+05:00, bar@mysql.com +8 -0
    Adding tests

  sql/item_strfunc.cc@1.298.1.1, 2007-03-28 18:57:27+05:00, bar@mysql.com +105 -28
    Making soundex multi-byte aware.

ChangeSet@1.2410.2.13, 2007-03-28 15:56:57+02:00, msvensson@pilot.blaudden +1 -0
  Add back the look for exe_mysql

  mysql-test/mysql-test-run.pl@1.211.1.3, 2007-03-28 15:56:56+02:00, msvensson@pilot.blaudden +1 -0
    Add back the look for exe_mysql

ChangeSet@1.2410.2.12, 2007-03-28 15:34:52+02:00, msvensson@pilot.blaudden +3 -0
  Set yaSSL to use same type as MySQL do for socket handles

  extra/yassl/include/openssl/ssl.h@1.23, 2007-03-28 15:04:27+02:00, msvensson@pilot.blaudden +8 -2
    Import patch yassl.diff

  extra/yassl/src/ssl.cpp@1.29, 2007-03-28 15:04:28+02:00, msvensson@pilot.blaudden +1 -1
    Import patch yassl.diff

  include/violite.h@1.50, 2007-03-28 15:34:51+02:00, msvensson@pilot.blaudden +3 -0
    Set yaSSL to use same type as MySQL do for socket handles

ChangeSet@1.2410.14.2, 2007-03-28 14:35:23+03:00, gkodinov@magare.gmz +4 -0
  Bug #27300:
    Geometry fields have a result type string and a 
    special subclass to cater for the differences
    between them and the base class (just like 
    DATE/TIME).
    When creating temporary tables for results of 
    functions that return results of type GEOMETRY
    we must construct fields of the derived class 
    instead of the base class.
    Fixed by creating a GEOMETRY field (Field_geom) 
    instead of a generic BLOB (Field_blob) in temp 
    tables for the results of GIS functions that 
    have GEOMETRY return type (Item_geometry_func).

  mysql-test/r/gis.result@1.41.1.2, 2007-03-28 14:35:22+03:00, gkodinov@magare.gmz +11 -0
    Bug #27300: test case

  mysql-test/t/gis.test@1.34.1.2, 2007-03-28 14:35:22+03:00, gkodinov@magare.gmz +11 -0
    Bug #27300: test case

  sql/item.cc@1.260, 2007-03-28 14:35:22+03:00, gkodinov@magare.gmz +4 -1
    Bug #27300:
      Create a GEOMETRY field (Field_geom) instead of 
      a generic BLOB (Field_blob) in temp tables for 
      the results of GIS functions (Item_geometry_func). 

  sql/sql_select.cc@1.502.1.1, 2007-03-28 14:35:22+03:00, gkodinov@magare.gmz +3 -3
    Bug #27300:
      Create a GEOMETRY field (Field_geom) instead of 
      a generic BLOB (Field_blob) in temp tables for 
      the results of GIS functions (Item_geometry_func). 

ChangeSet@1.2392.133.1, 2007-03-28 12:23:55+02:00, msvensson@pilot.blaudden +3 -0
  Bug#25309 SSL connections without CA certificate broken since MySQL 5.0.23
   - Turn off verification of peer if both ca_path and ca_file is null
     i.e from only passing --ssl-key=<client_key> and --ssl-cert=<client_cert>
     to the mysql utility programs.
     The server will authenticate the client accoring to GRANT tables
     but the client won't authenticate the server 

  mysql-test/r/openssl_1.result@1.18, 2007-03-28 12:23:53+02:00, msvensson@pilot.blaudden +2 -0
    Update result file

  mysql-test/t/openssl_1.test@1.17.1.1, 2007-03-28 12:23:54+02:00, msvensson@pilot.blaudden +8 -1
    Test that it's possible to connect with --ssl-ca set to /dev/null

  vio/viosslfactories.c@1.33, 2007-03-28 12:23:54+02:00, msvensson@pilot.blaudden +8 -0
    Turn off verification of peer if both ca_file and ca_path is NULL

ChangeSet@1.2410.13.4, 2007-03-28 12:11:44+02:00, istruewing@chilla.local +1 -0
  After merge fix

  mysql-test/t/heap_btree.test@1.24, 2007-03-28 12:11:41+02:00, istruewing@chilla.local +2 -0
    After merge fix

ChangeSet@1.2410.2.11, 2007-03-28 11:16:50+02:00, msvensson@pilot.blaudden +1 -0
  Turn off im if extern
  Remove strange comment
  Add run_query function 

  mysql-test/mysql-test-run.pl@1.211.1.2, 2007-03-28 11:16:49+02:00, msvensson@pilot.blaudden +49 -16
    Turn off im if extern
    Remove strange comment
    Add run_query function 

ChangeSet@1.2410.14.1, 2007-03-28 12:09:30+03:00, gkodinov@magare.gmz +2 -0
  disabled a test reuturning wrong result (reported separately)

  mysql-test/r/subselect3.result@1.7, 2007-03-28 12:09:29+03:00, gkodinov@magare.gmz +0 -6
    disabled a test reuturning wrong result (reported separately)

  mysql-test/t/subselect3.test@1.7, 2007-03-28 12:09:29+03:00, gkodinov@magare.gmz +3 -2
    disabled a test reuturning wrong result (reported separately)

ChangeSet@1.2410.2.10, 2007-03-28 10:24:33+02:00, msvensson@pilot.blaudden +1 -0
  Dont' redirect stderr in ActiveState perl
  Improve comments

  mysql-test/lib/mtr_process.pl@1.53, 2007-03-28 10:24:32+02:00, msvensson@pilot.blaudden +19 -26
    Dont' redirect stderr in ActiveState perl
    Improve comments

ChangeSet@1.2392.30.3, 2007-03-28 10:12:33+02:00, msvensson@pilot.blaudden +1 -0
  Bug#27490 Function to log to NT event log could allocate memory
  - Change 'print_buffer_to_nt_event_log' to overwrite the string
  if the buffer is not long enough to hold the ending CR/LF's
  - Make functions static
  - Remove the "hack" intended to force 'print_buffer_to_nt_event_log'
   never to use "new"

  sql/log.cc@1.200.4.1, 2007-03-28 10:12:32+02:00, msvensson@pilot.blaudden +11 -23
    -Change 'print_buffer_to_nt_event_log' to overwrite the string
    if the buffer is not long enough to hold the ending CR/LF's
    - Make functions static
    - Remove the "hack" intended to force 'print_buffer_to_nt_event_log'
     never to use "new"

ChangeSet@1.2423, 2007-03-28 10:10:27+02:00, tomas@whalegate.ndb.mysql.com +2 -0
  Bug #25275 SINGLE USER MODE prevents ALTER on non-ndb tables for other mysqld nodes
  - test case

  mysql-test/r/ndb_single_user.result@1.4, 2007-03-28 10:10:26+02:00, tomas@whalegate.ndb.mysql.com +3 -0
    Bug #25275 SINGLE USER MODE prevents ALTER on non-ndb tables for other mysqld nodes
    - test case

  mysql-test/t/ndb_single_user.test@1.3, 2007-03-28 10:10:26+02:00, tomas@whalegate.ndb.mysql.com +12 -0
    Bug #25275 SINGLE USER MODE prevents ALTER on non-ndb tables for other mysqld nodes
    - test case

ChangeSet@1.2392.30.2, 2007-03-28 09:32:49+02:00, msvensson@pilot.blaudden +3 -0
  Bug#25197 repeat function returns null when using table field directly as count
   - Add extra test case from bug#27073
   - Change "if" to be optimized for count > 0

  mysql-test/r/func_str.result@1.127.1.1, 2007-03-28 09:32:47+02:00, msvensson@pilot.blaudden +9 -0
    Add test case from bug#27073

  mysql-test/t/func_str.test@1.100.1.1, 2007-03-28 09:32:47+02:00, msvensson@pilot.blaudden +4 -0
    Add test case from bug#27073

  sql/item_strfunc.cc@1.292.4.2, 2007-03-28 09:32:47+02:00, msvensson@pilot.blaudden +1 -1
    Change the if statemnet to be optimized for the normal case where count > 0

ChangeSet@1.2410.2.8, 2007-03-27 21:29:45+02:00, msvensson@pilot.blaudden +1 -0
  Remove remnants of ssl_des.test

  BitKeeper/deleted/.del-ssl_des-master.opt@1.3, 2007-03-27 21:15:49+02:00, msvensson@pilot.blaudden +0 -0
    Delete: mysql-test/t/ssl_des-master.opt

ChangeSet@1.2410.12.1, 2007-03-27 19:26:01+02:00, msvensson@pilot.blaudden +2 -0
  Bug#24121 Incorrect test for SSL_VERIFY_SERVER_CERT
   - Interpret the pointer passed to 'mysql_options' for
     MYSQL_OPT_SSL_VERIFY_SERVER_CERT as a my_bool
   - In 5.1 the mysql_options signature will be chanegd to take
     a 'void*' in order to further emphasize the need for a pointer
     to correct type

  client/mysqltest.c@1.283, 2007-03-27 19:25:59+02:00, msvensson@pilot.blaudden +3 -5
    Turn on ssl_verify_server_cert for all connections to "localhost"
    in mysqltest

  sql-common/client.c@1.111, 2007-03-27 19:26:00+02:00, msvensson@pilot.blaudden +1 -1
    The pointer passed to 'mysql_options' for MYSQL_OPT_SSL_VERIFY_SERVER_CERT
    should be interpreted as a my_bool pointer (aka char*).

ChangeSet@1.2410.11.1, 2007-03-27 09:48:10-07:00, igor@olga.mysql.com +3 -0
  Fixed bug #27348.
  If a set function with a outer reference s(outer_ref) cannot be aggregated 
  the outer query against which the reference has been resolved then MySQL
  interpretes s(outer_ref) in the same way as it would interpret s(const).
  Hovever the standard requires throwing an error in this situation.
  Added some code to support this requirement in ansi mode.
  Corrected another minor bug in Item_sum::check_sum_func.
   

  mysql-test/r/subselect.result@1.182, 2007-03-27 09:48:07-07:00, igor@olga.mysql.com +23 -0
    Added a test case for bug #27348.

  mysql-test/t/subselect.test@1.147, 2007-03-27 09:48:07-07:00, igor@olga.mysql.com +27 -0
    Added a test case for bug #27348.

  sql/item_sum.cc@1.201.1.1, 2007-03-27 09:48:07-07:00, igor@olga.mysql.com +5 -2
    Fixed bug #27348.
    If a set function with a outer reference s(outer_ref) cannot be aggregated 
    the outer query against which the reference has been resolved then MySQL
    interprets s(outer_ref) in the same way as it would interpret s(const).
    Hovever the standard requires throwing an error in this situation.
    Added some code to support this requirement in ansi mode.
    Corrected another minor bug in Item_sum::check_sum_func.
     

ChangeSet@1.2405.1.2, 2007-03-27 12:31:44-04:00, iggy@recycle.(none) +9 -0
  Bug#23491 MySQLDump prefix function call in a view by database name
  - mysqldump executes a SHOW CREATE VIEW statement to generate the text
  that it outputs.  When the function name is retrieved it's database 
  name is unconditionally prepended.  This change causes the function's 
  database name to be prepended only when it was used to define the 
  function.

  mysql-test/r/information_schema.result@1.121, 2007-03-27 12:31:42-04:00, iggy@recycle.(none) +1 -1
    Bug#23491 MySQLDump prefix function call in a view by database name
    - Updated Results.

  mysql-test/r/mysqldump.result@1.119.1.1, 2007-03-27 12:31:42-04:00, iggy@recycle.(none) +23 -0
    Bug#23491 MySQLDump prefix function call in a view by database name
    - Added new results.

  mysql-test/r/sp-code.result@1.10, 2007-03-27 12:31:42-04:00, iggy@recycle.(none) +1 -1
    Bug#23491 MySQLDump prefix function call in a view by database name
    - Updated Results.

  mysql-test/r/udf.result@1.12, 2007-03-27 12:31:43-04:00, iggy@recycle.(none) +1 -1
    Bug#23491 MySQLDump prefix function call in a view by database name
    - Updated Results.

  mysql-test/t/mysqldump.test@1.110.1.1, 2007-03-27 12:31:43-04:00, iggy@recycle.(none) +32 -0
    Bug#23491 MySQLDump prefix function call in a view by database name
    - Added new testcase.

  sql/item_func.cc@1.327.1.1, 2007-03-27 12:31:43-04:00, iggy@recycle.(none) +6 -3
    Bug#23491 MySQLDump prefix function call in a view by database name
    - Use new m_explicit_name member when deciding whether or not to prepend
    the db name while building the function name.

  sql/sp.cc@1.128, 2007-03-27 12:31:43-04:00, iggy@recycle.(none) +1 -1
    Bug#23491 MySQLDump prefix function call in a view by database name
    - Use new sp_name constructor.

  sql/sp_head.h@1.93.1.1, 2007-03-27 12:31:43-04:00, iggy@recycle.(none) +4 -2
    Bug#23491 MySQLDump prefix function call in a view by database name
    - Add m_explicit_name member to sp_name object.
    - Redefined sp_name constructor to include new member.

  sql/sql_yacc.yy@1.510.2.1, 2007-03-27 12:31:43-04:00, iggy@recycle.(none) +4 -4
    Bug#23491 MySQLDump prefix function call in a view by database name
    - Use new sp_name constructors.

ChangeSet@1.2410.1.11, 2007-03-27 19:28:04+03:00, gkodinov@magare.gmz +4 -0
  Bug #26815:
   When creating a temporary table the concise column type
   of a string expression is decided based on its length:
   - if its length is under 512 it is stored as either 
     varchar or char.
   - otherwise it is stored as a BLOB.
   
   There is a flag (convert_blob_length) to create_tmp_field 
   that, when >0 allows to force creation of a varchar if the
   max blob length is under convert_blob_length.
   However it must be verified that convert_blob_length 
   (settable through a SQL option in some cases) is 
   under the maximum that can be stored in a varchar column.
   While performing that check for expressions in 
   create_tmp_field_from_item the max length of the blob was
   used instead. This causes blob columns to be created in the
   heap temp table used by GROUP_CONCAT (where blobs must not
   be created in the temp table because of the constant 
   convert_blob_length that is passed to create_tmp_field() ).
   And since these blob columns are not expected in that place
   we get wrong results.
   Fixed by checking that the value of the flag variable is 
   in the limits that fit into VARCHAR instead of the max length
   of the blob column.

  mysql-test/r/func_gconcat.result@1.67, 2007-03-27 19:28:02+03:00, gkodinov@magare.gmz +10 -0
    Bug #26815: test case

  mysql-test/t/func_gconcat.test@1.54, 2007-03-27 19:28:02+03:00, gkodinov@magare.gmz +11 -1
    Bug #26815: test case

  sql/item_sum.cc@1.202, 2007-03-27 19:28:02+03:00, gkodinov@magare.gmz +1 -2
    Bug #26815: wrong length was checked

  sql/sql_select.cc@1.503, 2007-03-27 19:28:02+03:00, gkodinov@magare.gmz +1 -2
    Bug #26815: wrong length was checked

ChangeSet@1.2392.129.2, 2007-03-27 18:05:17+02:00, thek@kpdesk.mysql.com +2 -0
  Corrected error in test case:
  - 1.84e+15 converted to unsigned bigint should be
    18400000000000000000 < 18446744073709551615.
  - The test will still fail on windows, and is extracted
    into a new bug report.

  mysql-test/r/sp.result@1.224, 2007-03-27 18:05:14+02:00, thek@kpdesk.mysql.com +0 -3
    Corrected error in test case:
    - 1.84e+15 converted to unsigned bigint should be
      18400000000000000000 < 18446744073709551615.
    - The test will still fail on windows, and is extracted
      into a new bug report.

  mysql-test/t/sp.test@1.214, 2007-03-27 18:05:14+02:00, thek@kpdesk.mysql.com +0 -1
    Corrected error in test case:
    - 1.84e+15 converted to unsigned bigint should be
      18400000000000000000 < 18446744073709551615.
    - The test will still fail on windows, and is extracted
      into a new bug report.

ChangeSet@1.1616.3003.6, 2007-03-27 17:42:55+02:00, kent@mysql.com +2 -0
  mysql.spec.sh, Makefile.am:
    Don't use explicit calls to mysql-test-run in spec

  Makefile.am@1.60.1.20, 2007-03-27 17:42:46+02:00, kent@mysql.com +6 -0
    Don't use explicit calls to mysql-test-run in spec

  support-files/mysql.spec.sh@1.83.1.51, 2007-03-27 17:42:46+02:00, kent@mysql.com +1 -4
    Don't use explicit calls to mysql-test-run in spec

ChangeSet@1.2392.132.1, 2007-03-27 11:30:53-04:00, cmiller@zippy.cornsilk.net +1 -0
  Bug#26600: table PROFILING in INFORMATION SCHEMA has wrong data type
  
  Bug#27047[partial]: INFORMATION_SCHEMA table cannot have BIGINT \
  	fields
  
  No Information_schema table has ever needed floating-point data 
  before.  Transforming all floating point to a string and back to a
  number causes a real data problem on Windows, where the libc may 
  pad the exponent with more leading zeroes than we expect and the
  significant digits are truncated away.
  
  This also makes interpreting an unimplemented type as a string into
  a fatal error in debug builds.  Thus, we will catch problems when we
  try to use those types in new I_S tables.

  sql/sql_show.cc@1.337.1.3, 2007-03-27 11:30:51-04:00, cmiller@zippy.cornsilk.net +9 -0
    Add floating-point types to information_schema output.

ChangeSet@1.2392.90.5, 2007-03-27 12:39:31+02:00, istruewing@chilla.local +1 -0
  Bug#24985 - UTF8 ENUM primary key on MEMORY using BTREE
              causes incorrect duplicate entries
  After merge fix

  mysql-test/t/heap_btree.test@1.20.1.2, 2007-03-27 12:39:27+02:00, istruewing@chilla.local +17 -18
    Bug#24985 - UTF8 ENUM primary key on MEMORY using BTREE
                causes incorrect duplicate entries
    After merge fix

ChangeSet@1.2392.131.1, 2007-03-27 15:06:41+05:00, bar@mysql.com +3 -0
  Bug#22378 Make error, strings/ctype-utf8.c, uni_plane undeclared
  - Fixing utf8_general_cs according to recent changes.
  - Compiling utf8_general_cs in pentium-debug-max configuration
    to avoid these problems in the future.

  BUILD/compile-pentium-debug-max@1.18, 2007-03-27 15:06:38+05:00, bar@mysql.com +1 -1
    Enable compiling of experimental collations in compile-pentium-debug-max

  config/ac-macros/character_sets.m4@1.9, 2007-03-27 15:06:38+05:00, bar@mysql.com +13 -0
    Adding hidden flag --with-experimental-collations,
    not seen in "configure --help".

  strings/ctype-utf8.c@1.106, 2007-03-27 15:06:38+05:00, bar@mysql.com +6 -1
    Compilation failure changes:
    catching up with previous character set changes:
    - uni_plane is now not a global variables
    - adding new parameter into my_strnncollsp_utf8_cs
    - adding my_strnxfrm_len into MY_COLLATION_HANDLER 
      for utf8_general_cs

ChangeSet@1.1616.2993.2, 2007-03-27 10:49:48+02:00, istruewing@chilla.local +3 -0
  Bug#24985 - UTF8 ENUM primary key on MEMORY using BTREE
              causes incorrect duplicate entries
  
  Keys for BTREE indexes on ENUM and SET columns of MEMORY tables
  with character set UTF8 were computed incorrectly. Many
  different column values got the same key value.
  
  Apart of possible performance problems, it made unique indexes
  of this type unusable because it rejected many different
  values as duplicates.
  
  The problem was that multibyte character detection was tried
  on the internal numeric column value. Many values were not
  identified as characters. Their key value became blank filled.
  
  Thanks to Alexander Barkov and Ramil Kalimullin for the patch,
  which sets the character set of ENUM and SET key segments to
  the pseudo binary character set.

  mysql-test/r/heap_btree.result@1.13.3.1, 2007-03-27 10:49:47+02:00, istruewing@chilla.local +12 -0
    Bug#24985 - UTF8 ENUM primary key on MEMORY using BTREE
                causes incorrect duplicate entries
    Added test result.

  mysql-test/t/heap_btree.test@1.12.2.1, 2007-03-27 10:49:47+02:00, istruewing@chilla.local +17 -0
    Bug#24985 - UTF8 ENUM primary key on MEMORY using BTREE
                causes incorrect duplicate entries
    Added test.

  sql/ha_heap.cc@1.47.1.15, 2007-03-27 10:49:47+02:00, istruewing@chilla.local +4 -1
    Bug#24985 - UTF8 ENUM primary key on MEMORY using BTREE
                causes incorrect duplicate entries
    Set key segment charset to my_charset_bin for ENUM and SET
    columns.

ChangeSet@1.2392.130.1, 2007-03-27 13:30:43+05:00, bar@mysql.com +2 -0
  Bug#25946 Namespace not include for xsi usage within --xml output with null/nil values
  Fix: adding namespace reference into "mysql --xml" output,
  to make it work similary to "mysqldump --xml".

  client/mysql.cc@1.235, 2007-03-27 13:30:40+05:00, bar@mysql.com +2 -1
    Adding namespace reference.

  mysql-test/r/client_xml.result@1.5, 2007-03-27 13:30:41+05:00, bar@mysql.com +6 -6
    Fixing test results

ChangeSet@1.2392.105.3, 2007-03-27 12:20:20+05:00, bar@mysql.com +3 -0
  Bug#27079 Crash while grouping empty ucs2 strings
  Problem: GROUP BY on empty ucs2 strings crashed server.
  Reason: sometimes mi_unique_hash() is executed with
  ptr=null and length=0, which means "empty string".
  The branch of code handling UCS2 character set
  was not safe against ptr=null and fell into and
  endless loop even if length=0 because of poiter
  arithmetic overflow.
  Fix: adding special check for length=0 to avoid pointer arithmetic
  overflow.

  mysql-test/r/ctype_uca.result@1.18, 2007-03-27 12:20:17+05:00, bar@mysql.com +9 -0
    Adding test case

  mysql-test/t/ctype_uca.test@1.16, 2007-03-27 12:20:17+05:00, bar@mysql.com +10 -0
    Adding test case

  strings/ctype-uca.c@1.44, 2007-03-27 12:20:17+05:00, bar@mysql.com +27 -7
    Fix my_uca_scanner_init_ucs2 to be safe against
    strings with length=0 and ptr=0.

ChangeSet@1.2420, 2007-03-26 17:57:00+02:00, tomas@whalegate.ndb.mysql.com +3 -0
      correct medium int printout
      correct cit printout
      correct bit store retrieve

  ndb/include/ndbapi/NdbRecAttr.hpp@1.20, 2007-03-26 17:56:58+02:00, tomas@whalegate.ndb.mysql.com +2 -5
    correct medium int printout

  ndb/src/ndbapi/NdbRecAttr.cpp@1.33, 2007-03-26 17:56:59+02:00, tomas@whalegate.ndb.mysql.com +6 -17
    correct cit printout

  sql/ha_ndbcluster.cc@1.299.2.2, 2007-03-26 17:56:59+02:00, tomas@whalegate.ndb.mysql.com +7 -2
    correct bit store retrieve

ChangeSet@1.2410.1.10, 2007-03-26 16:52:52+03:00, gkodinov@magare.gmz +3 -0
  WL3527: 5.0 part:
  enabled the optional FOR JOIN to all the three
  clauses : USE, FORCE and IGNORE

  mysql-test/r/select.result@1.154, 2007-03-26 16:52:51+03:00, gkodinov@magare.gmz +6 -0
    WL3527: 5.0 part: test cases

  mysql-test/t/select.test@1.128, 2007-03-26 16:52:51+03:00, gkodinov@magare.gmz +2 -0
    WL3527: 5.0 part: test cases

  sql/sql_yacc.yy@1.513, 2007-03-26 16:52:51+03:00, gkodinov@magare.gmz +4 -8
    WL3527: 5.0 part:
    enabled the optional FOR JOIN to all the three
    clauses : USE, FORCE and IGNORE

ChangeSet@1.2417.1.1, 2007-03-26 14:48:52+02:00, tomas@whalegate.ndb.mysql.com +1 -0
  Bug #26986  	BIT(33) for ndb is broken on solaris.
  - always store lsw first in ndb

  sql/ha_ndbcluster.cc@1.299.2.1, 2007-03-26 14:48:50+02:00, tomas@whalegate.ndb.mysql.com +9 -5
    Bug #26986  	BIT(33) for ndb is broken on solaris.
    - always store lsw first in ndb

ChangeSet@1.1616.3007.1, 2007-03-26 13:17:40+03:00, gkodinov@magare.gmz +3 -0
  Bug #27164: not reseting the data pointer
   to 0 causes wrong (large) length to be read
   from the row in _mi_calc_blob_length() when 
   storing NULL values in (e.g) POINT columns.
   This large length is then used to allocate
   a block of memory that (on some OSes) causes
   trouble.
   Fixed by calling the base class's 
   Field_blob::reset() from Field_geom::reset()
   that is called when storing a NULL value into
   the column.

  mysql-test/r/gis.result@1.15.1.10, 2007-03-26 13:17:39+03:00, gkodinov@magare.gmz +6 -0
    Bug #27164: test case

  mysql-test/t/gis.test@1.17.1.6, 2007-03-26 13:17:39+03:00, gkodinov@magare.gmz +8 -0
    Bug #27164: test case

  sql/field.h@1.120.1.17, 2007-03-26 13:17:39+03:00, gkodinov@magare.gmz +1 -1
    Bug #27164: not reseting the data pointer
     to 0 causes wrong (large) length to be read
     from the row in _mi_calc_blob_length() when 
     storing NULL values in (e.g) POINT columns.
     This large length is then used to allocate
     a block of memory that (on some OSes) causes
     trouble.

ChangeSet@1.2392.58.3, 2007-03-26 13:31:23+04:00, kaa@polly.local +2 -0
  Fix for bug #26844 "Memory allocation failures ignored by slave IO thread".
  
  Pass ME_NOREFRESH flag to an error handler in my_malloc() and _mymalloc() in case of memory allocation failure, so that it gets logged to the error log.

  mysys/my_malloc.c@1.13, 2007-03-26 13:31:20+04:00, kaa@polly.local +1 -1
    Pass ME_NOREFRESH flag to an error handler in my_malloc() in case of memory allocation failure, so that it gets logged to the error log.

  mysys/safemalloc.c@1.28, 2007-03-26 13:31:20+04:00, kaa@polly.local +2 -2
    Pass ME_NOREFRESH flag to an error handler in _mymalloc() in case of memory allocation failure, so that it gets logged to the error log.

ChangeSet@1.2417, 2007-03-26 10:39:11+02:00, tomas@whalegate.ndb.mysql.com +1 -0
  remove warning

  ndb/test/src/NDBT_Table.cpp@1.11, 2007-03-26 10:39:09+02:00, tomas@whalegate.ndb.mysql.com +1 -1
    remove warning

ChangeSet@1.2416, 2007-03-26 09:58:01+02:00, tomas@whalegate.ndb.mysql.com +1 -0
  Bug #26900 ndb_restore printout option does not give structured data
  - set sizes for data

  ndb/tools/restore/Restore.cpp@1.31, 2007-03-26 09:57:59+02:00, tomas@whalegate.ndb.mysql.com +5 -1
    Bug #26900 ndb_restore printout option does not give structured data
    - set sizes for data

ChangeSet@1.2410.2.4, 2007-03-26 12:56:41+05:00, ramil@mysql.com +3 -0
  Fix for bug #25993: mysqldump crashes with merge table and -c option
    
  opt_complete_insert was improperly used by accident.
  Use complete_insert flag instead.

  client/mysqldump.c@1.260, 2007-03-26 12:56:39+05:00, ramil@mysql.com +3 -3
    Fix for bug #25993: mysqldump crashes with merge table and -c option
      - use complete_insert instead of opt_complete_insert.

  mysql-test/r/mysqldump.result@1.121, 2007-03-26 12:56:40+05:00, ramil@mysql.com +47 -0
    Fix for bug #25993: mysqldump crashes with merge table and -c option
      - test result.

  mysql-test/t/mysqldump.test@1.112, 2007-03-26 12:56:40+05:00, ramil@mysql.com +10 -0
    Fix for bug #25993: mysqldump crashes with merge table and -c option
      - test case.

ChangeSet@1.2410.9.1, 2007-03-25 23:44:06-07:00, igor@olga.mysql.com +2 -0
  This is a fix for the memory corruption occurred in one of test cases
  from func_group.test after the patch for bug #27229 had been applied.
  The memory corruption happened because in some rare cases the function
  count_field_types underestimated the number of elements in
  in the array param->items_to_copy.

  sql/item_sum.cc@1.201, 2007-03-25 23:44:03-07:00, igor@olga.mysql.com +1 -2
    The return value of the Item_sum::update_used_tables method
    should not depend on the place of aggregation of the set 
    function for which the Item_sum object has been created.

  sql/sql_select.cc@1.502, 2007-03-25 23:44:03-07:00, igor@olga.mysql.com +16 -10
    This is a fix for the memory corruption occurred in one of test cases
    from func_group.test after the patch for bug #27229 had been applied.
    The memory corruption happened because in some rare cases the function
    count_field_types underestimated the number of elements in
    in the array param->items_to_copy.
    
    Currently it's not guaranteed that after JOIN::prepare() the 
    used_tables attribute is calculated for all items. For example
    for the expression SUM(outer_ref)+1 used_tables() must return
    OUTER_REF_TABLE_BIT. Yet by the moment when the used_tables
    attribute is calculated in JOIN::prepare SUM(outer_ref) has
    not been substituted for Item_aggregate_ref yet.
    By this reason additional calls of the method update_used_tables
    are needed for some items passed as parameters to the function
    create_tmp_table. 
     

ChangeSet@1.1616.3003.5, 2007-03-24 14:03:27+02:00, serg@sergbook.mysql.com +1 -0
  nptl: typo fixed. sigaddset restored

  sql/mysqld.cc@1.356.98.43, 2007-03-24 14:03:25+02:00, serg@sergbook.mysql.com +4 -2
    nptl: typo fixed. sigaddset restored

ChangeSet@1.2410.7.1, 2007-03-23 16:28:07-06:00, tsmith@siva.hindu.god +8 -0
  Bug #24563: MBROverlaps does not seem to function propertly.
  
  Fix is to rewrite the MBR::overlaps() function, to compute the dimension of both
  arguments, and the dimension of the intersection; test that all three dimensions are the
  same (e.g., all are Polygons).
  
  Add tests for all MBR* functions for various combinations of shapes, lines and points.

  mysql-test/include/gis_generic.inc@1.5, 2007-03-23 16:28:02-06:00, tsmith@siva.hindu.god +70 -1
    Add tests & checks for bug #24563 and bug #24588 - some GIS functions missing in
    5.1; many GIS functions not tested; Overlaps() function was incorrect when MBR shifted
    only along one axis; Overlaps() needs to take dimension of shape into account.

  mysql-test/r/archive_gis.result@1.5, 2007-03-23 16:28:02-06:00, tsmith@siva.hindu.god +87 -1
    Update test results.

  mysql-test/r/bdb_gis.result@1.5, 2007-03-23 16:28:02-06:00, tsmith@siva.hindu.god +62 -1
    Update test results.

  mysql-test/r/gis.result@1.42, 2007-03-23 16:28:02-06:00, tsmith@siva.hindu.god +86 -1
    Update test results.

  mysql-test/r/innodb_gis.result@1.5, 2007-03-23 16:28:02-06:00, tsmith@siva.hindu.god +87 -1
    Update test results.

  mysql-test/r/ndb_gis.result@1.6, 2007-03-23 16:28:02-06:00, tsmith@siva.hindu.god +174 -2
    Update test results.

  mysql-test/t/gis.test@1.35, 2007-03-23 16:28:02-06:00, tsmith@siva.hindu.god +68 -0
    Add tests & checks for bug #24563 and bug #24588 - some GIS functions missing in
    5.1; many GIS functions not tested; Overlaps() function was incorrect when MBR shifted
    only along one axis; Overlaps() needs to take dimension of shape into account.

  sql/spatial.h@1.25, 2007-03-23 16:28:02-06:00, tsmith@siva.hindu.god +37 -6
    Add MBR::dimension() (map MBR to integral dimension: point -> 0, line -> 1,
    polygon -> 2, invalid -> -1)
    
    Fix MBR::overlaps() to handle MBRs which are shifted on one dimension only, and to
    take MBR dimension into account.  Also, test both within() and contains() predicates (so
    that overlaps(a, b) == overlaps(b, a)).

ChangeSet@1.2410.2.3, 2007-03-23 18:15:11-04:00, dkatz@damiendev. +1 -0
  bug#26346
  
  Added some fixes for an existing memory leak and unitilialized variables, both caught by gcc.

  client/mysqldump.c@1.259, 2007-03-23 18:15:06-04:00, dkatz@damiendev. +3 -2
    bug#26346
    
    Added some fixes for an existing memory leak and unitilialized variables, both caught by gcc.

ChangeSet@1.2410.5.4, 2007-03-23 22:16:32+02:00, serg@sergbook.mysql.com +1 -0
  bug in im* tests - missing --no-defaults in the mysql command line

  mysql-test/t/wait_for_socket.sh@1.5, 2007-03-23 22:16:25+02:00, serg@sergbook.mysql.com +1 -1
    bug in im* tests - missing --no-defaults in the mysql command line

ChangeSet@1.1616.3003.4, 2007-03-23 20:37:20+02:00, serg@sergbook.mysql.com +2 -0
  reverted linuxthreads thr_client_alarm fix (not future-proof)
  fixed differently: wake up select_thread with THR_SERVER_ALARM instead

  mysys/thr_alarm.c@1.44.2.8, 2007-03-23 20:37:18+02:00, serg@sergbook.mysql.com +4 -0
    reverted linuxthreads thr_client_alarm fix (not future-proof)

  sql/mysqld.cc@1.356.98.42, 2007-03-23 20:37:18+02:00, serg@sergbook.mysql.com +8 -15
    reverted linuxthreads thr_client_alarm fix (not future-proof)
    fixed differently: wake up select_thread with THR_SERVER_ALARM instead

ChangeSet@1.2410.6.1, 2007-03-23 19:00:34+01:00, msvensson@pilot.blaudden +1 -0
  Bug#26837 Return value ignored for packet->append() call within Log_event::read_log_event
   - Improve error handling for "out of memory" problems when master is
     sending logs to slave. If memory allocation fails the log should
     now  report error "memory allocation failed reading log event"  

  sql/log_event.cc@1.230, 2007-03-23 19:00:33+01:00, msvensson@pilot.blaudden +21 -6
    Return LOG_READ_MEM from "Log_event::read_log_event" if memory
    allocation  fails.

ChangeSet@1.2414, 2007-03-23 17:14:38+01:00, tomas@whalegate.ndb.mysql.com +3 -0
  enabled and extended single user test

  mysql-test/r/ndb_single_user.result@1.3, 2007-03-23 17:14:35+01:00, tomas@whalegate.ndb.mysql.com +10 -0
    enabled and extended single user test

  mysql-test/t/disabled.def@1.46, 2007-03-23 17:14:35+01:00, tomas@whalegate.ndb.mysql.com +0 -1
    enabled and extended single user test

  mysql-test/t/ndb_single_user.test@1.2, 2007-03-23 17:14:35+01:00, tomas@whalegate.ndb.mysql.com +37 -16
    enabled and extended single user test

ChangeSet@1.2377.39.11, 2007-03-23 17:07:33+01:00, tomas@whalegate.ndb.mysql.com +1 -0
  Bug #25275 SINGLE USER MODE prevents ALTER on non-ndb tables for other mysqld nodes

  ndb/src/kernel/blocks/dbtc/DbtcMain.cpp@1.103.2.3, 2007-03-23 17:07:31+01:00, tomas@whalegate.ndb.mysql.com +8 -2
    abort on timeout if in single user mode

ChangeSet@1.2405.3.2, 2007-03-23 16:41:17+01:00, msvensson@pilot.blaudden +4 -0
  Import patch from yaSSL after fixing warnings upstream

  extra/yassl/src/ssl.cpp@1.28, 2007-03-23 16:09:15+01:00, msvensson@pilot.blaudden +1 -1
    Import patch yassl.diff

  extra/yassl/taocrypt/src/integer.cpp@1.31, 2007-03-23 16:30:14+01:00, msvensson@pilot.blaudden +1 -1
    Import patch yassl.diff

  extra/yassl/taocrypt/test/test.cpp@1.8, 2007-03-23 16:09:15+01:00, msvensson@pilot.blaudden +1 -2
    Import patch yassl.diff

  extra/yassl/testsuite/testsuite.cpp@1.9, 2007-03-23 16:09:15+01:00, msvensson@pilot.blaudden +1 -1
    Import patch yassl.diff

ChangeSet@1.2377.39.10, 2007-03-23 13:52:03+01:00, tomas@whalegate.ndb.mysql.com +13 -0
  Bug #25275 SINGLE USER MODE prevents ALTER on non-ndb tables for other mysqld nodes

  ndb/include/kernel/signaldata/DictTabInfo.hpp@1.20.1.2, 2007-03-23 13:51:54+01:00, tomas@whalegate.ndb.mysql.com +4 -1
    add single user mode field in table definition

  ndb/include/ndb_constants.h@1.12, 2007-03-23 13:51:54+01:00, tomas@whalegate.ndb.mysql.com +7 -0
    new constants for single usermode option of tables

  ndb/include/ndbapi/NdbDictionary.hpp@1.58, 2007-03-23 13:51:54+01:00, tomas@whalegate.ndb.mysql.com +16 -0
    add single user mode field in table definition

  ndb/src/common/debugger/signaldata/DictTabInfo.cpp@1.9, 2007-03-23 13:51:54+01:00, tomas@whalegate.ndb.mysql.com +3 -0
    add single user mode field in table definition

  ndb/src/kernel/blocks/dbdict/Dbdict.cpp@1.71.2.1, 2007-03-23 13:51:54+01:00, tomas@whalegate.ndb.mysql.com +6 -3
    add single user mode field in table definition
    send this infor to TC

  ndb/src/kernel/blocks/dbdict/Dbdict.hpp@1.24.2.1, 2007-03-23 13:51:55+01:00, tomas@whalegate.ndb.mysql.com +5 -0
    add single user mode field in table definition

  ndb/src/kernel/blocks/dbtc/Dbtc.hpp@1.36.2.2, 2007-03-23 13:51:55+01:00, tomas@whalegate.ndb.mysql.com +18 -6
    single user table mode on table object
    merge some flags from uint8 to bits
    get allow transaction to also check single user mode

  ndb/src/kernel/blocks/dbtc/DbtcMain.cpp@1.103.2.2, 2007-03-23 13:51:55+01:00, tomas@whalegate.ndb.mysql.com +54 -33
    single user table mode on table object
    merge some flags from uint8 to bits
    get allow transaction to also check single user mode

  ndb/src/kernel/blocks/ndbcntr/NdbcntrMain.cpp@1.34.3.1, 2007-03-23 13:51:55+01:00, tomas@whalegate.ndb.mysql.com +1 -0
    set single user mode flag on system tables to make them always updatable

  ndb/src/ndbapi/NdbDictionary.cpp@1.41, 2007-03-23 13:51:55+01:00, tomas@whalegate.ndb.mysql.com +12 -0
    get/set functions for single user mode on tables

  ndb/src/ndbapi/NdbDictionaryImpl.cpp@1.95.2.1, 2007-03-23 13:51:55+01:00, tomas@whalegate.ndb.mysql.com +15 -2
    get/set functions for single user mode on tables

  ndb/src/ndbapi/NdbDictionaryImpl.hpp@1.42, 2007-03-23 13:51:55+01:00, tomas@whalegate.ndb.mysql.com +1 -0
    get/set functions for single user mode on tables

  ndb/test/src/NDBT_Table.cpp@1.10, 2007-03-23 13:51:56+01:00, tomas@whalegate.ndb.mysql.com +1 -1
    print single user mode

ChangeSet@1.1616.3004.1, 2007-03-23 13:38:42+02:00, serg@sergbook.mysql.com +2 -0
  move thr_client_alarm initialization to mysqld.cc
  (in thr_alarm.cc it happened too late).

  mysys/thr_alarm.c@1.44.3.1, 2007-03-23 13:38:36+02:00, serg@sergbook.mysql.com +0 -4
    move thr_client_alarm initialization to mysqld.cc
    (here it happened too late)

  sql/mysqld.cc@1.356.116.1, 2007-03-23 13:38:36+02:00, serg@sergbook.mysql.com +11 -3
    move thr_client_alarm initialization to mysqld.cc
    (in thr_alarm.cc it happened too late).
    moved thr_kill_signal initialization to init_signals()

ChangeSet@1.2410.3.3, 2007-03-23 12:35:30+01:00, msvensson@pilot.blaudden +2 -0
  Backport from 5.1, limit SHOW VARIABLES to "log_bin%"

  mysql-test/r/flush2.result@1.2, 2007-03-23 12:35:28+01:00, msvensson@pilot.blaudden +2 -14
    Backport from 5.1, limit SHOW VARIABLES to "log_bin%"

  mysql-test/t/flush2.test@1.2, 2007-03-23 12:35:28+01:00, msvensson@pilot.blaudden +2 -2
    Backport from 5.1, limit SHOW VARIABLES to "log_bin%"

ChangeSet@1.2405.3.1, 2007-03-23 11:52:25+01:00, msvensson@pilot.blaudden +31 -0
  Import yassl 1.6.0

  extra/yassl/README@1.10, 2007-03-15 03:15:05+01:00, msvensson@pilot.blaudden +8 -0
    Import patch yassl.diff

  extra/yassl/include/buffer.hpp@1.9, 2007-03-15 03:15:07+01:00, msvensson@pilot.blaudden +0 -3
    Import patch yassl.diff

  extra/yassl/include/crypto_wrapper.hpp@1.8, 2007-03-15 03:15:08+01:00, msvensson@pilot.blaudden +0 -6
    Import patch yassl.diff

  extra/yassl/include/openssl/ssl.h@1.22, 2007-03-20 22:43:58+01:00, msvensson@pilot.blaudden +3 -7
    Import patch yassl.diff

  extra/yassl/include/socket_wrapper.hpp@1.12, 2007-03-15 03:15:08+01:00, msvensson@pilot.blaudden +4 -2
    Import patch yassl.diff

  extra/yassl/include/yassl_imp.hpp@1.10, 2007-03-15 03:15:08+01:00, msvensson@pilot.blaudden +1 -16
    Import patch yassl.diff

  extra/yassl/include/yassl_int.hpp@1.18, 2007-03-15 03:15:08+01:00, msvensson@pilot.blaudden +0 -1
    Import patch yassl.diff

  extra/yassl/src/crypto_wrapper.cpp@1.12, 2007-03-15 03:15:09+01:00, msvensson@pilot.blaudden +0 -2
    Import patch yassl.diff

  extra/yassl/src/ssl.cpp@1.27, 2007-03-15 03:15:10+01:00, msvensson@pilot.blaudden +2 -2
    Import patch yassl.diff

  extra/yassl/taocrypt/README@1.2, 2007-03-15 03:15:10+01:00, msvensson@pilot.blaudden +12 -1
    Import patch yassl.diff

  extra/yassl/taocrypt/benchmark/benchmark.cpp@1.4, 2006-04-11 22:34:30+02:00, msvensson@pilot.blaudden +16 -16
    Import patch yassl.diff

  extra/yassl/taocrypt/include/algebra.hpp@1.9, 2007-03-15 03:15:10+01:00, msvensson@pilot.blaudden +0 -3
    Import patch yassl.diff

  extra/yassl/taocrypt/include/des.hpp@1.8, 2007-03-15 03:15:11+01:00, msvensson@pilot.blaudden +0 -1
    Import patch yassl.diff

  extra/yassl/taocrypt/include/hash.hpp@1.9, 2007-03-20 22:43:58+01:00, msvensson@pilot.blaudden +33 -3
    Import patch yassl.diff

  extra/yassl/taocrypt/include/hmac.hpp@1.9, 2007-03-15 03:15:12+01:00, msvensson@pilot.blaudden +2 -2
    Import patch yassl.diff

  extra/yassl/taocrypt/include/misc.hpp@1.18, 2007-03-20 22:43:58+01:00, msvensson@pilot.blaudden +19 -0
    Import patch yassl.diff

  extra/yassl/taocrypt/include/modarith.hpp@1.6, 2007-03-15 03:15:12+01:00, msvensson@pilot.blaudden +2 -2
    Import patch yassl.diff

  extra/yassl/taocrypt/include/modes.hpp@1.11, 2007-03-15 03:15:12+01:00, msvensson@pilot.blaudden +2 -2
    Import patch yassl.diff

  extra/yassl/taocrypt/include/rsa.hpp@1.7, 2007-03-15 03:15:12+01:00, msvensson@pilot.blaudden +15 -19
    Import patch yassl.diff

  extra/yassl/taocrypt/include/sha.hpp@1.6, 2007-03-20 22:43:58+01:00, msvensson@pilot.blaudden +97 -0
    Import patch yassl.diff

  extra/yassl/taocrypt/include/type_traits.hpp@1.6, 2007-03-15 03:15:12+01:00, msvensson@pilot.blaudden +1 -5
    Import patch yassl.diff

  extra/yassl/taocrypt/include/types.hpp@1.12, 2007-03-20 22:43:58+01:00, msvensson@pilot.blaudden +3 -0
    Import patch yassl.diff

  extra/yassl/taocrypt/mySTL/list.hpp@1.4, 2006-09-18 22:19:22+02:00, msvensson@pilot.blaudden +8 -8
    Import patch yassl.diff

  extra/yassl/taocrypt/src/aes.cpp@1.8, 2007-03-15 03:15:12+01:00, msvensson@pilot.blaudden +2 -9
    Import patch yassl.diff

  extra/yassl/taocrypt/src/algebra.cpp@1.15, 2007-03-15 03:15:12+01:00, msvensson@pilot.blaudden +3 -3
    Import patch yassl.diff

  extra/yassl/taocrypt/src/asn.cpp@1.15, 2007-03-15 03:15:16+01:00, msvensson@pilot.blaudden +4 -4
    Import patch yassl.diff

  extra/yassl/taocrypt/src/hash.cpp@1.6, 2007-03-20 22:43:58+01:00, msvensson@pilot.blaudden +85 -0
    Import patch yassl.diff

  extra/yassl/taocrypt/src/integer.cpp@1.30, 2007-03-15 03:15:16+01:00, msvensson@pilot.blaudden +1 -1
    Import patch yassl.diff

  extra/yassl/taocrypt/src/sha.cpp@1.8, 2007-03-20 22:43:58+01:00, msvensson@pilot.blaudden +410 -0
    Import patch yassl.diff

  extra/yassl/taocrypt/test/test.cpp@1.7, 2007-03-20 22:43:58+01:00, msvensson@pilot.blaudden +212 -46
    Import patch yassl.diff

  extra/yassl/testsuite/testsuite.cpp@1.8, 2006-05-04 22:23:39+02:00, msvensson@pilot.blaudden +8 -9
    Import patch yassl.diff

ChangeSet@1.2405.2.1, 2007-03-23 11:18:59+01:00, msvensson@pilot.blaudden +1 -0
  Bug#27070 server logs are created unrequested and in wrong directory
   - Add output path for slow queries as well 

  mysql-test/mysql-test-run.pl@1.211.1.1, 2007-03-23 11:18:57+01:00, msvensson@pilot.blaudden +4 -7
    Send queries to var/log/$type.log and slow queries to var/log/$type-slow.log

ChangeSet@1.2392.128.1, 2007-03-23 11:01:47+01:00, msvensson@pilot.blaudden +3 -0
  Bug#26233 very suspect code in mf_tempfile.c, in function create_temp_file()
   - Rework the windows implementation in 'create_temp_file' to be
     thread safe by using GetTempFileName instad of fiddling
     with "environ"

  mysys/mf_tempfile.c@1.26, 2007-03-23 11:01:46+01:00, msvensson@pilot.blaudden +61 -84
    - Update windows implementation  of 'create_temp_file' to use
      GetTempFileName in favor of fiddeling with "environ" in an unsafe way
    - Remove the implementation that is supposed to be used if not
      windows, not mkstemp or tmpnam exists as it not longer compiles it
      can't be used anywhere.
    - Update function comment for 'create_temp_file' 

  mysys/my_static.c@1.18, 2007-03-23 11:01:46+01:00, msvensson@pilot.blaudden +0 -5
    Remove unused variable

  mysys/my_static.h@1.20, 2007-03-23 11:01:47+01:00, msvensson@pilot.blaudden +0 -4
    Remove unused variable

ChangeSet@1.2392.127.1, 2007-03-22 14:48:03-07:00, igor@olga.mysql.com +9 -0
  Fixed bug #27229: crash when a set function aggregated in outer
  context was used as an argument of GROUP_CONCAT.
  Ensured correct setting of the depended_from field in references
  generated for set functions aggregated in outer selects.
  A wrong value of this field resulted in wrong maps returned by 
  used_tables() for these references.
  Made sure that a temporary table field is added for any set function
  aggregated in outer context when creation of a temporary table is 
  needed to execute the inner subquery. 

  mysql-test/r/subselect.result@1.181, 2007-03-22 14:48:00-07:00, igor@olga.mysql.com +19 -0
    Added a test case for bug #27229.

  mysql-test/t/subselect.test@1.146, 2007-03-22 14:48:00-07:00, igor@olga.mysql.com +19 -0
    Added a test case for bug #27229.

  sql/item.cc@1.256.2.1, 2007-03-22 14:48:00-07:00, igor@olga.mysql.com +6 -3
    Fixed bug #27229: crash when a set function aggregated in outer
    context was used as an argument of GROUP_CONCAT.
    Ensured correct setting of the depended_from field in references
    generated for set functions aggregated in outer selects.
      

  sql/item_sum.cc@1.198.1.1, 2007-03-22 14:48:00-07:00, igor@olga.mysql.com +18 -15
    Fixed bug #27229: crash when a set function aggregated in outer
    context was used as an argument of GROUP_CONCAT.
    Added the field aggr_sel to the objects of the class Item_sum.
    In any Item_sum object created for a set function this field 
    has to contain a pointer to the select where the set function
    is aggregated.

  sql/item_sum.h@1.112, 2007-03-22 14:48:00-07:00, igor@olga.mysql.com +3 -1
    Fixed bug #27229: crash when a set function aggregated in outer
    context was used as an argument of GROUP_CONCAT.
    Added the field aggr_sel to the objects of the class Item_sum.
    In any Item_sum object created for a set function this field 
    has to contain a pointer to the select where the set function
    is aggregated.
    Added a method that says whether a set function is aggregated
    in outer context and, if so, returns the aggregating select.
    Removed the field nest_level_tables_count introduced by the
    patch for bug 24484 as aggr_sel->join->tables contains the
    sane number. 

  sql/sql_base.cc@1.370.1.2, 2007-03-22 14:48:00-07:00, igor@olga.mysql.com +0 -2
    Fixed bug #27229: crash when a set function aggregated in outer
    context was used as an argument of GROUP_CONCAT.
    Added the field aggr_sel to the objects of the class Item_sum.
    Removed changes introduced by the patch for bug 24484 as 
    the field leaf_count of the THD class is not used anymore.

  sql/sql_class.h@1.327, 2007-03-22 14:48:01-07:00, igor@olga.mysql.com +0 -3
    Fixed bug #27229: crash when a set function aggregated in outer
    context was used as an argument of GROUP_CONCAT.
    Added the field aggr_sel to the objects of the class Item_sum.
    Removed changes introduce by the patch for bug 24484 as 
    the field leaf_count of the THD class is not used anymore.

  sql/sql_insert.cc@1.227, 2007-03-22 14:48:01-07:00, igor@olga.mysql.com +2 -4
    Fixed bug #27229: crash when a set function aggregated in outer
    context was used as an argument of GROUP_CONCAT.
    Added the field aggr_sel to the objects of the class Item_sum.
    Removed changes introduce by the patch for bug 24484 as 
    the field leaf_count of the THD class is not used anymore.

  sql/sql_select.cc@1.498.1.2, 2007-03-22 14:48:01-07:00, igor@olga.mysql.com +9 -2
    Fixed bug #27229: crash when a set function aggregated in outer
    context was used as an argument of GROUP_CONCAT.
    When creating a temporary table a field is added in it for any 
    set function aggregated in outer context. 

ChangeSet@1.2410.3.1, 2007-03-22 14:40:52-06:00, tsmith@siva.hindu.god +9 -0
  NULL MERGE this to 5.1
  
  Apply the following InnoDB snapshots:
  innodb-5.0-ss1319
  innodb-5.0-ss1331
  innodb-5.0-ss1333
  innodb-5.0-ss1341
  
  Fixes:
  - Bug #21409: Incorrect result returned when in READ-COMMITTED with query_cache ON
    At low transaction isolation levels we let each consistent read set
    its own snapshot.
  - Bug #23666: strange Innodb_row_lock_time_% values in show status; also millisecs wrong
    On Windows ut_usectime returns secs and usecs relative to the UNIX
    epoch (which is Jan, 1 1970).
  
  - Bug #25494: LATEST DEADLOCK INFORMATION is not always cleared
    lock_deadlock_recursive(): When the search depth or length is exceeded,
    rewind lock_latest_err_file and display the two transactions at the
    point of aborting the search.
  
  - Bug #25927: Foreign key with ON DELETE SET NULL on NOT NULL can crash server
    Prevent ALTER TABLE ... MODIFY ... NOT NULL on columns for which
    there is a foreign key constraint ON ... SET NULL.
  
  - Bug #26835: Repeatable corruption of utf8-enabled tables inside InnoDB
    The bug could be reproduced as follows:
  
    Define a table so that the first column of the clustered index is
    a VARCHAR or a UTF-8 CHAR in a collation where sequences of bytes
    of differing length are considered equivalent.
  
    Insert and delete a record.  Before the delete-marked record is
    purged, insert another record whose first column is of different
    length but equivalent to the first record.  Under certain conditions,
    the insertion can be incorrectly performed as update-in-place.
  
    Likewise, an operation that could be done as update-in-place can
    unnecessarily be performed as delete and insert, but that would not
    cause corruption but merely degraded performance.

  innobase/dict/dict0dict.c@1.83, 2007-03-22 14:40:46-06:00, tsmith@siva.hindu.god +26 -10
    NULL MERGE this to 5.1
    
    Apply the following InnoDB snapshots:
    innodb-5.0-ss1319
    innodb-5.0-ss1331
    innodb-5.0-ss1333
    innodb-5.0-ss1341
    
    Revision r1317:
    branches/5.0: Port r1316 from trunk:
    
    Prevent ALTER TABLE ... MODIFY ... NOT NULL on columns for which
    there is a foreign key constraint ON ... SET NULL.  (Bug #25927)
    
    dict_foreign_find_index(): Add paramettter check_null.
    
    dict_foreign_add_to_cache(): Do not allow ON DELETE SET NULL
    or ON UPDATE SET NULL if any of the referencing columns are declared NOT NULL.

  innobase/include/rem0rec.ic@1.28, 2007-03-22 14:40:46-06:00, tsmith@siva.hindu.god +3 -0
    NULL MERGE this to 5.1
    
    Apply the following InnoDB snapshots:
    innodb-5.0-ss1319
    innodb-5.0-ss1331
    innodb-5.0-ss1333
    innodb-5.0-ss1341
    
    Revision r1339:
    branches/5.0: Merge r1338 from trunk:
    
    rec_offs_nth_size(): Treat n==0 as a special case.  (Bug #26835)

  innobase/include/sync0sync.ic@1.20, 2007-03-22 14:40:46-06:00, tsmith@siva.hindu.god +13 -24
    NULL MERGE this to 5.1
    
    Apply the following InnoDB snapshots:
    innodb-5.0-ss1319
    innodb-5.0-ss1331
    innodb-5.0-ss1333
    innodb-5.0-ss1341
    
    Revision r1293:
    branches/5.0: Fixed inline asm code, it didn't work with GCC > ver 3.x.

  innobase/lock/lock0lock.c@1.70, 2007-03-22 14:40:46-06:00, tsmith@siva.hindu.god +21 -9
    NULL MERGE this to 5.1
    
    Apply the following InnoDB snapshots:
    innodb-5.0-ss1319
    innodb-5.0-ss1331
    innodb-5.0-ss1333
    innodb-5.0-ss1341
    
    Revision r1331:
    branches/5.0: Merge r1330 from trunk:
    
    lock_deadlock_recursive(): When the search depth or length is exceeded,
    rewind lock_latest_err_file and display the two transactions at the
    point of aborting the search.  (Bug #25494)
    
    
    Revision r1333:
    branches/5.0: Merge r1332 from trunk:
    
    lock_deadlock_recursive(): When aborting the search, display a note
    regardless of start->undo_no.  Otherwise, aborted searches may show
    up as genuine deadlocks.  This mistake was made in r1330.

  innobase/srv/srv0srv.c@1.98, 2007-03-22 14:40:46-06:00, tsmith@siva.hindu.god +3 -3
    NULL MERGE this to 5.1
    
    Apply the following InnoDB snapshots:
    innodb-5.0-ss1319
    innodb-5.0-ss1331
    innodb-5.0-ss1333
    innodb-5.0-ss1341
    
    Revision r1261:
    branches/5.0: Fix for Bug# 23666. On Windows ut_usectime returns secs 
    and usecs relative to the UNIX epoch (which is Jan, 1 1970).

  innobase/ut/ut0ut.c@1.33, 2007-03-22 14:40:46-06:00, tsmith@siva.hindu.god +51 -8
    NULL MERGE this to 5.1
    
    Apply the following InnoDB snapshots:
    innodb-5.0-ss1319
    innodb-5.0-ss1331
    innodb-5.0-ss1333
    innodb-5.0-ss1341
    
    Revision r1261:
    branches/5.0: Fix for Bug# 23666. On Windows ut_usectime returns secs 
    and usecs relative to the UNIX epoch (which is Jan, 1 1970).

  mysql-test/r/innodb.result@1.166, 2007-03-22 14:40:46-06:00, tsmith@siva.hindu.god +18 -0
    NULL MERGE this to 5.1
    
    Apply the following InnoDB snapshots:
    innodb-5.0-ss1319
    innodb-5.0-ss1331
    innodb-5.0-ss1333
    innodb-5.0-ss1341
    
    Revision r1319:
    branches/5.0: Port r1318 from trunk:
    
    Add a test case for r1316 (Bug #25927).
    
    
    Revision r1328:
    branches/5.0: mysql-test: Merge changes from MySQL AB.
    
    
    Revision r1341:
    branches/5.0: Merge r1340 from trunk:
    
    innodb.test, innodb.result: Add test case for Bug #26835.
    The bug could be reproduced as follows:
    
    Define a table so that the first column of the clustered index is
    a VARCHAR or a UTF-8 CHAR in a collation where sequences of bytes
    of differing length are considered equivalent.
    
    Insert and delete a record.  Before the delete-marked record is
    purged, insert another record whose first column is of different
    length but equivalent to the first record.  Under certain conditions,
    the insertion can be incorrectly performed as update-in-place.
    
    Likewise, an operation that could be done as update-in-place can
    unnecessarily be performed as delete and insert, but that would not
    cause corruption but merely degraded performance.
    
    Revision r1284:
    Merge changes from MySQL AB:
    
    ChangeSet
      2007/01/24 14:49:36+04:00 holyfoot@mysql.com 
      bug #22682 Test fails --without-geometry
      geometry dependent parts moved to proper .test files
    
    mysql-test/r/innodb.result
      2007/01/24 14:49:34+04:00 holyfoot@mysql.com +0 -2
      result fixed
    
    mysql-test/r/innodb_gis.result
      2007/01/24 14:49:34+04:00 holyfoot@mysql.com +2 -0
      result fixed
    
    mysql-test/t/innodb.test
      2007/01/24 14:49:34+04:00 holyfoot@mysql.com +0 -6
      HAVE_GEOMETRY dependent part moved to innodb_gis.test
    
    mysql-test/t/innodb_gis.test
      2007/01/24 14:49:35+04:00 holyfoot@mysql.com +6 -0
      HAVE_GEOMETRY dependent part moved here from innodb.test
    
    
    Revision r1186:
    dict_load_foreign(): Use a local variable instead of the 10-bit field
    foreign->n_fields in order to preserve ON UPDATE CASCADE and
    ON DELETE CASCADE flags.  For some reason, gcc does not warn about
    shifting a 10-bit field to right by 24 bits.  (Bug #24741)
    
    This bug was introduced while reducing the memory footprint of the
    InnoDB data dictionary (Bug #20877).
    
    innodb.test, innodb.result: Add a test case.
    
    
    Revision r1318:
    Add a test case for r1316 (Bug #25927).
    
    
    Revision r1340:
    innodb.test, innodb.result: Add test case for Bug #26835.
    The bug could be reproduced as follows:
    
    Define a table so that the first column of the clustered index is
    a VARCHAR or a UTF-8 CHAR in a collation where sequences of bytes
    of differing length are considered equivalent.
    
    Insert and delete a record.  Before the delete-marked record is
    purged, insert another record whose first column is of different
    length but equivalent to the first record.  Under certain conditions,
    the insertion can be incorrectly performed as update-in-place.
    
    Likewise, an operation that could be done as update-in-place can
    unnecessarily be performed as delete and insert, but that would not
    cause corruption but merely degraded performance.

  mysql-test/t/innodb.test@1.139, 2007-03-22 14:40:46-06:00, tsmith@siva.hindu.god +28 -0
    NULL MERGE this to 5.1
    
    Apply the following InnoDB snapshots:
    innodb-5.0-ss1319
    innodb-5.0-ss1331
    innodb-5.0-ss1333
    innodb-5.0-ss1341
    
    Revision r1279:
    branches/5.0: Merge changes from MySQL AB:
    
    ChangeSet
      2006/11/20 22:42:06+02:00 monty@mysql.com 
      Remove compiler warnings
      (Mostly in DBUG_PRINT() and unused arguments)
      Fixed bug in query cache when used with traceing (--with-debug)
      Fixed memory leak in mysqldump
      Removed warnings from mysqltest scripts (replaced -- with #)
    
    mysql-test/t/innodb.test
      2006/11/20 22:41:41+02:00 monty@mysql.com +1 -1
      Remove mysqltest warnings
    
    sql/ha_innodb.cc
      2006/11/20 22:41:51+02:00 monty@mysql.com +2 -2
      Fixed compiler warning
    
    
    Revision r1319:
    branches/5.0: Port r1318 from trunk:
    
    Add a test case for r1316 (Bug #25927).
    
    
    Revision r1328:
    branches/5.0: mysql-test: Merge changes from MySQL AB.
    
    
    Revision r1341:
    branches/5.0: Merge r1340 from trunk:
    
    innodb.test, innodb.result: Add test case for Bug #26835.
    The bug could be reproduced as follows:
    
    Define a table so that the first column of the clustered index is
    a VARCHAR or a UTF-8 CHAR in a collation where sequences of bytes
    of differing length are considered equivalent.
    
    Insert and delete a record.  Before the delete-marked record is
    purged, insert another record whose first column is of different
    length but equivalent to the first record.  Under certain conditions,
    the insertion can be incorrectly performed as update-in-place.
    
    Likewise, an operation that could be done as update-in-place can
    unnecessarily be performed as delete and insert, but that would not
    cause corruption but merely degraded performance.
    
    Revision r1284:
    Merge changes from MySQL AB:
    
    ChangeSet
      2007/01/24 14:49:36+04:00 holyfoot@mysql.com 
      bug #22682 Test fails --without-geometry
      geometry dependent parts moved to proper .test files
    
    mysql-test/r/innodb.result
      2007/01/24 14:49:34+04:00 holyfoot@mysql.com +0 -2
      result fixed
    
    mysql-test/r/innodb_gis.result
      2007/01/24 14:49:34+04:00 holyfoot@mysql.com +2 -0
      result fixed
    
    mysql-test/t/innodb.test
      2007/01/24 14:49:34+04:00 holyfoot@mysql.com +0 -6
      HAVE_GEOMETRY dependent part moved to innodb_gis.test
    
    mysql-test/t/innodb_gis.test
      2007/01/24 14:49:35+04:00 holyfoot@mysql.com +6 -0
      HAVE_GEOMETRY dependent part moved here from innodb.test
    
    
    Revision r1283:
    Merge changes from MySQL AB:
    
    ChangeSet
      2007/01/22 18:42:52+02:00 monty@mysql.com 
      Give warnings for unused objects
      Changed error message to be compatible with old error file
      Added new error message for new DUP_ENTRY syntax
    
    mysql-test/t/innodb.test
      2007/01/22 18:42:49+02:00 monty@mysql.com +14 -14
      Changed to use new error message
    
    
    Revision r1186:
    dict_load_foreign(): Use a local variable instead of the 10-bit field
    foreign->n_fields in order to preserve ON UPDATE CASCADE and
    ON DELETE CASCADE flags.  For some reason, gcc does not warn about
    shifting a 10-bit field to right by 24 bits.  (Bug #24741)
    
    This bug was introduced while reducing the memory footprint of the
    InnoDB data dictionary (Bug #20877).
    
    innodb.test, innodb.result: Add a test case.
    
    
    Revision r1318:
    Add a test case for r1316 (Bug #25927).
    
    
    Revision r1329:
    Merge changes from MySQL AB to mysql-test directives.
    The results are not affected.
    
    
    Revision r1340:
    innodb.test, innodb.result: Add test case for Bug #26835.
    The bug could be reproduced as follows:
    
    Define a table so that the first column of the clustered index is
    a VARCHAR or a UTF-8 CHAR in a collation where sequences of bytes
    of differing length are considered equivalent.
    
    Insert and delete a record.  Before the delete-marked record is
    purged, insert another record whose first column is of different
    length but equivalent to the first record.  Under certain conditions,
    the insertion can be incorrectly performed as update-in-place.
    
    Likewise, an operation that could be done as update-in-place can
    unnecessarily be performed as delete and insert, but that would not
    cause corruption but merely degraded performance.

  sql/ha_innodb.cc@1.310, 2007-03-22 14:40:46-06:00, tsmith@siva.hindu.god +9 -0
    NULL MERGE this to 5.1
    
    Apply the following InnoDB snapshots:
    innodb-5.0-ss1319
    innodb-5.0-ss1331
    innodb-5.0-ss1333
    innodb-5.0-ss1341
    
    Revision r1279:
    branches/5.0: Merge changes from MySQL AB:
    
    ChangeSet
      2006/11/20 22:42:06+02:00 monty@mysql.com 
      Remove compiler warnings
      (Mostly in DBUG_PRINT() and unused arguments)
      Fixed bug in query cache when used with traceing (--with-debug)
      Fixed memory leak in mysqldump
      Removed warnings from mysqltest scripts (replaced -- with #)
    
    mysql-test/t/innodb.test
      2006/11/20 22:41:41+02:00 monty@mysql.com +1 -1
      Remove mysqltest warnings
    
    sql/ha_innodb.cc
      2006/11/20 22:41:51+02:00 monty@mysql.com +2 -2
      Fixed compiler warning
    
    
    Revision r1280:
    branches/5.0: Merge a change from MySQL AB:
    
    ChangeSet
      2006/11/30 18:25:05+02:00 monty@mysql.com 
      Fixed portability issue in my_thr_init.c (was added in my last push)
      
      Fixed compiler warnings (detected by VC++):
      - Removed not used variables
      - Added casts
      - Fixed wrong assignments to bool
      - Fixed wrong calls with bool arguments
      - Added missing argument to store(longlong), which caused wrong store
      method to be called.
    
    sql/ha_innodb.cc
      2006/11/30 18:24:53+02:00 monty@mysql.com +0 -1
      Removed not used variable
    
    
    Revision r1260:
    branches/5.0: Fix for Bug# 21409. At low transaction isolation levels
    we let each consistent read set its own snapshot.
    
    
    Revision r1326:
    branches/5.0: Merge code from MySQL AB:
    
    ChangeSet@1.2417.3.1  2007-02-22 16:59:57+02:00  monty@mysql.fi
    
    Fixed compiler warnings (for linux and win32 and win64)

ChangeSet@1.2392.120.8, 2007-03-22 23:13:40+03:00, evgen@moonbone.local +1 -0
  sql_view.cc:
    Post-fix for bug#26813.

  sql/sql_view.cc@1.107, 2007-03-22 23:12:41+03:00, evgen@moonbone.local +2 -0
    Post-fix for bug#26813.

ChangeSet@1.2392.126.1, 2007-03-22 22:05:19+03:00, evgen@moonbone.local +3 -0
  Bug#26813: The SUPER privilege is wrongly required to alter a view created by
  another user.
  
  When the DEFINER clause isn't specified in the ALTER statement then it's loaded
  from the view definition. If the definer differs from the current user then
  the error is thrown because only a super-user can set other users as a definers.
  
  Now if the DEFINER clause is omitted in the ALTER VIEW statement then the
  definer from the original view is used without check.

  mysql-test/r/view_grant.result@1.23, 2007-03-22 22:04:11+03:00, evgen@moonbone.local +21 -0
    Added a test case for the bug#27006: The SUPER privilege is wrongly required
    to alter a view created by another user.

  mysql-test/t/view_grant.test@1.22, 2007-03-22 22:04:07+03:00, evgen@moonbone.local +31 -0
    Added a test case for the bug#27006: The SUPER privilege is wrongly required
    to alter a view created by another user.

  sql/sql_view.cc@1.106, 2007-03-22 22:04:19+03:00, evgen@moonbone.local +8 -6
    Bug#26813: The SUPER privilege is wrongly required to alter a view created by
    another user.
    Now if the DEFINER clause is omitted in the ALTER VIEW statement then the
    definer from the original view is used without check.

ChangeSet@1.1616.3002.2, 2007-03-22 19:43:15+01:00, kent@mysql.com +3 -0
  .del-fill_func_tables.sh:
    Delete: scripts/fill_func_tables.sh
  .del-fill_help_tables.sh:
    Delete: scripts/fill_help_tables.sh
  .del-internals.texi:
    Delete: Docs/internals.texi

  BitKeeper/deleted/.del-fill_func_tables.sh@1.2.2.2, 2007-03-22 18:32:47+01:00, kent@mysql.com +0 -0
    Delete: scripts/fill_func_tables.sh

  BitKeeper/deleted/.del-fill_help_tables.sh@1.16.1.1, 2007-03-22 18:32:47+01:00, kent@mysql.com +0 -0
    Delete: scripts/fill_help_tables.sh

  BitKeeper/deleted/.del-internals.texi@1.2, 2007-03-22 18:14:04+01:00, kent@mysql.com +0 -0
    Delete: Docs/internals.texi

ChangeSet@1.1346.1.868, 2007-03-22 19:38:56+01:00, kent@mysql.com +74 -0
  Deleted directories
    Docs/Books/
    Docs/MySQL-logos/
  Deleted files
    Docs/Tutorial-MySQL-final.txt
    Docs/bk.txt
    Docs/Support/.cvsignore
    Docs/Support/colspec-fix.pl
    Docs/Support/docbook-fixup.pl
    Docs/Support/docbook-prefix.pl
    Docs/Support/docbook-split
    Docs/Support/make-docbook
    Docs/Support/make-makefile
    Docs/Support/test-make-manual
    Docs/Support/test-make-manual-de
    Docs/Support/trivial-makeinfo-4.0c.patch
    Docs/Support/xwf
  Deleted file now in internals main text
    Docs/my_sys.txt
  Deleted file now in internals svn tree
    Docs/net_doc.txt
  Removed obsolete entries
    Docs/.cvsignore
  Added note that info is obsolete
    Docs/linuxthreads.txt

  BitKeeper/deleted/.del-.cvsignore@1.3, 2007-03-22 19:29:56+01:00, kent@mysql.com +0 -0
    Delete: Docs/Support/.cvsignore

  BitKeeper/deleted/.del-Tutorial-MySQL-final.txt@1.3, 2007-03-22 18:55:49+01:00, kent@mysql.com +0 -0
    Delete: Docs/Tutorial-MySQL-final.txt

  BitKeeper/deleted/.del-algor.eps~1a57aff065918206@1.2, 2007-03-22 18:55:19+01:00, kent@mysql.com +0 -0
    Delete: Docs/Books/algor.eps

  BitKeeper/deleted/.del-algor.gif@1.2, 2007-03-22 18:55:19+01:00, kent@mysql.com +0 -0
    Delete: Docs/Books/algor.gif

  BitKeeper/deleted/.del-algor.txt@1.2, 2007-03-22 18:55:19+01:00, kent@mysql.com +0 -0
    Delete: Docs/Books/algor.txt

  BitKeeper/deleted/.del-bk.txt@1.8, 2007-03-22 19:28:56+01:00, kent@mysql.com +0 -0
    Delete: Docs/bk.txt

  BitKeeper/deleted/.del-colspec-fix.pl@1.5.1.1, 2007-03-22 18:54:53+01:00, kent@mysql.com +0 -0
    Delete: Docs/Support/colspec-fix.pl

  BitKeeper/deleted/.del-dbi.eps~7b1032f98de7736d@1.2, 2007-03-22 18:55:19+01:00, kent@mysql.com +0 -0
    Delete: Docs/Books/dbi.eps

  BitKeeper/deleted/.del-dbi.gif@1.2, 2007-03-22 18:55:19+01:00, kent@mysql.com +0 -0
    Delete: Docs/Books/dbi.gif

  BitKeeper/deleted/.del-dbi.txt@1.2, 2007-03-22 18:55:19+01:00, kent@mysql.com +0 -0
    Delete: Docs/Books/dbi.txt

  BitKeeper/deleted/.del-docbook-fixup.pl@1.16.1.1, 2007-03-22 18:54:53+01:00, kent@mysql.com +0 -0
    Delete: Docs/Support/docbook-fixup.pl

  BitKeeper/deleted/.del-docbook-prefix.pl@1.1.1.1, 2007-03-22 18:54:53+01:00, kent@mysql.com +0 -0
    Delete: Docs/Support/docbook-prefix.pl

  BitKeeper/deleted/.del-docbook-split@1.3.1.1, 2007-03-22 18:54:53+01:00, kent@mysql.com +0 -0
    Delete: Docs/Support/docbook-split

  BitKeeper/deleted/.del-dubois.eps~f24e09a7fa420436@1.2, 2007-03-22 18:55:19+01:00, kent@mysql.com +0 -0
    Delete: Docs/Books/dubois.eps

  BitKeeper/deleted/.del-dubois.gif@1.2, 2007-03-22 18:55:19+01:00, kent@mysql.com +0 -0
    Delete: Docs/Books/dubois.gif

  BitKeeper/deleted/.del-dubois.txt@1.2, 2007-03-22 18:55:19+01:00, kent@mysql.com +0 -0
    Delete: Docs/Books/dubois.txt

  BitKeeper/deleted/.del-ecomm.eps~17833026ebd7656@1.2, 2007-03-22 18:55:19+01:00, kent@mysql.com +0 -0
    Delete: Docs/Books/ecomm.eps

  BitKeeper/deleted/.del-ecomm.gif@1.2, 2007-03-22 18:55:19+01:00, kent@mysql.com +0 -0
    Delete: Docs/Books/ecomm.gif

  BitKeeper/deleted/.del-ecomm.txt@1.2, 2007-03-22 18:55:19+01:00, kent@mysql.com +0 -0
    Delete: Docs/Books/ecomm.txt

  BitKeeper/deleted/.del-in_21.eps~8150d06653dab178@1.2, 2007-03-22 18:55:19+01:00, kent@mysql.com +0 -0
    Delete: Docs/Books/in_21.eps

  BitKeeper/deleted/.del-in_21.gif@1.2, 2007-03-22 18:55:19+01:00, kent@mysql.com +0 -0
    Delete: Docs/Books/in_21.gif

  BitKeeper/deleted/.del-in_21.txt@1.2, 2007-03-22 18:55:19+01:00, kent@mysql.com +0 -0
    Delete: Docs/Books/in_21.txt

  BitKeeper/deleted/.del-make-docbook@1.5.1.1, 2007-03-22 18:54:53+01:00, kent@mysql.com +0 -0
    Delete: Docs/Support/make-docbook

  BitKeeper/deleted/.del-make-makefile@1.2.1.1, 2007-03-22 18:54:53+01:00, kent@mysql.com +0 -0
    Delete: Docs/Support/make-makefile

  BitKeeper/deleted/.del-manual.eps~1c2ebcea50b4840c@1.2, 2007-03-22 18:55:19+01:00, kent@mysql.com +0 -0
    Delete: Docs/Books/manual.eps

  BitKeeper/deleted/.del-manual.gif@1.2, 2007-03-22 18:55:19+01:00, kent@mysql.com +0 -0
    Delete: Docs/Books/manual.gif

  BitKeeper/deleted/.del-manual.txt@1.2, 2007-03-22 18:55:19+01:00, kent@mysql.com +0 -0
    Delete: Docs/Books/manual.txt

  BitKeeper/deleted/.del-msql.eps~f3801b9d166ae4fc@1.2, 2007-03-22 18:55:19+01:00, kent@mysql.com +0 -0
    Delete: Docs/Books/msql.eps

  BitKeeper/deleted/.del-msql.gif@1.2, 2007-03-22 18:55:19+01:00, kent@mysql.com +0 -0
    Delete: Docs/Books/msql.gif

  BitKeeper/deleted/.del-msql.txt@1.2, 2007-03-22 18:55:19+01:00, kent@mysql.com +0 -0
    Delete: Docs/Books/msql.txt

  BitKeeper/deleted/.del-my_sys.txt@1.2, 2007-03-22 19:13:47+01:00, kent@mysql.com +0 -0
    Delete: Docs/my_sys.txt

  BitKeeper/deleted/.del-mysql-01.gif@1.3, 2007-03-22 18:55:44+01:00, kent@mysql.com +0 -0
    Delete: Docs/MySQL-logos/mysql-01.gif

  BitKeeper/deleted/.del-mysql-02.gif@1.3, 2007-03-22 18:55:44+01:00, kent@mysql.com +0 -0
    Delete: Docs/MySQL-logos/mysql-02.gif

  BitKeeper/deleted/.del-mysql-03.gif@1.3, 2007-03-22 18:55:44+01:00, kent@mysql.com +0 -0
    Delete: Docs/MySQL-logos/mysql-03.gif

  BitKeeper/deleted/.del-mysql-04.gif@1.3, 2007-03-22 18:55:44+01:00, kent@mysql.com +0 -0
    Delete: Docs/MySQL-logos/mysql-04.gif

  BitKeeper/deleted/.del-mysql-05.gif@1.3, 2007-03-22 18:55:44+01:00, kent@mysql.com +0 -0
    Delete: Docs/MySQL-logos/mysql-05.gif

  BitKeeper/deleted/.del-mysql-06.gif@1.3, 2007-03-22 18:55:44+01:00, kent@mysql.com +0 -0
    Delete: Docs/MySQL-logos/mysql-06.gif

  BitKeeper/deleted/.del-mysql-07.gif@1.3, 2007-03-22 18:55:44+01:00, kent@mysql.com +0 -0
    Delete: Docs/MySQL-logos/mysql-07.gif

  BitKeeper/deleted/.del-mysql-08.gif@1.3, 2007-03-22 18:55:44+01:00, kent@mysql.com +0 -0
    Delete: Docs/MySQL-logos/mysql-08.gif

  BitKeeper/deleted/.del-mysql-09.gif@1.3, 2007-03-22 18:55:44+01:00, kent@mysql.com +0 -0
    Delete: Docs/MySQL-logos/mysql-09.gif

  BitKeeper/deleted/.del-mysql-10.gif@1.3, 2007-03-22 18:55:44+01:00, kent@mysql.com +0 -0
    Delete: Docs/MySQL-logos/mysql-10.gif

  BitKeeper/deleted/.del-mysql-11.gif@1.3, 2007-03-22 18:55:44+01:00, kent@mysql.com +0 -0
    Delete: Docs/MySQL-logos/mysql-11.gif

  BitKeeper/deleted/.del-mysql-12.gif@1.3, 2007-03-22 18:55:44+01:00, kent@mysql.com +0 -0
    Delete: Docs/MySQL-logos/mysql-12.gif

  BitKeeper/deleted/.del-mysql-13.gif@1.3, 2007-03-22 18:55:44+01:00, kent@mysql.com +0 -0
    Delete: Docs/MySQL-logos/mysql-13.gif

  BitKeeper/deleted/.del-mysql-14.gif@1.3, 2007-03-22 18:55:44+01:00, kent@mysql.com +0 -0
    Delete: Docs/MySQL-logos/mysql-14.gif

  BitKeeper/deleted/.del-mysql-15.gif@1.3, 2007-03-22 18:55:44+01:00, kent@mysql.com +0 -0
    Delete: Docs/MySQL-logos/mysql-15.gif

  BitKeeper/deleted/.del-mysql-16.gif@1.3, 2007-03-22 18:55:44+01:00, kent@mysql.com +0 -0
    Delete: Docs/MySQL-logos/mysql-16.gif

  BitKeeper/deleted/.del-mysql-17.gif@1.3, 2007-03-22 18:55:44+01:00, kent@mysql.com +0 -0
    Delete: Docs/MySQL-logos/mysql-17.gif

  BitKeeper/deleted/.del-mysql-compatible.jpg@1.3, 2007-03-22 18:55:44+01:00, kent@mysql.com +0 -0
    Delete: Docs/MySQL-logos/mysql-compatible.jpg

  BitKeeper/deleted/.del-mysql_anim-01.gif@1.3, 2007-03-22 18:55:44+01:00, kent@mysql.com +0 -0
    Delete: Docs/MySQL-logos/mysql_anim-01.gif

  BitKeeper/deleted/.del-mysql_anim-02.gif@1.3, 2007-03-22 18:55:44+01:00, kent@mysql.com +0 -0
    Delete: Docs/MySQL-logos/mysql_anim-02.gif

  BitKeeper/deleted/.del-mysql_anim-03.gif@1.3, 2007-03-22 18:55:44+01:00, kent@mysql.com +0 -0
    Delete: Docs/MySQL-logos/mysql_anim-03.gif

  BitKeeper/deleted/.del-mysql_anim-04.gif@1.3, 2007-03-22 18:55:44+01:00, kent@mysql.com +0 -0
    Delete: Docs/MySQL-logos/mysql_anim-04.gif

  BitKeeper/deleted/.del-mysql_anim-05.gif@1.3, 2007-03-22 18:55:44+01:00, kent@mysql.com +0 -0
    Delete: Docs/MySQL-logos/mysql_anim-05.gif

  BitKeeper/deleted/.del-mysql_anim-06.gif@1.3, 2007-03-22 18:55:44+01:00, kent@mysql.com +0 -0
    Delete: Docs/MySQL-logos/mysql_anim-06.gif

  BitKeeper/deleted/.del-net_doc.txt@1.3.1.1, 2007-03-22 19:05:42+01:00, kent@mysql.com +0 -0
    Delete: Docs/net_doc.txt

  BitKeeper/deleted/.del-prof.eps~1f54d9a56eb2b908@1.2, 2007-03-22 18:55:19+01:00, kent@mysql.com +0 -0
    Delete: Docs/Books/prof.eps

  BitKeeper/deleted/.del-prof.gif@1.2, 2007-03-22 18:55:19+01:00, kent@mysql.com +0 -0
    Delete: Docs/Books/prof.gif

  BitKeeper/deleted/.del-prof.txt@1.2, 2007-03-22 18:55:19+01:00, kent@mysql.com +0 -0
    Delete: Docs/Books/prof.txt

  BitKeeper/deleted/.del-pthreads.eps~2ca8ff2d1181b2c0@1.2, 2007-03-22 18:55:19+01:00, kent@mysql.com +0 -0
    Delete: Docs/Books/pthreads.eps

  BitKeeper/deleted/.del-pthreads.gif@1.2, 2007-03-22 18:55:19+01:00, kent@mysql.com +0 -0
    Delete: Docs/Books/pthreads.gif

  BitKeeper/deleted/.del-pthreads.txt@1.2, 2007-03-22 18:55:19+01:00, kent@mysql.com +0 -0
    Delete: Docs/Books/pthreads.txt

  BitKeeper/deleted/.del-realmen.eps~cc022325d3cb045@1.2, 2007-03-22 18:55:19+01:00, kent@mysql.com +0 -0
    Delete: Docs/Books/realmen.eps

  BitKeeper/deleted/.del-realmen.gif@1.2, 2007-03-22 18:55:19+01:00, kent@mysql.com +0 -0
    Delete: Docs/Books/realmen.gif

  BitKeeper/deleted/.del-realmen.txt@1.2, 2007-03-22 18:55:19+01:00, kent@mysql.com +0 -0
    Delete: Docs/Books/realmen.txt

  BitKeeper/deleted/.del-sql-99.eps~f85c06de7a016c7d@1.2, 2007-03-22 18:55:19+01:00, kent@mysql.com +0 -0
    Delete: Docs/Books/sql-99.eps

  BitKeeper/deleted/.del-sql-99.gif@1.2, 2007-03-22 18:55:19+01:00, kent@mysql.com +0 -0
    Delete: Docs/Books/sql-99.gif

  BitKeeper/deleted/.del-sql-99.txt@1.2, 2007-03-22 18:55:19+01:00, kent@mysql.com +0 -0
    Delete: Docs/Books/sql-99.txt

  BitKeeper/deleted/.del-test-make-manual@1.7.1.1, 2007-03-22 18:54:53+01:00, kent@mysql.com +0 -0
    Delete: Docs/Support/test-make-manual

  BitKeeper/deleted/.del-test-make-manual-de@1.1.1.1, 2007-03-22 18:54:53+01:00, kent@mysql.com +0 -0
    Delete: Docs/Support/test-make-manual-de

  BitKeeper/deleted/.del-trivial-makeinfo-4.0c.patch@1.2, 2007-03-22 18:54:53+01:00, kent@mysql.com +0 -0
    Delete: Docs/Support/trivial-makeinfo-4.0c.patch

  BitKeeper/deleted/.del-xwf@1.1.1.1, 2007-03-22 18:55:05+01:00, kent@mysql.com +0 -0
    Delete: Docs/Support/xwf

  Docs/.cvsignore@1.11, 2007-03-22 19:32:33+01:00, kent@mysql.com +1 -36
    Removed obsolete entries

  Docs/linuxthreads.txt@1.3, 2007-03-22 19:33:08+01:00, kent@mysql.com +2 -0
    Added note info is obsolete

ChangeSet@1.2398.3.1, 2007-03-22 13:35:29-04:00, Damien@damiendev. +3 -0
  Bug#26346: stack + buffer overrun in mysqldump
  
  Fixes to buffer overlows from long command line args, and unchecked dyn_str return codes. Also light refactoring.

  client/mysqldump.c@1.258, 2007-03-22 13:35:24-04:00, Damien@damiendev. +323 -229
    Bug#26346 stack + buffer overrun in mysqldump

  mysql-test/r/mysqldump.result@1.120, 2007-03-22 13:35:25-04:00, Damien@damiendev. +7 -12
    Bug#26346 stack + buffer overrun in mysqldump

  mysql-test/t/mysqldump.test@1.111, 2007-03-22 13:35:25-04:00, Damien@damiendev. +24 -0
    Bug#26346 stack + buffer overrun in mysqldump

ChangeSet@1.2392.124.1, 2007-03-22 18:44:16+02:00, gkodinov@magare.gmz +3 -0
  Bug #26207: When making the key image to use
   in index search MySQL was not explicitly
   suppressing warnings. And if the context 
   happens to enable warnings (e.g. INSERT ..
   SELECT) the warnings resulting from converting 
   the data the key is compared to are 
   reported to the client.
   Fixed by suppressing warnings when converting
   the data to the same type as the key parts.

  mysql-test/r/insert_select.result@1.46, 2007-03-22 18:44:15+02:00, gkodinov@magare.gmz +29 -0
    Bug #26207: test case

  mysql-test/t/insert_select.test@1.38, 2007-03-22 18:44:15+02:00, gkodinov@magare.gmz +26 -1
    Bug #26207: test case

  sql/sql_select.h@1.115.1.1, 2007-03-22 18:44:15+02:00, gkodinov@magare.gmz +41 -12
    Bug #26207: supress warnings when converting
      data of the same type to key buffer format.

ChangeSet@1.2392.123.1, 2007-03-22 16:53:37+01:00, kent@mysql.com +3 -0
  Makefile.am:
    Don't install benchmark executable
  CMakeLists.txt:
    Handle CMAKE_C_FLAGS_RELWITHDEBINFO and CMAKE_CXX_FLAGS_RELWITHDEBINFO

  CMakeLists.txt@1.6, 2007-03-22 16:53:25+01:00, kent@mysql.com +8 -0
    Handle CMAKE_C_FLAGS_RELWITHDEBINFO and CMAKE_CXX_FLAGS_RELWITHDEBINFO

  extra/yassl/taocrypt/benchmark/Makefile.am@1.6, 2007-03-20 22:05:11+01:00, kent@mysql.com +1 -1
    Don't install benchmark executable

  mysys/CMakeLists.txt@1.5, 2007-03-22 16:53:25+01:00, kent@mysql.com +2 -0
    Handle CMAKE_C_FLAGS_RELWITHDEBINFO and CMAKE_CXX_FLAGS_RELWITHDEBINFO

ChangeSet@1.2392.105.2, 2007-03-22 15:07:32+01:00, guilhem@gbichot3.local +7 -0
  - renaming TMP_TABLE to NON_TRANSACTIONAL_TMP_TABLE because this is
  what it actually means (Monty approved the renaming)
  - correcting description of transaction_alloc command-line options
  (our manual is correct)
  - fix for a failure of rpl_trigger.

  mysql-test/t/rpl_misc_functions.test@1.7, 2007-03-22 15:07:29+01:00, guilhem@gbichot3.local +2 -0
    test was cleaning up only on slave, but it's also needed on master,
    otherwise it influences rpl_trigger.test

  sql/lock.cc@1.95, 2007-03-22 15:07:29+01:00, guilhem@gbichot3.local +4 -4
    clearer name

  sql/mysqld.cc@1.596.1.1, 2007-03-22 15:07:29+01:00, guilhem@gbichot3.local +2 -2
    I checked the code that those two variables are not about binlogging
    but about the size of the transaction's memroot which is used
    to create savepoint structures and to store list of tables to be invalidated
    (for NDB). The manual has a correct description, no need to fix it.

  sql/sql_base.cc@1.370.2.1, 2007-03-22 15:07:29+01:00, guilhem@gbichot3.local +1 -1
    clearer name

  sql/sql_derived.cc@1.82, 2007-03-22 15:07:30+01:00, guilhem@gbichot3.local +1 -1
    clearer name

  sql/sql_select.cc@1.498.2.1, 2007-03-22 15:07:30+01:00, guilhem@gbichot3.local +1 -1
    clearer name

  sql/table.h@1.140, 2007-03-22 15:07:30+01:00, guilhem@gbichot3.local +2 -1
    clearer name: TMP_TABLE is used for non-transactional tables.

ChangeSet@1.2392.120.5, 2007-03-22 14:58:43+01:00, mhansson@linux-st28.site +1 -0
  Bug#24791: Union with AVG-groups generates wrong results
  
  Patch appled after doing a pull from the team tree. Additional tests had to be
  fixed

  mysql-test/r/union.result@1.91, 2007-03-22 14:58:37+01:00, mhansson@linux-st28.site +2 -2
    Bug 24791
    
    The tests for temporary tables have been fixed. Since the call to 
    display_length(Item) was removed from the constructor for Item_type_holder, items 
    in temporary tables keep the original values of the items, rather than the magic
    numbers supplied by display_length.

ChangeSet@1.2377.51.5, 2007-03-22 12:42:13+01:00, tomas@whalegate.ndb.mysql.com +2 -0
  Bug #27320 ndb handler does not reset extra flags on reset()
  - make sure all extra flags are reset

  sql/ha_ndbcluster.cc@1.291.5.3, 2007-03-22 12:42:11+01:00, tomas@whalegate.ndb.mysql.com +16 -2
    Bug #27320 ndb handler does not reset extra flags on reset()
    - make sure all extra flags are reset

  sql/ha_ndbcluster.h@1.108.2.1, 2007-03-22 12:42:11+01:00, tomas@whalegate.ndb.mysql.com +1 -0
    Bug #27320 ndb handler does not reset extra flags on reset()
    - make sure all extra flags are reset

ChangeSet@1.2216.71.57, 2007-03-22 11:12:18+01:00, jonas@perch.ndb.mysql.com +1 -0
  ndb -
    fix test prg

  ndb/test/ndbapi/testNodeRestart.cpp@1.24.1.7, 2007-03-22 11:12:17+01:00, jonas@perch.ndb.mysql.com +1 -1
    fix test prg

ChangeSet@1.2392.121.1, 2007-03-22 10:56:47+01:00, mhansson@linux-st28.site +7 -0
  Bug #24791: Union with AVG-groups generates wrong results
  
  The problem in this bug is when we create temporary tables. When
  temporary tables are created for unions, there is some 
  inferrence being carried out regarding the type of the column.
  Whenever this column type is inferred to be REAL (i.e. FLOAT or
  DOUBLE), MySQL will always try to maintain exact precision, and
  if that is not possible (there are hardware limits, since FLOAT
  and DOUBLE are stored as approximate values) will switch to
  using approximate values. The problem here is that at this point
  the information about number of significant digits is not 
  available. Furthermore, the number of significant digits should
  be increased for the AVG function, however, this was not properly 
  handled. There are 4 parts to the problem:
  
  #1: DOUBLE and FLOAT fields don't display their proper display 
  lengths in max_display_length(). This is hard-coded as 53 for 
  DOUBLE and 24 for FLOAT. Now changed to instead return the 
  field_length.
  
  #2: Type holders for temporary tables do not preserve the 
  max_length of the Item's from which they are created, and is 
  instead reverted to the 53 and 24 from above. This causes 
  *all* fields to get non-fixed significant digits.
  
  #3: AVG function does not update max_length (display length)
  when updating number of decimals.
  
  #4: The function that switches to non-fixed number of 
  significant digits should use DBL_DIG + 2 or FLT_DIG + 2 as 
  cut-off values (Since fixed precision does not use the 'e' 
  notation)
  
  Of these points, #1 is the controversial one, but this 
  change is preferred and has been cleared with Monty. The 
  function causes quite a few unit tests to blow up and they had
  to b changed, but each one is annotated and motivated. We 
  frequently see the magical 53 and 24 give way to more relevant
  numbers.

  mysql-test/r/create.result@1.125, 2007-03-22 10:56:40+01:00, mhansson@linux-st28.site +2 -2
    bug#24791
    
    changed test result
    
    With the changes made for FLOAT and DOUBLE, the original display
    lengths are now preserved. 

  mysql-test/r/temp_table.result@1.22, 2007-03-22 10:56:40+01:00, mhansson@linux-st28.site +21 -0
    bug#24791
    
    changed test resullt
    
    Test case added

  mysql-test/r/type_float.result@1.50, 2007-03-22 10:56:40+01:00, mhansson@linux-st28.site +4 -4
    bug#24791
    
    changed test result
    
    delta 1: field was originally declared as DOUBLE with no display
    length, so the hardware maximum is chosen rather than 53.
    
    delta 2: fields exceed the maximum precision and thus switch to
    non-fixed significant digits
    
    delta 3: Same as above, number of decmals and significant digits
    was not specified when t3 was created.

  mysql-test/t/temp_table.test@1.16, 2007-03-22 10:56:40+01:00, mhansson@linux-st28.site +16 -0
    bug#24791
    
    Test case

  sql/field.h@1.196.1.1, 2007-03-22 10:56:40+01:00, mhansson@linux-st28.site +1 -3
    bug#24791
    
    The method max_display_length is reimplemented as
    
    uint32 max_display_length() { return field_length; }
    
    in Field_double and Field_float. Since all subclasses of 
    Field_real now have the same implementation of this method, the
    implementation has been moved up the hierarchy to Field_real.

  sql/item.cc@1.256.1.1, 2007-03-22 10:56:41+01:00, mhansson@linux-st28.site +11 -7
    bug#24791
    
    We switch to a non-fixed number of significant digits
    (by setting decimals=NOT_FIXED_DECIMAL) if the calculated 
    display length is greater than the display length of a value 
    with the maximum precision. These values differ for double and 
    float, obviously.

  sql/item_sum.cc@1.196.2.1, 2007-03-22 10:56:41+01:00, mhansson@linux-st28.site +3 -1
    bug#24791
    
    We must increase the display length accordinly whenever we 
    change number of decimal places. 

ChangeSet@1.2392.120.3, 2007-03-22 12:44:38+04:00, holyfoot@mysql.com +1 -0
  bug #16546 (DATETIME+0 not always coerced the same way)
    fix for cast( AS DATETIME)+0 in 5.0 and above versions.
    val_real now works using val_decimal for DATETIME Items
    Superfluous val_real() methods deleted

  sql/item_timefunc.h@1.74, 2007-03-22 12:44:37+04:00, holyfoot@mysql.com +8 -11
    val_real() for datetime functions implemented
        as { return val_real_from_decimal(); }
        It's not a fastest possible way, but code is simple and less
        error-prone, what i belive is more important here as this part
        works unfrequently.

ChangeSet@1.1616.3001.2, 2007-03-22 12:24:56+04:00, holyfoot@mysql.com +3 -0
   bug #16546 (DATETIME + 0 not always coerced in the same way)
    fix for cast( AS DATETIME) + 0 operation.
    I just implemented Item_datetime_typecast::val() method
    as it is usually done in other classes.
    Should be fixed more radically in 5.0

  mysql-test/r/type_datetime.result@1.21.1.5, 2007-03-22 12:24:55+04:00, holyfoot@mysql.com +3 -0
    result added

  mysql-test/t/type_datetime.test@1.18.1.1, 2007-03-22 12:24:56+04:00, holyfoot@mysql.com +6 -0
    testcase

  sql/item_timefunc.h@1.42.1.17, 2007-03-22 12:24:56+04:00, holyfoot@mysql.com +7 -0
    added double conversion to Item_datetime_typecast

ChangeSet@1.2392.110.4, 2007-03-22 00:05:36-07:00, igor@olga.mysql.com +3 -0
  Fixed bug #27362: crash at evaluation of IN predicate when one
  of its argument happened to be a decimal expression returning
  the NULL value.
  The crash was due to the fact the function in_decimal::set did
  not take into account that val_decimal() could return 0 if 
  the decimal expression had been evaluated to NULL.  

  mysql-test/r/func_in.result@1.34, 2007-03-22 00:05:34-07:00, igor@olga.mysql.com +5 -0
    Added a test case for bug #27362.

  mysql-test/t/func_in.test@1.28, 2007-03-22 00:05:34-07:00, igor@olga.mysql.com +11 -0
    Added a test case for bug #27362.

  sql/item_cmpfunc.cc@1.239.1.1, 2007-03-22 00:05:34-07:00, igor@olga.mysql.com +2 -1
    Fixed bug #27362: crash at evaluation of IN predicate when one
    of its argument happened to be a decimal expression returning
    the NULL value.
    The crash was due to the fact the function in_decimal::set did
    not take into account that val_decimal() could return 0 if 
    the decimal expression had been evaluated to NULL.  

ChangeSet@1.2392.118.1, 2007-03-21 21:54:38+03:00, evgen@moonbone.local +3 -0
  Bug#23345: Wrongly allowed INTO in a non-last select of a UNION.
  
  INTO clause can be specified only for the last select of a UNION and it
  receives the result of the whole query. But it was wrongly allowed in
  non-last selects of a UNION which leads to a confusing query result.
  
  Now INTO allowed only in the last select of a UNION.

  mysql-test/r/union.result@1.90, 2007-03-21 21:53:53+03:00, evgen@moonbone.local +8 -0
    Added a test case for the bug#23345: Wrongly allowed INTO in a non-last select of a UNION.

  mysql-test/t/union.test@1.99, 2007-03-21 21:53:51+03:00, evgen@moonbone.local +9 -0
    Added a test case for the bug#23345: Wrongly allowed INTO in a non-last select of a UNION.

  sql/sql_yacc.yy@1.510.1.1, 2007-03-21 21:53:53+03:00, evgen@moonbone.local +1 -1
    Bug#23345: Wrongly allowed INTO in a non-last select of a UNION.
    Now INTO allowed only in the last select of a UNION.

ChangeSet@1.2392.1.103, 2007-03-21 11:05:43-07:00, omer@linux.site +1 -0
  Modifying mysql-test-run.pl to allow steeing of --secure-file-priv to 'mysql-test' when 
  running suites other tha the main one

  mysql-test/mysql-test-run.pl@1.208.1.2, 2007-03-21 11:05:41-07:00, omer@linux.site +10 -2
    Modifying to allow steeing of --secure-file-priv to 'mysql-test' when running suites 
    other tha the main one

ChangeSet@1.2405.1.1, 2007-03-21 13:58:11-04:00, iggy@recycle.(none) +1 -0
  Bug#27144 sp-destruct.test is disabled on Windows
  - Update test to run properly on Windows.

  mysql-test/t/sp-destruct.test@1.7, 2007-03-21 13:58:09-04:00, iggy@recycle.(none) +18 -14
    Bug#27144 sp-destruct.test is disabled on Windows
    - Enabled test on Windows.
    - Replaced non-portable system commands (mkdir, rmdir, mv, cp, echo) 
    with the mysqltest builtin commands.
    - Replace Windows directory seperator in error ER_NOT_FROM_FILE with
    posix directory seperator for single test/result pair.

ChangeSet@1.2392.35.9, 2007-03-21 15:49:51+01:00, df@pippilotta.erinye.com +1 -0
  fix shell script

  BUILD/check-cpu@1.18.1.3, 2007-03-21 15:49:49+01:00, df@pippilotta.erinye.com +7 -2
    make comparison a little more compatible with less exotic shells

ChangeSet@1.2216.71.56, 2007-03-21 15:34:47+01:00, jonas@perch.ndb.mysql.com +4 -0
  ndb - bug#27283
      Additional fix for 2-node case

  ndb/src/kernel/blocks/dbdih/Dbdih.hpp@1.14.2.2, 2007-03-21 15:34:45+01:00, jonas@perch.ndb.mysql.com +2 -0
    Add error insert ref for errcode = 7181

  ndb/src/kernel/blocks/dbdih/DbdihMain.cpp@1.55.1.15, 2007-03-21 15:34:45+01:00, jonas@perch.ndb.mysql.com +6 -1
    Make GSN_GCP_NODEFINISH always be sent to DIH node requesting it

  ndb/src/kernel/blocks/dbtc/Dbtc.hpp@1.36.3.1, 2007-03-21 15:34:45+01:00, jonas@perch.ndb.mysql.com +3 -0
    Make GSN_GCP_NODEFINISH always be sent to DIH node requesting it

  ndb/src/kernel/blocks/dbtc/DbtcMain.cpp@1.102.1.1, 2007-03-21 15:34:45+01:00, jonas@perch.ndb.mysql.com +2 -0
    Make GSN_GCP_NODEFINISH always be sent to DIH node requesting it

ChangeSet@1.2392.115.1, 2007-03-21 09:13:05+01:00, pekka@clam.ndb.mysql.com +4 -0
  ndb - bug#24028 in 5.0
  proper fix exists only in version >= 5.1

  mysql-test/r/ndb_blob.result@1.20, 2007-03-21 09:10:32+01:00, pekka@clam.ndb.mysql.com +2 -0
    bug#24028 in 5.0 only

  mysql-test/t/ndb_blob.test@1.19, 2007-03-21 09:10:32+01:00, pekka@clam.ndb.mysql.com +5 -0
    bug#24028 in 5.0 only

  ndb/src/ndbapi/NdbBlob.cpp@1.34, 2007-03-21 09:10:32+01:00, pekka@clam.ndb.mysql.com +6 -0
    bug#24028 in 5.0 only

  ndb/test/ndbapi/testBlobs.cpp@1.33, 2007-03-21 09:10:32+01:00, pekka@clam.ndb.mysql.com +33 -17
    bug#24028 in 5.0 only

ChangeSet@1.2216.71.55, 2007-03-21 08:57:14+01:00, jonas@perch.ndb.mysql.com +1 -0
  ndb - bug#27286 (5.0 version)
    make sure master is sendable

  ndb/src/mgmsrv/MgmtSrvr.cpp@1.102.2.2, 2007-03-21 08:57:13+01:00, jonas@perch.ndb.mysql.com +2 -0
    make sure master is sendable

ChangeSet@1.2377.51.4, 2007-03-21 08:40:24+01:00, tomas@whalegate.ndb.mysql.com +1 -0
  Bug #26825 MySQL Server Crashes in high load
  - initialize to NULL, to avoid call of free on uninitialized variable

  sql/ha_ndbcluster.cc@1.291.5.2, 2007-03-21 08:40:22+01:00, tomas@whalegate.ndb.mysql.com +7 -4
    Bug #26825 MySQL Server Crashes in high load
    - initialize to NULL, to avoid call of free on uninitialized variable

ChangeSet@1.2392.93.2, 2007-03-21 15:36:22+08:00, Justin.He@dev3-240.dev.cn.tlan +1 -0
  Bug#24568, NdbScanFilter NAND/NOR operations sometimes do not works as expected
  this patch is an absolutely necessary supplement of the previous patch,
  the previous patch doesnot cover isnull() and isnotnull() methods' effect.

  ndb/src/ndbapi/NdbScanFilter.cpp@1.13, 2007-03-21 15:36:20+08:00, Justin.He@dev3-240.dev.cn.tlan +8 -2
    correct isnull() and isnotnull() when these two methods called in a NAND/NOR operation 

ChangeSet@1.2392.113.1, 2007-03-20 11:51:09-07:00, igor@olga.mysql.com +3 -0
  Fixed bug #27257: queries containing subqueries with COUNT(*)
  aggregated in outer context returned wrong results.
  This happened only if the subquery did not contain any references
  to outer fields.
  As there were no references to outer fields the subquery erroneously
  was taken for non-correlated one.
  Now any set function aggregated in outer context makes the subquery
  correlated.

  mysql-test/r/subselect.result@1.180, 2007-03-20 11:51:06-07:00, igor@olga.mysql.com +25 -0
    Added a test case for bug #27257.

  mysql-test/t/subselect.test@1.145, 2007-03-20 11:51:07-07:00, igor@olga.mysql.com +21 -0
    Added a test case for bug #27257.

  sql/item_sum.cc@1.196.1.1, 2007-03-20 11:51:07-07:00, igor@olga.mysql.com +1 -0
    Fixed bug #27257: queries containing subqueries with COUNT(*)
    aggregated in outer context returned wrong results.
    This happened only if the subquery did not contain any references
    to outer fields.
    As there were no references to outer fields the subquery erroneously
    was taken for non-correlated one.
    Now any set function aggregated in outer context makes the subquery
    correlated.

ChangeSet@1.1616.3000.1, 2007-03-20 19:43:36+01:00, msvensson@pilot.blaudden +1 -0
  Remove the variables for long gone disable_ps_warnings 

  client/mysqltest.c@1.92.21.53, 2007-03-20 19:43:35+01:00, msvensson@pilot.blaudden +1 -6
    Remove the variables for long gone disable_ps_warnings 

ChangeSet@1.2377.52.1, 2007-03-20 19:46:02+02:00, gkodinov@macbook.local +10 -0
  Bug #24484:
  To correctly decide which predicates can be evaluated with a given table
  the optimizer must know the exact set of tables that a predicate depends 
  on. If that mask is too wide (refer to non-existing tables) the optimizer
  can erroneously skip a predicate.
  One such case of wrong table usage mask were the aggregate functions.
  The have a all-1 mask (meaning depend on all tables, including non-existent
  ones).
  Fixed by making a real used_tables mask for the aggregates. The mask is
  constructed in the following way :
  1. OR the table dependency masks of all the arguments of the aggregate.
  2. If all the arguments of the function are from the local name resolution 
    context and it is evaluated in the same name resolution
    context where it is referenced all the tables from that name resolution 
    context are OR-ed to the dependency mask. This is to denote that an
    aggregate function depends on the number of rows it processes.
  3. Handle correctly the case of an aggregate function optimization (such that
    the aggregate function can be pre-calculated and made a constant).
  
  Made sure that an aggregate function is never a constant (unless subject of a 
  specific optimization and pre-calculation).  
  
  One other flaw was revealed and fixed in the process : references were 
  not calling the recalculation method for used_tables of their targets.

  mysql-test/r/subselect3.result@1.4.1.1, 2007-03-20 19:45:49+02:00, gkodinov@macbook.local +53 -0
    Bug #24484: test case

  mysql-test/t/subselect3.test@1.6, 2007-03-20 19:45:49+02:00, gkodinov@macbook.local +41 -0
    Bug #24484: test case

  sql/item.h@1.213.7.1, 2007-03-20 19:45:50+02:00, gkodinov@macbook.local +5 -0
    Bug #24484: Item_ref must update the used tables.

  sql/item_sum.cc@1.192.3.1, 2007-03-20 19:45:51+02:00, gkodinov@macbook.local +30 -6
    Bug #24484: correct calculation of used_tables for aggregates.

  sql/item_sum.h@1.111, 2007-03-20 19:45:51+02:00, gkodinov@macbook.local +36 -23
    Bug #24484: correct calculation of used_tables for aggregates.

  sql/opt_range.cc@1.237.2.1, 2007-03-20 19:45:52+02:00, gkodinov@macbook.local +4 -2
    Bug #24484: fixed ref resolution in loose index scan

  sql/sql_base.cc@1.365.3.1, 2007-03-20 19:45:53+02:00, gkodinov@macbook.local +2 -0
    Bug #24484: moved counting of leaf tables inside 
    setup_tables_and_check_access.

  sql/sql_class.h@1.317.3.1, 2007-03-20 19:45:54+02:00, gkodinov@macbook.local +3 -0
    Bug #24484: changed table count to more narrow type.

  sql/sql_insert.cc@1.211.8.1, 2007-03-20 19:45:54+02:00, gkodinov@macbook.local +4 -2
    Bug #24484: moved counting of leaf tables inside 
    setup_tables_and_check_access. Substract the first
    table (and its subtables) of an INSERT statement
    from leaf_count.

  sql/sql_select.cc@1.488.4.1, 2007-03-20 19:45:55+02:00, gkodinov@macbook.local +11 -12
    Bug #24484: correct check for aggregates

ChangeSet@1.2392.1.99, 2007-03-20 18:31:49+01:00, kent@mysql.com +1 -0
  echo.c:
    Corrected GPL to be version 2 only

  client/echo.c@1.2, 2007-03-20 18:31:35+01:00, kent@mysql.com +1 -2
    Corrected GPL to be version 2 only

ChangeSet@1.2216.71.54, 2007-03-20 16:16:25+01:00, jonas@perch.ndb.mysql.com +4 -0
  ndb - bug#27283 (wl2325-5.0)
      Handle race condtition between MASTER_GCPCONF and execGCP_NODEFINISH

  ndb/src/kernel/blocks/ERROR_codes.txt@1.28, 2007-03-20 16:16:24+01:00, jonas@perch.ndb.mysql.com +1 -1
    new error codes

  ndb/src/kernel/blocks/dbdih/DbdihMain.cpp@1.55.1.14, 2007-03-20 16:16:24+01:00, jonas@perch.ndb.mysql.com +29 -3
    Handle race condtition between MASTER_GCPCONF and execGCP_NODEFINISH

  ndb/test/ndbapi/testNodeRestart.cpp@1.24.1.6, 2007-03-20 16:16:24+01:00, jonas@perch.ndb.mysql.com +45 -0
    testcase

  ndb/test/run-test/daily-basic-tests.txt@1.41.1.10, 2007-03-20 16:16:24+01:00, jonas@perch.ndb.mysql.com +4 -0
    testcase

ChangeSet@1.2216.71.53, 2007-03-20 16:08:39+01:00, jonas@perch.ndb.mysql.com +1 -0
  ndb - bug#27291
    Fix correct min-value for LockPagesInMemory

  ndb/src/mgmsrv/ConfigInfo.cpp@1.77.1.3, 2007-03-20 16:08:37+01:00, jonas@perch.ndb.mysql.com +1 -1
    Fix correct min-value

ChangeSet@1.2398.2.1, 2007-03-20 10:34:25-04:00, iggy@recycle.(none) +4 -0
  Bug#23736 Pointer free error in mysqlbinlog
  - Mis-matched SAFEMALLOC defines caused misleading error message.

  client/mysqlbinlog.cc@1.136, 2007-03-20 10:34:23-04:00, iggy@recycle.(none) +13 -14
    Bug#23736 Pointer free error in mysqlbinlog
    - Re-worked the Load_log_processor so that it frees it's resources before 
    my_end is called.  This is necessary because SAFEMALLOC's _my_free calls
    pthread_mutex_lock() using THR_LOCK_malloc which is cleaned up in my_end().

  include/my_sys.h@1.194, 2007-03-20 10:34:23-04:00, iggy@recycle.(none) +9 -8
    Bug#23736 Pointer free error in mysqlbinlog
    - Define DYNAMIC_ARRAY beofore MY_TMPDIR
    - Add DYNAMIC_ARRAY to MY_TMP_DIR

  mysys/array.c@1.13, 2007-03-20 10:34:23-04:00, iggy@recycle.(none) +0 -4
    Bug#23736 Pointer free error in mysqlbinlog
    - SAFEMALLOC should not be unconditionally undef'd.

  mysys/mf_tempdir.c@1.6, 2007-03-20 10:34:23-04:00, iggy@recycle.(none) +6 -7
    Bug#23736 Pointer free error in mysqlbinlog
    - Use struct's DYNAMIC_ARRAY.
    - Use DYNAMIC_ARRAY:delete_dynamic function instead of my_free

ChangeSet@1.2398.1.4, 2007-03-20 10:07:23-04:00, iggy@recycle.(none) +1 -0
  Bug#25765 too many dbg heap assertions on windows
  - SAFEMALLOC should be defined for each project in debug Windows builds.
  SAFEMALLOC was not defined for the innodb project. Debug asserts caused 
  due to mixed SAFEMALLOC defines.

  innobase/CMakeLists.txt@1.5, 2007-03-20 10:07:21-04:00, iggy@recycle.(none) +2 -2
    Bug#25765 too many dbg heap assertions on windows
    - Make sure that *_DEBUG defaults are not overwritten.
    - Define SAFEMALLOC and SAFE_MUTEX for debug innodb builds.

ChangeSet@1.2392.109.1, 2007-03-20 17:53:55+04:00, holyfoot@mysql.com +6 -0
  tests fixed to work in embedded server

  mysql-test/r/delayed.result@1.14, 2007-03-20 17:53:54+04:00, holyfoot@mysql.com +5 -0
    result fixed

  mysql-test/r/merge.result@1.59, 2007-03-20 17:53:54+04:00, holyfoot@mysql.com +0 -5
    result fixed

  mysql-test/t/delayed.test@1.18, 2007-03-20 17:53:54+04:00, holyfoot@mysql.com +10 -0
    moved here from merge.test

  mysql-test/t/init_connect.test@1.10, 2007-03-20 17:53:54+04:00, holyfoot@mysql.com +3 -2
    test fixed as it created users, then stopped without deletion, what caused
    problems in consequent tests

  mysql-test/t/merge.test@1.49, 2007-03-20 17:53:54+04:00, holyfoot@mysql.com +0 -9
    moved to delayed.test

  mysql-test/t/mysqlbinlog-cp932.test@1.2, 2007-03-20 17:53:54+04:00, holyfoot@mysql.com +2 -0
    disabled in embedded server

ChangeSet@1.2392.108.2, 2007-03-20 13:33:17+01:00, df@pippilotta.erinye.com +1 -0
  small build fix

  netware/Makefile.am@1.20.2.1, 2007-03-20 13:33:14+01:00, df@pippilotta.erinye.com +1 -1
    use detected awk variant instead of using awk directly

ChangeSet@1.2403, 2007-03-20 11:15:15+01:00, msvensson@pilot.blaudden +1 -0
  Bug#27070 server logs are created unrequested and in wrong directory
  - Setting up a A->B->A replication causes relay logs being written
    by the master, remove them when test is finished
   

  mysql-test/t/rpl_dual_pos_advance.test@1.2, 2007-03-20 11:15:14+01:00, msvensson@pilot.blaudden +6 -0
    Cleanup files created by test case in var/run directory

ChangeSet@1.2392.107.1, 2007-03-20 00:46:19+03:00, evgen@moonbone.local +3 -0
  sql_insert.cc:
    Removed wrong fix for the bug#27006.
    The bug was added by the fix for the bug#19978 and fixed by Monty on 2007/02/21.
  trigger.test, trigger.result:
    Corrected test case for the bug#27006.

  mysql-test/r/trigger.result@1.57, 2007-03-20 00:46:03+03:00, evgen@moonbone.local +6 -5
    Corrected test case for the bug#27006.

  mysql-test/t/trigger.test@1.64, 2007-03-20 00:45:30+03:00, evgen@moonbone.local +3 -3
    Corrected test case for the bug#27006.

  sql/sql_insert.cc@1.225, 2007-03-20 00:39:47+03:00, evgen@moonbone.local +5 -5
    Removed wrong fix for the bug#27006.
    The bug was added by the fix for the bug#19978 and fixed by Monty on 2007/02/21.

ChangeSet@1.2392.35.8, 2007-03-19 16:15:47+01:00, df@pippilotta.erinye.com +1 -0
  Modify BUG#26701 patch and a different location to also use the correct arguments for GCC 5 and 6.

  BUILD/check-cpu@1.18.1.2, 2007-03-19 16:15:46+01:00, df@pippilotta.erinye.com +11 -15
    case -> if ... -lt

ChangeSet@1.1616.2996.1, 2007-03-19 15:56:53+01:00, istruewing@chilla.local +3 -0
  Bug#26996 - Update of a Field in a Memory Table ends with wrong result
  
  Using a MEMORY table BTREE index for scanning for updatable rows
  could lead to an infinite loop.
  
  Everytime a key was inserted into a btree index, the position
  in the index scan was cleared. The search started from the
  beginning and found the same key again.
  
  Now we do not clear the position on key insert an more.

  heap/hp_write.c@1.19.1.3, 2007-03-19 15:56:51+01:00, istruewing@chilla.local +0 -1
    Bug#26996 - Update of a Field in a Memory Table ends with wrong result
    Removed the index-scan-breaking nulling of last_pos.
    The comment behind this line ("For heap_rnext/heap_rprev")
    was misleading. It should have been "Breaks heap_rnext/heap_rprev".

  mysql-test/r/heap_btree.result@1.13.2.3, 2007-03-19 15:56:51+01:00, istruewing@chilla.local +15 -0
    Bug#26996 - Update of a Field in a Memory Table ends with wrong result
    Added test result.

  mysql-test/t/heap_btree.test@1.12.1.4, 2007-03-19 15:56:51+01:00, istruewing@chilla.local +14 -0
    Bug#26996 - Update of a Field in a Memory Table ends with wrong result
    Added test.

ChangeSet@1.2402, 2007-03-16 17:28:32+01:00, msvensson@pilot.blaudden +9 -0
  Bug#20166 mysql-test-run.pl does not test system privilege tables creation
   - Build sql files for netware from the mysql_system_tables*.sq files
   - Fix comments about mysql_create_system_tables.sh
   - Use mysql_install_db.sh to create system tables for mysql_test-run-shell
   - Fix mysql-test-run.pl to also look in share/mysql for the msyql_system*.sql files

  BitKeeper/deleted/.del-init_db.sql~e2b8d0c8390e8023@1.9, 2007-03-16 17:26:27+01:00, msvensson@pilot.blaudden +0 -0
    Rename: netware/init_db.sql -> BitKeeper/deleted/.del-init_db.sql~e2b8d0c8390e8023

  BitKeeper/deleted/.del-test_db.sql@1.5, 2007-03-16 17:26:27+01:00, msvensson@pilot.blaudden +0 -0
    Rename: netware/test_db.sql -> BitKeeper/deleted/.del-test_db.sql

  BitKeeper/etc/ignore@1.244, 2007-03-16 17:28:30+01:00, msvensson@pilot.blaudden +2 -0
    Added netware/init_db.sql netware/test_db.sql to the ignore list

  mysql-test/install_test_db.sh@1.39, 2007-03-16 17:28:31+01:00, msvensson@pilot.blaudden +8 -12
    Use mysql_install_db from install_test_db(which is used bu mysql-test-run-shell)
    to install the system tables

  mysql-test/mysql-test-run.pl@1.210, 2007-03-16 17:28:31+01:00, msvensson@pilot.blaudden +11 -3
    Look for the mysql_system_tables*.sql also in share/mysql

  netware/Makefile.am@1.21, 2007-03-16 17:28:31+01:00, msvensson@pilot.blaudden +24 -4
    Build netware/init_db.sql and netware/test_db.sql from
    the sources in scripts/msyql_system_tables*.sql

  scripts/make_binary_distribution.sh@1.123, 2007-03-16 17:28:31+01:00, msvensson@pilot.blaudden +0 -6
    netware/init_db.sql and netware/test_db.sql are now built by the Makefiles
    from the scripts/mysql_system_tables*.sql files

  sql/mysql_priv.h@1.436.1.1, 2007-03-16 17:28:31+01:00, msvensson@pilot.blaudden +3 -2
    Update comment remindging to update the MySQL system table definitions
    when adding a new SQL_MODE

  sql/sql_acl.h@1.53, 2007-03-16 17:28:31+01:00, msvensson@pilot.blaudden +1 -1
    Update comment reminding to update the MySQL System tables
    when changing the ACL defines

ChangeSet@1.2385.9.1, 2007-03-16 17:25:20+03:00, kaa@polly.local +3 -0
  Fix for bug #23775 "Replicated event larger that max_allowed_packet infinitely re-transmits".
  
  Problem: to handle a situation when the size of event on the master is greater than max_allowed_packet on slave, we checked for the wrong constant (ER_NET_PACKET_TOO_LARGE instead of CR_NET_PACKET_TOO_LARGE).
  
  Solution: test for the client "packet too large" error code instead of the server one in slave I/O thread.

  mysql-test/r/rpl_packet.result@1.4, 2007-03-16 17:25:15+03:00, kaa@polly.local +9 -0
    Added test case for bug #23775 "Replicated event larger that max_allowed_packet infinitely re-transmits"

  mysql-test/t/rpl_packet.test@1.4, 2007-03-16 17:25:15+03:00, kaa@polly.local +33 -0
    Added test case for bug #23775 "Replicated event larger that max_allowed_packet infinitely re-transmits"

  sql/slave.cc@1.286.5.1, 2007-03-16 17:25:15+03:00, kaa@polly.local +2 -1
    Test for the client "packet too large" error code instead of the server one in slave I/O thread.

ChangeSet@1.2392.1.93, 2007-03-16 17:23:26+03:00, evgen@moonbone.local +3 -0
  Bug#27006: AFTER UPDATE triggers not fired with INSERT ... ON DUPLICATE KEY
  UPDATE if the row wasn't actually changed.
  
  This bug was caused by fix for bug#19978. It causes AFTER UPDATE triggers
  not firing if a row wasn't actually changed by the update part of the
  INSERT .. ON DUPLICATE KEY UPDATE.
  
  Now triggers are always fired if a row is touched by the INSERT ... ON
  DUPLICATE KEY UPDATE.

  mysql-test/r/trigger.result@1.56, 2007-03-16 17:21:22+03:00, evgen@moonbone.local +41 -0
    Added a test case for the bug#27006: AFTER UPDATE triggers not fired with INSERT ... ON DUPLICATE KEY
    UPDATE if the row wasn't actually changed.

  mysql-test/t/trigger.test@1.63, 2007-03-16 17:21:43+03:00, evgen@moonbone.local +38 -0
    Added a test case for the bug#27006: AFTER UPDATE triggers not fired with INSERT ... ON DUPLICATE KEY
    UPDATE if the row wasn't actually changed.

  sql/sql_insert.cc@1.224, 2007-03-16 17:20:54+03:00, evgen@moonbone.local +6 -6
    Bug#27006: AFTER UPDATE triggers not fired with INSERT ... ON DUPLICATE KEY
    UPDATE if the row wasn't actually changed.
    Now triggers are always fired if a row is touched by the INSERT ... ON
    DUPLICATE KEY UPDATE.

ChangeSet@1.2392.100.1, 2007-03-16 14:25:11+01:00, Kristofer.Pettersson@naruto. +4 -0
  Bug#20777 Function w BIGINT UNSIGNED shows diff. behaviour with and without --ps-protocol
  
  - Stored procedures returning unsinged values returns signed values if
    text protocol is used. The reason is that the stored proceedure item
    Item_func_sp wasn't initializing the member variables properly based
    on the information contained in the associated result field.
  - The patch is to upon field-item association, ::fix_fields, initialize
    the member variables in appropriate order.
  - Field type of an Item_func_sp was hard coded to MYSQL_TYPE_VARCHAR.
    This is changed to return the type of the actual result field.
  - Member function name sp_result_field was refactored to the more 
    appropriate init_result_field.
  - Member function name find_and_check_access was refactored to 
    sp_check_access.

  mysql-test/r/sp.result@1.218.3.1, 2007-03-16 14:25:00+01:00, Kristofer.Pettersson@naruto. +88 -0
    - Added test

  mysql-test/t/sp.test@1.208.3.1, 2007-03-16 14:25:01+01:00, Kristofer.Pettersson@naruto. +56 -4
    - Added test

  sql/item_func.cc@1.317.7.1, 2007-03-16 14:25:01+01:00, Kristofer.Pettersson@naruto. +155 -164
    Bug#20777 Function w BIGINT UNSIGNED shows diff. behaviour with and without --ps-protocol
    
    - Stored procedures returning unsinged values returns signed values if
      text protocol is used. The reason is that the stored proceedure item
      Item_func_sp wasn't initializing the member variables properly based
      on the information contained in the associated result field.
    - The patch is to upon field-item association, ::fix_fields, initialize
      the member variables in appropriate order.
    - Field type of an Item_func_sp was hard coded to MYSQL_TYPE_VARCHAR.
      This is changed to to return the type of the actual result field.
    - Member function name sp_result_field was refactored to the more 
      appropriate init_result_field.
    - Member function name find_and_check_access was refactored to 
      sp_check_access.

  sql/item_func.h@1.161, 2007-03-16 14:25:02+01:00, Kristofer.Pettersson@naruto. +18 -15
    Bug#20777 Function w BIGINT UNSIGNED shows diff. behaviour with and without --ps-protocol
    
    - Stored procedures returning unsinged values returns signed values if
      text protocol is used. The reason is that the stored proceedure item
      Item_func_sp wasn't initializing the member variables properly based
      on the information contained in the associated result field.
    - The patch is to upon field-item association, ::fix_fields, initialize
      the member variables in appropriate order.
    - Field type of an Item_func_sp was hard coded to MYSQL_TYPE_VARCHAR.
      This is changed to to return the type of the actual result field.
    - Member function name sp_result_field was refactored to the more 
      appropriate init_result_field.
    - Member function name find_and_check_access was refactored to 
      sp_check_access.

ChangeSet@1.2392.98.1, 2007-03-16 11:52:30+01:00, msvensson@pilot.blaudden +1 -0
  Bug#27022 Install fails with Duplicate entry '%-test-' for key 'PRIMARY'
   - Bail out with error if MySQL System tables already exist

  scripts/mysql_install_db.sh@1.72, 2007-03-16 11:52:29+01:00, msvensson@pilot.blaudden +11 -17
    Bail out with error if the MySQL system tables already exist
    in the location where we want to install

ChangeSet@1.1616.2994.1, 2007-03-16 10:28:48+01:00, istruewing@chilla.local +4 -0
  Bug#26231 - select count(*) on myisam table returns wrong value
              when index is used
  
  When the table contained TEXT columns with empty contents
  ('', zero length, but not NULL) _and_ strings starting with
  control characters like tabulator or newline, the empty values
  were not found in a "records in range" estimate. Hence count(*)
  missed these records.
  
  The reason was a different set of search flags used for key
  insert and key range estimation.
  
  I decided to fix the set of flags used in range estimation.
  Otherwise millions of databases around the world would require
  a repair after an upgrade.
  
  The consequence is that the manual must be fixed, which claims
  that TEXT columns are compared with "end space padding". This
  is true for CHAR/VARCHAR but wrong for TEXT. See also bug 21335.

  myisam/mi_range.c@1.12.1.3, 2007-03-16 10:28:45+01:00, istruewing@chilla.local +35 -1
    Bug#26231 - select count(*) on myisam table returns wrong value
                when index is used
    Added SEARCH_UPDATE to the search flags so that it compares
    like write/update/delete operations do. Only so it expects
    the keys at the place where they have been inserted.

  myisam/mi_search.c@1.49.1.8, 2007-03-16 10:28:46+01:00, istruewing@chilla.local +35 -7
    Bug#26231 - select count(*) on myisam table returns wrong value
                when index is used
    Added some comments to explain how _mi_get_binary_pack_key()
    works.

  mysql-test/r/myisam.result@1.45.1.28, 2007-03-16 10:28:46+01:00, istruewing@chilla.local +150 -0
    Bug#26231 - select count(*) on myisam table returns wrong value
                when index is used
    Added a test.

  mysql-test/t/myisam.test@1.33.1.26, 2007-03-16 10:28:46+01:00, istruewing@chilla.local +144 -0
    Bug#26231 - select count(*) on myisam table returns wrong value
                when index is used
    Added test result.

ChangeSet@1.2392.97.1, 2007-03-16 10:35:39+02:00, gkodinov@macbook.gmz +5 -0
  Bug #26261: 
   INSERT uses query_id to verify what fields are
   mentioned in the fields list of the INSERT command.
   However the check for that is made after the 
   ON DUPLICATE KEY is processed. This causes all
   the fields mentioned in ON DUPLICATE KEY to be 
   considered as mentioned in the fields list of 
   INSERT.
   Moved the check up, right after processing the
   fields list.

  mysql-test/r/insert_update.result@1.21.1.1, 2007-03-16 10:35:20+02:00, gkodinov@macbook.gmz +11 -0
    Bug #26261: test case

  mysql-test/t/insert_update.test@1.21.1.1, 2007-03-16 10:35:22+02:00, gkodinov@macbook.gmz +21 -0
    Bug #26261: test case

  sql/mysql_priv.h@1.429.8.3, 2007-03-16 10:35:23+02:00, gkodinov@macbook.gmz +2 -1
    Bug #26261: moved the check inside mysql_prepare_insert

  sql/sql_insert.cc@1.211.7.1, 2007-03-16 10:35:25+02:00, gkodinov@macbook.gmz +45 -23
    Bug #26261: move the check inside mysql_prepare_insert
    before setting up the ON DUPLICATE KEY part

  sql/sql_prepare.cc@1.187.1.9, 2007-03-16 10:35:25+02:00, gkodinov@macbook.gmz +1 -1
    Bug #26261: moved the check inside mysql_prepare_insert

ChangeSet@1.2392.96.1, 2007-03-16 12:15:51+04:00, gluh@mysql.com +3 -0
  Bug#26285 selecting information_schema crahes server
  The crash happens when 'skip-grant-tables' is enabled.
  We skip the filling of I_S privilege tables 
  if acl_cache is not initialized.

  mysql-test/r/skip_grants.result@1.10, 2007-03-16 12:15:49+04:00, gluh@mysql.com +12 -0
    test result

  mysql-test/t/skip_grants.test@1.12, 2007-03-16 12:15:49+04:00, gluh@mysql.com +8 -0
    test case

  sql/sql_acl.cc@1.218, 2007-03-16 12:15:49+04:00, gluh@mysql.com +4 -0
    skip filling of I_S privilege tables
    if acl_cache is not initialized

ChangeSet@1.2392.87.5, 2007-03-14 21:45:20-07:00, omer@linux.site +1 -0
  Added test options to Makefile.am including
   - test suites developed by QA 
   - additional 'fast' test options 

  Makefile.am@1.98, 2007-03-14 21:42:15-07:00, omer@linux.site +32 -4
    Added test options to cover 
     - test suites developed by QA 
     - additional 'fast' test options 

ChangeSet@1.2392.87.4, 2007-03-15 19:01:58+01:00, jbruehe@mysql.com +1 -0
  Raise version number after cloning 5.0.38

  configure.in@1.433, 2007-03-15 19:01:47+01:00, jbruehe@mysql.com +2 -2
    Raise version number after cloning 5.0.38

ChangeSet@1.2392.92.1, 2007-03-15 23:21:29+03:00, evgen@moonbone.local +4 -0
  Bug#27033: 0 as LAST_INSERT_ID() after INSERT .. ON DUPLICATE if rows were
  touched but not actually changed.
  
  The LAST_INSERT_ID() is reset to 0 if no rows were inserted or changed.
  This is the case when an INSERT ... ON DUPLICATE KEY UPDATE updates a row
  with the same values as the row contains.
  
  Now the LAST_INSERT_ID() values is reset to 0 only if there were no rows
  successfully inserted or touched.
  The new 'touched' field is added to the COPY_INFO structure. It holds the
  number of rows that were touched no matter whether they were actually
  changed or not.

  mysql-test/r/insert_update.result@1.22, 2007-03-15 23:20:59+03:00, evgen@moonbone.local +11 -0
    Added a test case for the bug#27033: 0 as LAST_INSERT_ID() after INSERT .. ON DUPLICATE if rows were
    touched but not actually changed.
    

  mysql-test/t/insert_update.test@1.22, 2007-03-15 23:20:59+03:00, evgen@moonbone.local +12 -0
    Added a test case for the bug#27033: 0 as LAST_INSERT_ID() after INSERT .. ON DUPLICATE if rows were
    touched but not actually changed.
    

  sql/sql_class.h@1.325, 2007-03-15 23:20:57+03:00, evgen@moonbone.local +17 -5
    Bug#27033: 0 as LAST_INSERT_ID() after INSERT .. ON DUPLICATE if rows were
    touched but not actually changed.
    
    The new 'touched' field is added to the COPY_INFO structure. It holds the
    number of rows that were touched no matter whether they were actually
    changed or not.

  sql/sql_insert.cc@1.222, 2007-03-15 23:20:59+03:00, evgen@moonbone.local +9 -7
    Bug#27033: 0 as LAST_INSERT_ID() after INSERT .. ON DUPLICATE if rows were
    touched but not actually changed.
    
    Now the LAST_INSERT_ID() values is reset to 0 only if there were no rows
    successfully inserted or touched.

ChangeSet@1.2400, 2007-03-15 15:52:04+01:00, msvensson@pilot.blaudden +3 -0
  Remove test/udf_test and test/udf_test.res, since udf's are nowadays
  tested by mysql-test-run.pl 

  BitKeeper/deleted/.del-udf_test@1.5, 2007-03-15 15:48:47+01:00, msvensson@pilot.blaudden +0 -0
    Delete: tests/udf_test

  BitKeeper/deleted/.del-udf_test.res@1.5, 2007-03-15 15:48:48+01:00, msvensson@pilot.blaudden +0 -0
    Delete: tests/udf_test.res

  tests/Makefile.am@1.32, 2007-03-15 15:52:03+01:00, msvensson@pilot.blaudden +1 -1
    Remove test/udf_test and test/udf_test.res, since udf's are nowadays
    tested by mysql-test-run.pl 

ChangeSet@1.2216.71.52, 2007-03-15 11:05:12+01:00, jonas@perch.ndb.mysql.com +1 -0
  ndb - fix bug in UtilTransactions::compare
    reset rowcount on temporary error during scan of base table

  ndb/test/src/UtilTransactions.cpp@1.19.1.1, 2007-03-15 11:05:11+01:00, jonas@perch.ndb.mysql.com +1 -0
    ndb - fix bug in UtilTransactions::compare
      reset rowcount on temporary error during scan of base table

ChangeSet@1.2399, 2007-03-15 09:58:39+01:00, msvensson@pilot.blaudden +1 -0
  Pass pointer to current mysqld to mysqld_arguments in order to make the
  code eaiser and more extensible

  mysql-test/mysql-test-run.pl@1.209, 2007-03-15 09:58:37+01:00, msvensson@pilot.blaudden +55 -83
    Pass pointer to current mysqld to mysqld_arguments in order to make the
    code eaiser and more extensible

ChangeSet@1.2392.89.1, 2007-03-15 12:06:06+04:00, ramil@mysql.com +3 -0
  Fix for bug #24558: Increasing decimal column length causes data loss
  
  Altering to a decimal field we get double value then store it 
  that may cause data loss. 
  Fix: use store_decimal() instead.
  

  mysql-test/r/type_newdecimal.result@1.44, 2007-03-15 12:06:05+04:00, ramil@mysql.com +8 -0
    Fix for bug #24558: Increasing decimal column length causes data loss
      - test result.

  mysql-test/t/type_newdecimal.test@1.43, 2007-03-15 12:06:05+04:00, ramil@mysql.com +11 -0
    Fix for bug #24558: Increasing decimal column length causes data loss
      - test case.

  sql/field_conv.cc@1.62, 2007-03-15 12:06:05+04:00, ramil@mysql.com +9 -0
    Fix for bug #24558: Increasing decimal column length causes data loss
      - if target field's result type is DECIMAL_RESULT
        use store_decimal(val_decimal()) in order not to loss data.

ChangeSet@1.2392.88.1, 2007-03-14 12:02:32-06:00, malff@weblab.(none) +9 -0
  Bug#26503 (Illegal SQL exception handler code causes the server to crash)
  
  Before this fix, the parser would accept illegal code in SQL exceptions
  handlers, that later causes the runtime to crash when executing the code,
  due to memory violations in the exception handler stack.
  
  The root cause of the problem is instructions within an exception handler
  that jumps to code located outside of the handler. This is illegal according
  to the SQL 2003 standard, since labels located outside the handler are not
  supposed to be visible (they are "out of scope"), so any instruction that
  jumps to these labels, like ITERATE or LEAVE, should not parse.
  
  The section of the standard that is relevant for this is :
    SQL:2003 SQL/PSM (ISO/IEC 9075-4:2003)
    section 13.1 <compound statement>,
    syntax rule 4
  <quote>
    The scope of the <beginning label> is CS excluding every <SQL schema
    statement> contained in CS and excluding every
    <local handler declaration list> contained in CS. <beginning label> shall
    not be equivalent to any other <beginning label>s within that scope.
  </quote>
  
  With this fix, the C++ class sp_pcontext, which represent the "parsing
  context" tree (a.k.a symbol table) of a stored procedure, has been changed
  as follows:
  - constructors have been cleaned up, so that only building a root node for
  the tree is public; building nodes inside a tree is not public.
  - a new member, m_label_scope, indicates if a given syntactic context
  belongs to a DECLARE HANDLER block,
  - label resolution, in the method find_label(), has been changed to
  implement the restriction of scope regarding labels used in a compound
  statement.
  
  The actions in the parser, when parsing the body of a SQL exception handler,
  have been changed as follows:
  - the implementation of an exception handler (DECLARE HANDLER) now creates
  explicitly a new sp_pcontext, to isolate the code inside the handler from
  the containing compound statement context.
  - registering exception handlers as a result occurs in the parent context,
  see the rule sp_hcond_element
  - the code in sp_hcond_list has been cleaned up, to avoid code duplication
  
  In addition, the flags IN_SIMPLE_CASE and IN_HANDLER, declared in sp_head.h
  have been removed, since they are unused and broken by design (as seen with
  Bug 19194 (Right recursion in parser for CASE causes excessive stack usage,
  limitation), representing a stack in a single flag is not possible.
  
  Tests in sp-error have been added to show that illegal constructs are now
  rejected.
  
  Tests in sp have been added for code coverage, to show that ITERATE or LEAVE
  statements are legal when jumping to a label in scope, inside the body of
  an exception handler.

  mysql-test/r/sp-error.result@1.112, 2007-03-14 12:02:30-06:00, malff@weblab.(none) +52 -0
    SQL Exception handlers define a parsing context for label resolution.

  mysql-test/r/sp.result@1.218.1.3, 2007-03-14 12:02:30-06:00, malff@weblab.(none) +165 -0
    SQL Exception handlers define a parsing context for label resolution.

  mysql-test/t/sp-error.test@1.113, 2007-03-14 12:02:30-06:00, malff@weblab.(none) +68 -0
    SQL Exception handlers define a parsing context for label resolution.

  mysql-test/t/sp.test@1.208.1.3, 2007-03-14 12:02:30-06:00, malff@weblab.(none) +135 -0
    SQL Exception handlers define a parsing context for label resolution.

  sql/sp_head.cc@1.238, 2007-03-14 12:02:30-06:00, malff@weblab.(none) +1 -1
    Minor cleanup

  sql/sp_head.h@1.95, 2007-03-14 12:02:30-06:00, malff@weblab.(none) +0 -2
    Minor cleanup

  sql/sp_pcontext.cc@1.33, 2007-03-14 12:02:30-06:00, malff@weblab.(none) +69 -23
    SQL Exception handlers define a parsing context for label resolution.

  sql/sp_pcontext.h@1.31, 2007-03-14 12:02:30-06:00, malff@weblab.(none) +51 -10
    SQL Exception handlers define a parsing context for label resolution.

  sql/sql_yacc.yy@1.509.1.1, 2007-03-14 12:02:30-06:00, malff@weblab.(none) +16 -27
    SQL Exception handlers define a parsing context for label resolution.

ChangeSet@1.1616.2993.1, 2007-03-14 16:27:37+01:00, istruewing@chilla.local +1 -0
  Bug#25289 - repair table causes "my_seek.c:56:
              my_seek: Assertion `fd != -1' failed"
  
  In difficult optimize/repair situations the server could crash.
  Under some circumstances the server retries an optimize/repair
  with more elaborate options. But it did not check if the first
  attempt failed so badly that a second one must not be tried.
  
  This could happen when a new data file has been created
  but it was not possible to open it. In this case the
  repair leaves behind a table with closed data file.
  This must not be used for another repair attempt.
  
  We do now detect the closed data file and do not try
  another repair attempt in this situation.
  
  No test case. The required table corruption can not be
  repeated easily. There is a test program attached to
  bug 25433.

  sql/ha_myisam.cc@1.115.13.1, 2007-03-14 16:27:36+01:00, istruewing@chilla.local +16 -0
    Bug#25289 - repair table causes "my_seek.c:56:
                my_seek: Assertion `fd != -1' failed"
    Added code to detect a closed data file. It could be closed
    by a preceeding repair attempt. We must not try another
    repair then.

ChangeSet@1.2392.1.86, 2007-03-14 15:58:14+02:00, gkodinov@magare.gmz +1 -0
  Bug #26794: fixed valgrind warning

  sql/sql_table.cc@1.333.1.2, 2007-03-14 15:58:13+02:00, gkodinov@magare.gmz +1 -2
    Bug #26794: fixed valgrind warning

ChangeSet@1.2392.62.4, 2007-03-14 11:54:20+02:00, gkodinov@magare.gmz +6 -0
  Bug #26794:
  Different set of conditions is used to verify
  the validity of index definitions over a GEOMETRY
  column in ALTER TABLE and CREATE TABLE. 
  The difference was on how sub-keys notion validity
  is checked.
  Fixed by extending the CREATE TABLE condition to
  support the cases allowed in ALTER TABLE.
  Made the SHOW CREATE TABLE not to display spatial
  indexes using the sub-key notion.

  mysql-test/r/alter_table.result@1.63, 2007-03-14 11:54:19+02:00, gkodinov@magare.gmz +34 -0
    Bug #26794: test case

  mysql-test/r/gis-rtree.result@1.23.1.1, 2007-03-14 11:54:19+02:00, gkodinov@magare.gmz +2 -2
    Bug #26794: fixed SHOW CREATE TABLE output.

  mysql-test/t/alter_table.test@1.50, 2007-03-14 11:54:19+02:00, gkodinov@magare.gmz +23 -0
    Bug #26794: test case

  sql/field.cc@1.339.2.1, 2007-03-14 11:54:19+02:00, gkodinov@magare.gmz +1 -0
    Bug #26794: Allow sub-keys for GEOMETRY

  sql/sql_show.cc@1.341.1.1, 2007-03-14 11:54:19+02:00, gkodinov@magare.gmz +1 -1
    Bug #26794: Don't show sub-key notion 
     in SHOW CREATE TABLE for SPATIAL indexes.

  sql/sql_table.cc@1.333.1.1, 2007-03-14 11:54:19+02:00, gkodinov@magare.gmz +3 -1
    Bug #26794: Allow sub-keys for GEOMETRY

ChangeSet@1.2392.60.13, 2007-03-13 06:06:09-07:00, mtaylor@qualinost.(none) +1 -0
  BUG#26952: mysql.server needs to be able to not timeout in certain situations
  
  For systems running MySQL through heartbeat, it is imperitive that the startup scripts 
  not only return correct return values, but do not return until success or failure has been 
  determined. This is a different behavior than is typically wanted for the startup 
  of a normal machine. 
  
  This patch adds support for a timeout variable for mysql.server. Read from my.cnf, this
  variable defaults to 900 (the current default). A value of 0 means not to wait at all for
  startup confirmation. A negative value means to wait forever.  

  support-files/mysql.server.sh@1.54, 2007-03-13 06:06:02-07:00, mtaylor@qualinost.(none) +9 -1
    Added support for a timeout variable to control timing out our wait for server startup. BUG#26952

ChangeSet@1.2216.71.51, 2007-03-13 11:29:14+01:00, jonas@perch.ndb.mysql.com +7 -0
  ndb - bug#27003
    Handle random(not in order) LQHKEYREQ failures during node-restart

  ndb/src/kernel/blocks/ERROR_codes.txt@1.27, 2007-03-13 11:29:13+01:00, jonas@perch.ndb.mysql.com +12 -0
    Document new error codes

  ndb/src/kernel/blocks/dblqh/DblqhMain.cpp@1.97.2.4, 2007-03-13 11:29:13+01:00, jonas@perch.ndb.mysql.com +16 -3
    Handle random(not in order) LQHKEYREQ failures during node-restart

  ndb/src/kernel/blocks/dbtup/DbtupExecQuery.cpp@1.22.1.1, 2007-03-13 11:29:13+01:00, jonas@perch.ndb.mysql.com +24 -0
    Error codes for various oom problems

  ndb/src/kernel/blocks/dbtup/DbtupGen.cpp@1.20.1.1, 2007-03-13 11:29:13+01:00, jonas@perch.ndb.mysql.com +1 -1
    move CLEAR_ERROR_INSERT_VALUE to constructor so that it's reasonable to use it for
    restart testing
    

  ndb/src/kernel/blocks/ndbcntr/NdbcntrMain.cpp@1.32.1.2, 2007-03-13 11:29:13+01:00, jonas@perch.ndb.mysql.com +1 -0
    Add error insert for CopyFragRef
    

  ndb/test/ndbapi/testNodeRestart.cpp@1.24.1.5, 2007-03-13 11:29:13+01:00, jonas@perch.ndb.mysql.com +56 -0
    Testprg for bug#27003

  ndb/test/run-test/daily-basic-tests.txt@1.41.1.9, 2007-03-13 11:29:13+01:00, jonas@perch.ndb.mysql.com +4 -0
    add testprg

ChangeSet@1.2392.1.82, 2007-03-12 01:39:57-07:00, igor@olga.mysql.com +3 -0
  Fixed bug #26738: incomplete string values in a result set column 
  when the column is to be read from a derived table column which 
  was specified as a concatenation of string literals.
  The bug happened because the Item_string::append did not adjust the
  value of Item_string::max_length. As a result of it the temporary 
  table column  defined to store the concatenation of literals was 
  not wide enough to hold the whole value.
  

  mysql-test/r/subselect.result@1.179, 2007-03-12 01:39:55-07:00, igor@olga.mysql.com +13 -0
    Added a test case for bug #26738.

  mysql-test/t/subselect.test@1.144, 2007-03-12 01:39:55-07:00, igor@olga.mysql.com +13 -0
    Added a test case for bug #26738.

  sql/item.h@1.222, 2007-03-12 01:39:55-07:00, igor@olga.mysql.com +5 -1
    Fixed bug #26738: incomplete string values in a result set column 
    when the column is to be read from a derived table column which 
    was specified as a concatenation of string literals.
    The bug happened because the Item_string::append did not adjust the
    value of Item_string::max_length. As a result of it the temporary 
    table column  defined to store the concatenation of literals was 
    not wide enough to hold the whole value.
    

ChangeSet@1.2392.80.4, 2007-03-11 23:34:40-07:00, igor@olga.mysql.com +3 -0
  Fixed bug #26963: invalid optimization of the pushdown conditions
  after single-row table substitution could lead to a wrong result set.
  The bug happened because the function Item_field::replace_equal_field
  erroniously assumed that any field included in a multiple equality
  with a constant has been already substituted for this constant.
  This not true for fields becoming constant after row substitutions
  for constant tables.
   

  mysql-test/r/select.result@1.151.1.1, 2007-03-11 23:34:38-07:00, igor@olga.mysql.com +38 -0
    Added a test case for bug #26963.

  mysql-test/t/select.test@1.125.1.1, 2007-03-11 23:34:39-07:00, igor@olga.mysql.com +47 -0
    Added a test case for bug #26963.

  sql/item.cc@1.256, 2007-03-11 23:34:39-07:00, igor@olga.mysql.com +13 -2
    Fixed bug #26963: invalid optimization of the pushdown conditions
    after single-row table substitution could lead to a wrong result set.
    The bug happened because the function Item_field::replace_equal_field
    erroneously assumed that any field included in a multiple equality
    with a constant has been already substituted for this constant.
    This not true for fields becoming constant after row substitutions
    for constant tables.
     

ChangeSet@1.2392.81.1, 2007-03-10 17:44:25+04:00, holyfoot@mysql.com +1 -0
  bug #26833 (Compile error with embedded lib)
  org_tables declaration was mistakenly #ifdef-ed with the EMBEDDED_LIBRARY
  instead of ACCESS_CHECKS

  sql/sql_parse.cc@1.610, 2007-03-10 17:44:23+04:00, holyfoot@mysql.com +1 -1
    default condition fixed

ChangeSet@1.2392.77.1, 2007-03-09 12:18:28-05:00, cbell@mysql_cab_desk. +3 -0
  Bug #25543 Replication of wrong values if using rand() in stored procedure
  
  When rand() is called multiple times inside a stored procedure, the server does 
  not binlog the correct random seed values.
  
  This patch corrects the problem by resetting rand_used= 0 in 
  THD::cleanup_after_query() allowing the system to save the random seeds if needed
  for each command in a stored procedure body.
  
  However, rand_used is not reset if executing in a stored function or trigger 
  because these operations are binlogged by call and thus only the calling statement
  need detect the call to rand() made by its substatements. These substatements must 
  not set rand_used to 0 because it would remove the detection of rand() by the 
  calling statement.

  mysql-test/r/rpl_misc_functions.result@1.5, 2007-03-09 12:18:25-05:00, cbell@mysql_cab_desk. +25 -2
    Bug #25543 Replication of wrong values if using rand() in stored procedure
    
    The result file was modified to include the correct processing of the new
    additions to the test. The results from execution are written to files on 
    both the master and the slave. The files are compared to ensure the values 
    from rand() generated on the master are correctly generated on the slave.

  mysql-test/t/rpl_misc_functions.test@1.6, 2007-03-09 12:18:25-05:00, cbell@mysql_cab_desk. +66 -2
    Bug #25543 Replication of wrong values if using rand() in stored procedure
    
    The test was modified to include a test of a stored procedure that calls
    the rand() function multiple times. 
    
    The results from execution are written to files on both the master and the
    slave. The files are compared to ensure the values from rand() generated
    on the master are correctly generated on the slave.

  sql/sql_class.cc@1.260.1.1, 2007-03-09 12:18:26-05:00, cbell@mysql_cab_desk. +12 -0
    Bug #25543 Replication of wrong values if using rand() in stored procedure
    
    The code was modified to reset rand_used so that detection of calls to rand() 
    will save random seeds if needed by the slave. 

ChangeSet@1.2341.91.1, 2007-03-09 15:20:06+02:00, gkodinov@macbook.gmz +3 -0
  WL#3527: Extend IGNORE INDEX so places where index is ignored can 
           be specified
   5.0 part of the fix. Implements IGNORE INDEX FOR JOIN as a synonym
   of IGNORE INDEX for backward compatibility with the 5.1 fix.

  mysql-test/r/select.result@1.143.3.1, 2007-03-09 15:19:58+02:00, gkodinov@macbook.gmz +9 -0
    WL#3527: Extend IGNORE INDEX so places where index is ignored can 
             be specified
    - test case

  mysql-test/t/select.test@1.117.3.1, 2007-03-09 15:19:59+02:00, gkodinov@macbook.gmz +10 -0
    WL#3527: Extend IGNORE INDEX so places where index is ignored can 
             be specified
    - test case

  sql/sql_yacc.yy@1.498.7.1, 2007-03-09 15:20:00+02:00, gkodinov@macbook.gmz +13 -4
    WL#3527: Extend IGNORE INDEX so places where index is ignored can 
             be specified
     5.0 part of the fix. Implements IGNORE INDEX FOR JOIN as a synonym
     of IGNORE INDEX for backward compatibility with the 5.1 fix.

ChangeSet@1.2392.72.4, 2007-03-09 18:12:46+07:00, tomas@poseidon.mysql.com +1 -0
  manual merge

  mysql-test/r/ndb_single_user.result@1.2, 2007-03-09 18:12:39+07:00, tomas@poseidon.mysql.com +9 -9
    manual merge

ChangeSet@1.2392.54.8, 2007-03-09 10:17:21+01:00, df@pippilotta.erinye.com +1 -0
  BUG#25601 Missing m4 macro MYSQL_CHECK_TIME_T

  config/ac-macros/misc.m4@1.13, 2007-03-09 10:17:18+01:00, df@pippilotta.erinye.com +24 -0
    BUG#25601 MYSQL_CHECK_TIME_T macro is missing in 5.0 and upward, likely incorrectly merged up from 4.1. This patch is a verbatim copy from 4.1's acinclude.m4 (except for typos in comment).

ChangeSet@1.2392.47.23, 2007-03-09 10:44:48+03:00, anozdrin@booka.opbmk +1 -0
  Fix typo.

  sql/sql_show.cc@1.343, 2007-03-09 10:44:45+03:00, anozdrin@booka.opbmk +1 -1
    Fix typo.

ChangeSet@1.2392.47.22, 2007-03-09 08:05:08+03:00, anozdrin@booka.opbmk +13 -0
  Polishing: use constants instead of magic numbers.

  include/my_global.h@1.137, 2007-03-09 08:05:04+03:00, anozdrin@booka.opbmk +9 -0
    Introduce constants to be used instead of magic numbers.

  sql/field.cc@1.341.1.1, 2007-03-09 08:05:05+03:00, anozdrin@booka.opbmk +3 -3
    Polishing: use contants instead of magic numbers.

  sql/ha_innodb.cc@1.309, 2007-03-09 08:05:05+03:00, anozdrin@booka.opbmk +8 -8
    Polishing: use contants instead of magic numbers.

  sql/handler.cc@1.229, 2007-03-09 08:05:05+03:00, anozdrin@booka.opbmk +3 -3
    Polishing: use contants instead of magic numbers.

  sql/item.cc@1.251.2.1, 2007-03-09 08:05:05+03:00, anozdrin@booka.opbmk +3 -3
    Polishing: use contants instead of magic numbers.

  sql/item.h@1.218.1.1, 2007-03-09 08:05:05+03:00, anozdrin@booka.opbmk +6 -3
    Polishing: use contants instead of magic numbers.

  sql/item_func.cc@1.326.1.1, 2007-03-09 08:05:05+03:00, anozdrin@booka.opbmk +3 -2
    Polishing: use contants instead of magic numbers.

  sql/item_subselect.cc@1.154, 2007-03-09 08:05:05+03:00, anozdrin@booka.opbmk +2 -1
    Polishing: use contants instead of magic numbers.

  sql/log_event.cc@1.229, 2007-03-09 08:05:05+03:00, anozdrin@booka.opbmk +3 -2
    Polishing: use contants instead of magic numbers.

  sql/sql_base.cc@1.369.1.1, 2007-03-09 08:05:05+03:00, anozdrin@booka.opbmk +2 -1
    Polishing: use contants instead of magic numbers.

  sql/sql_select.cc@1.495.5.2, 2007-03-09 08:05:05+03:00, anozdrin@booka.opbmk +3 -3
    Polishing: use contants instead of magic numbers.

  sql/sql_show.cc@1.342, 2007-03-09 08:05:05+03:00, anozdrin@booka.opbmk +25 -18
    Polishing: use contants instead of magic numbers.

  sql/sql_table.cc@1.334, 2007-03-09 08:05:05+03:00, anozdrin@booka.opbmk +2 -1
    Polishing: use contants instead of magic numbers.

ChangeSet@1.2392.54.7, 2007-03-08 18:12:16+01:00, df@pippilotta.erinye.com +1 -0
  add comment to compiler_warnings.supp

  support-files/compiler_warnings.supp@1.9, 2007-03-08 18:12:14+01:00, df@pippilotta.erinye.com +5 -0
    add comment to make this file more useful

ChangeSet@1.2392.47.20, 2007-03-08 12:04:45+03:00, kostja@bodhi.local +2 -0
  Fix -ansi -pedantic warning (can't cast a pointer to function 
  to a pointer to object, that is, int foo(); void *bar= (void*) foo
  is not allowed.

  sql/lex.h@1.146, 2007-03-08 12:04:41+03:00, kostja@bodhi.local +2 -2
    Fix -ansi -pedantic warning.

  sql/lex_symbol.h@1.10, 2007-03-08 12:04:41+03:00, kostja@bodhi.local +1 -1
    Fix -ansi -pedantic warning.

ChangeSet@1.2377.50.6, 2007-03-08 15:37:53+07:00, tomas@poseidon.mysql.com +4 -0
  medium int printout support

  mysql-test/r/ndb_restore_print.result@1.3, 2007-03-08 15:37:45+07:00, tomas@poseidon.mysql.com +18 -0
    medium int printout support

  mysql-test/t/ndb_restore_print.test@1.3, 2007-03-08 15:37:45+07:00, tomas@poseidon.mysql.com +21 -0
    medium int printout support

  ndb/include/ndbapi/NdbRecAttr.hpp@1.19, 2007-03-08 15:37:46+07:00, tomas@poseidon.mysql.com +31 -0
    medium int printout support

  ndb/src/ndbapi/NdbRecAttr.cpp@1.32, 2007-03-08 15:37:46+07:00, tomas@poseidon.mysql.com +6 -2
    medium int printout support

ChangeSet@1.2377.50.5, 2007-03-08 10:39:35+07:00, tomas@poseidon.mysql.com +3 -0
     changed ndb_restore defaults handeling for structured printout
      extended ndb_restore_print test with tests

  mysql-test/r/ndb_restore_print.result@1.2, 2007-03-08 10:39:24+07:00, tomas@poseidon.mysql.com +197 -18
    extended ndb_restore_print test with tests

  mysql-test/t/ndb_restore_print.test@1.2, 2007-03-08 10:39:25+07:00, tomas@poseidon.mysql.com +29 -1
    extended ndb_restore_print test with tests

  ndb/tools/restore/restore_main.cpp@1.36.1.3, 2007-03-08 10:39:25+07:00, tomas@poseidon.mysql.com +8 -12
    changed ndb_restore defaults handeling for structured printout

ChangeSet@1.2377.50.4, 2007-03-08 00:26:23+07:00, tomas@poseidon.mysql.com +1 -0
  ndb - Bit formatting for printout wrong

  ndb/src/ndbapi/NdbRecAttr.cpp@1.31, 2007-03-08 00:26:14+07:00, tomas@poseidon.mysql.com +18 -9
    ndb - Bit formatting for printout wrong

ChangeSet@1.2392.47.19, 2007-03-07 09:53:46-07:00, malff@weblab.(none) +2 -0
  
  Bug 8407, post review cleanup: use instr::get_cont_dest() to get the instruction
  continuation instruction, for CONTINUE exception handlers.

  sql/sp_head.cc@1.237, 2007-03-07 09:53:43-07:00, malff@weblab.(none) +7 -13
    Post review cleanup: use instr::get_cont_dest() to get the instruction
    continuation instruction, for CONTINUE exception handlers.

  sql/sp_head.h@1.94, 2007-03-07 09:53:43-07:00, malff@weblab.(none) +12 -15
    Post review cleanup: use instr::get_cont_dest() to get the instruction
    continuation instruction, for CONTINUE exception handlers.

ChangeSet@1.2377.50.3, 2007-03-07 20:04:50+07:00, tomas@poseidon.mysql.com +1 -0
  remove extra ; causing compile errors on some platforms

  ndb/src/ndbapi/NdbRecAttr.cpp@1.30, 2007-03-07 20:04:40+07:00, tomas@poseidon.mysql.com +1 -1
    remove extra ; causing compile errors on some platforms

ChangeSet@1.2392.66.2, 2007-03-07 14:51:45+02:00, gkodinov@macbook.gmz +3 -0
  Bug #26672:
   DATE/DATETIME values are out of the currently supported
   4 basic value types (INT,STRING,REAL and DECIMAL).
   So expressions (not fields) of compile type DATE/DATETIME are 
   generally considered as STRING values. This is not so
   when they are compared : then they are compared as 
   INTEGER values.
   But the rule for comparison as INTEGERS must be checked
   explicitly each time when a comparison is to be performed.
   filesort is one such place. However there the check was 
   not done and hence the expressions (not fields) of type 
   DATE/DATETIME were sorted by their string representation.
   Fixed to compare them as INTEGER values for filesort.

  mysql-test/r/order_by.result@1.59.1.2, 2007-03-07 14:51:39+02:00, gkodinov@macbook.gmz +22 -0
    Bug #26672: test case

  mysql-test/t/order_by.test@1.42.1.2, 2007-03-07 14:51:40+02:00, gkodinov@macbook.gmz +15 -0
    Bug #26672: test case

  sql/filesort.cc@1.117, 2007-03-07 14:51:40+02:00, gkodinov@macbook.gmz +4 -1
    Bug #26672: sort dates/times as integers

ChangeSet@1.2377.50.2, 2007-03-07 13:19:37+07:00, tomas@poseidon.mysql.com +4 -0
  Bug#26899 ndb_restore cannot restore selected tables and databases
  Bug#26900 ndb_restore printout option does not give structured data
    - test cases

  mysql-test/include/ndb_backup.inc@1.1, 2007-03-07 13:19:28+07:00, tomas@poseidon.mysql.com +24 -0
    Bug#26899 ndb_restore cannot restore selected tables and databases
    Bug#26900 ndb_restore printout option does not give structured data
      - test cases
    

  mysql-test/include/ndb_backup.inc@1.0, 2007-03-07 13:19:28+07:00, tomas@poseidon.mysql.com +0 -0
    BitKeeper file /home/tomas/mysql-5.0-telco-gca-ndb_restore/mysql-test/include/ndb_backup.inc

  mysql-test/include/ndb_backup_print.inc@1.1, 2007-03-07 13:19:29+07:00, tomas@poseidon.mysql.com +6 -0
    Bug#26899 ndb_restore cannot restore selected tables and databases
    Bug#26900 ndb_restore printout option does not give structured data
      - test cases
    

  mysql-test/include/ndb_backup_print.inc@1.0, 2007-03-07 13:19:29+07:00, tomas@poseidon.mysql.com +0 -0
    BitKeeper file /home/tomas/mysql-5.0-telco-gca-ndb_restore/mysql-test/include/ndb_backup_print.inc

  mysql-test/r/ndb_restore_print.result@1.1, 2007-03-07 13:19:29+07:00, tomas@poseidon.mysql.com +124 -0
    Bug#26899 ndb_restore cannot restore selected tables and databases
    Bug#26900 ndb_restore printout option does not give structured data
      - test cases
    

  mysql-test/r/ndb_restore_print.result@1.0, 2007-03-07 13:19:29+07:00, tomas@poseidon.mysql.com +0 -0
    BitKeeper file /home/tomas/mysql-5.0-telco-gca-ndb_restore/mysql-test/r/ndb_restore_print.result

  mysql-test/t/ndb_restore_print.test@1.1, 2007-03-07 13:19:30+07:00, tomas@poseidon.mysql.com +140 -0
    Bug#26899 ndb_restore cannot restore selected tables and databases
    Bug#26900 ndb_restore printout option does not give structured data
      - test cases
    

  mysql-test/t/ndb_restore_print.test@1.0, 2007-03-07 13:19:30+07:00, tomas@poseidon.mysql.com +0 -0
    BitKeeper file /home/tomas/mysql-5.0-telco-gca-ndb_restore/mysql-test/t/ndb_restore_print.test

ChangeSet@1.2377.50.1, 2007-03-07 13:18:08+07:00, tomas@poseidon.mysql.com +7 -0
  Bug#26899 ndb_restore cannot restore selected tables and databases
  Bug#26900 ndb_restore printout option does not give structured data
  - add data stucturing options
  - add database and table selection options

  ndb/include/ndbapi/NdbRecAttr.hpp@1.18, 2007-03-07 13:18:01+07:00, tomas@poseidon.mysql.com +19 -0
    add formatting option to ndb recattr printing

  ndb/include/util/OutputStream.hpp@1.4.2.1, 2007-03-07 13:18:01+07:00, tomas@poseidon.mysql.com +2 -1
    getter for FILE*

  ndb/src/ndbapi/NdbRecAttr.cpp@1.29, 2007-03-07 13:18:01+07:00, tomas@poseidon.mysql.com +103 -24
    add formatting option to ndb recattr printing

  ndb/tools/restore/Restore.cpp@1.30, 2007-03-07 13:18:01+07:00, tomas@poseidon.mysql.com +54 -6
    add formatting option to restore printing
    adoption to 5.1 source code

  ndb/tools/restore/Restore.hpp@1.20.1.2, 2007-03-07 13:18:01+07:00, tomas@poseidon.mysql.com +16 -2
    restore adoption to 5.1

  ndb/tools/restore/consumer_printer.cpp@1.5, 2007-03-07 13:18:01+07:00, tomas@poseidon.mysql.com +17 -5
    add formatting option to restore printing

  ndb/tools/restore/restore_main.cpp@1.36.1.2, 2007-03-07 13:18:01+07:00, tomas@poseidon.mysql.com +335 -70
    added option to restore only selected databases and tables
    added option to get CSV printout to file and stdout
    add formatting option to restore printing
    adoption to 5.1 source code

ChangeSet@1.2377.39.9, 2007-03-07 10:46:44+07:00, tomas@poseidon.mysql.com +5 -0
  Bug#25275 SINGLE USER MODE prevents ALTER on non-ndb tables for other mysqld nodes
  - refactor single user and move single user checks from api to kernel

  ndb/src/kernel/blocks/dbtc/Dbtc.hpp@1.36.2.1, 2007-03-07 10:46:37+07:00, tomas@poseidon.mysql.com +8 -3
    Bug#25275 SINGLE USER MODE prevents ALTER on non-ndb tables for other mysqld nodes
    - refactor single user and move single user checks from api to kernel

  ndb/src/kernel/blocks/dbtc/DbtcMain.cpp@1.103.2.1, 2007-03-07 10:46:37+07:00, tomas@poseidon.mysql.com +118 -15
    Bug#25275 SINGLE USER MODE prevents ALTER on non-ndb tables for other mysqld nodes
    - refactor single user and move single user checks from api to kernel

  ndb/src/ndbapi/ClusterMgr.cpp@1.33, 2007-03-07 10:46:37+07:00, tomas@poseidon.mysql.com +1 -1
    Bug#25275 SINGLE USER MODE prevents ALTER on non-ndb tables for other mysqld nodes
    - refactor single user and move single user checks from api to kernel

  ndb/src/ndbapi/Ndb.cpp@1.62.2.1, 2007-03-07 10:46:38+07:00, tomas@poseidon.mysql.com +11 -0
    Bug#25275 SINGLE USER MODE prevents ALTER on non-ndb tables for other mysqld nodes
    - refactor single user and move single user checks from api to kernel

  ndb/src/ndbapi/TransporterFacade.hpp@1.30, 2007-03-07 10:46:38+07:00, tomas@poseidon.mysql.com +5 -11
    Bug#25275 SINGLE USER MODE prevents ALTER on non-ndb tables for other mysqld nodes
    - refactor single user and move single user checks from api to kernel

ChangeSet@1.1616.2985.1, 2007-03-05 11:35:04+04:00, holyfoot@mysql.com +1 -0
  bug #25492 (Invalid deallocation in mysql_stmt_fetch())
  
  Additional patch.
  mysql_flush_use_result() fixed.

  libmysqld/lib_sql.cc@1.75.1.63, 2007-03-05 11:35:02+04:00, holyfoot@mysql.com +8 -14
    now emb_flush_use_result() uses emb_free_rows()
    duplicating code removed

ChangeSet@1.2392.35.7, 2007-03-01 20:58:51+01:00, df@pippilotta.erinye.com +1 -0
  BUG#26701 check-cpu compile flags in x86-64 doesn't support gcc < 3.4,
  apply suggestion from jocelyn fournier

  BUILD/check-cpu@1.18.1.1, 2007-03-01 20:58:50+01:00, df@pippilotta.erinye.com +8 -1
    BUG#26701 check-cpu compile flags in x86-64 doesn't support gcc < 3.4,
    apply suggestion from jocelyn fournier

ChangeSet@1.2377.46.1, 2007-03-01 15:13:33+08:00, Justin.He@dev3-240.dev.cn.tlan +5 -0
  correct NAND/NOR scan operations, and add a test case for it.

  ndb/src/ndbapi/NdbScanFilter.cpp@1.8.1.2, 2007-03-01 15:13:31+08:00, Justin.He@dev3-240.dev.cn.tlan +45 -1
    translate NAND/NOR into AND/OR, since AND/OR operations are all correct

  ndb/test/include/NDBT_Test.hpp@1.15, 2007-03-01 15:13:31+08:00, Justin.He@dev3-240.dev.cn.tlan +6 -0
    add a new method executeOneCtx() in class NDBT_TestSuite, declare it

  ndb/test/ndbapi/Makefile.am@1.29, 2007-03-01 15:13:31+08:00, Justin.He@dev3-240.dev.cn.tlan +2 -0
    Add a new test case: testScanFIlter.cpp to test/ndbapi/,
    thus modify the Makefile.am related to it

  ndb/test/ndbapi/testScanFilter.cpp@1.1, 2007-03-01 15:13:31+08:00, Justin.He@dev3-240.dev.cn.tlan +851 -0
    It's a test case for ndbapi scan filter, test for AND/OR/NAND/NOR scan operations.

  ndb/test/ndbapi/testScanFilter.cpp@1.0, 2007-03-01 15:13:31+08:00, Justin.He@dev3-240.dev.cn.tlan +0 -0

  ndb/test/src/NDBT_Test.cpp@1.27, 2007-03-01 15:13:31+08:00, Justin.He@dev3-240.dev.cn.tlan +57 -0
    add a new method in class NDBT_TestSuite in order to adapt to 
    some customized test cases, because the default NDBT's test talbes
    and flow are fixed, if just modify related existing methods, it will
    influence other test cases in test/ndbapi/

ChangeSet@1.2392.13.6, 2007-02-23 18:49:41+02:00, gkodinov@macbook.gmz +3 -0
  Bug #26186: 
  When handling DELETE ... FROM if there is no
  condition it is internally transformed to 
  TRUNCATE for more efficient execution by the
  storage handler.
  The check for validity of the optional ORDER BY 
  clause is done after the check for the above 
  optimization and will not be performed if the
  optimization can be applied.
  Moved the validity check for ORDER BY before 
  the optimization so it performed regardless of
  the optimization.

  mysql-test/r/delete.result@1.28, 2007-02-23 18:49:33+02:00, gkodinov@macbook.gmz +9 -0
    Bug #26186: test case

  mysql-test/t/delete.test@1.26, 2007-02-23 18:49:34+02:00, gkodinov@macbook.gmz +18 -0
    Bug #26186: test case

  sql/sql_delete.cc@1.193, 2007-02-23 18:49:34+02:00, gkodinov@macbook.gmz +21 -16
    Bug #26186: do validity check of the ORDER BY
    before deciding to skip it.

ChangeSet@1.2392.16.1, 2007-02-15 14:08:21+01:00, Kristofer.Pettersson@naruto. +2 -0
  Bug#25042 OPTIMIZE TABLE cause race condition in IO CACHE SHARE
  
  - The condition variable implementation "lost" a signal to
    WaitOnSingleObject when a semaphore was released.
  - The signal could be consumed by a new call to pthread_cond_wait
    before all waiting threads had awoken.
  - The new implementation of pthread_cond_* uses events
    instead of semaphores. It also uses an extra lock to protect entry
    into new cond wait before the broadcast has finished.

  include/my_pthread.h@1.95.1.4, 2007-02-15 14:08:17+01:00, Kristofer.Pettersson@naruto. +11 -5
    - New implementatin of pthread_cond_init. This version uses events
      instead of semaphores

  mysys/my_wincond.c@1.10, 2007-02-15 14:08:17+01:00, Kristofer.Pettersson@naruto. +111 -38
    - New implementatin of pthread_cond_init. This version uses events
      instead of semaphores

ChangeSet@1.1616.2976.1, 2007-02-15 16:52:23+08:00, gni@dev3-221.dev.cn.tlan +1 -0
  BUG#21715 mgm client command <id> status return version(0.0.0.0)

  ndb/src/mgmclient/CommandInterpreter.cpp@1.44.4.1, 2007-02-15 16:52:22+08:00, gni@dev3-221.dev.cn.tlan +13 -0
    Adding the judgement for node type to distinguish the data nodes and non-data nodes.
    From the return value. Management client can't distinguish the really not connected
    status for data nodes and status of non-data nodes.
    We can get the connect status about non-data nodes from version, if the version is 0, 
    it means no connected status.

ChangeSet@1.2256.2.2, 2007-02-12 16:35:32+08:00, gni@dev3-221.dev.cn.tlan +1 -0
  BUG#19378 Job Buffer Full error appears for too large MaxNoOfTables

  ndb/src/mgmsrv/ConfigInfo.cpp@1.80.2.1, 2007-02-12 16:35:30+08:00, gni@dev3-221.dev.cn.tlan +1 -1
    The high bound of MaxNoOfTables changes into MAX_TABLES defined in ndb_limits.h

ChangeSet@1.2281.4.17, 2007-02-09 16:31:12+01:00, mskold@mysql.com +2 -0
  bug #26225  Engine condition pushdown doesn't work with prepare statements (ps_7ndb): ensure that query plan for prepared statement is analyzed correctly

  sql/ha_ndbcluster.cc@1.285.1.11, 2007-02-09 16:30:46+01:00, mskold@mysql.com +1 -1
    bug #26225  Engine condition pushdown doesn't work with prepare statements (ps_7ndb): ensure that query plan for prepared statement is analyzed correctly

  sql/item_func.cc@1.307.5.1, 2007-02-09 16:30:46+01:00, mskold@mysql.com +2 -0
    bug #26225  Engine condition pushdown doesn't work with prepare statements (ps_7ndb): ensure that query plan for prepared statement is analyzed correctly

ChangeSet@1.2392.7.2, 2007-02-08 12:53:18+04:00, ramil@mysql.com +4 -0
  After merge fix.
  Reverted fix for 19370 DateTime datatype in MySQL has two bugs in it
  as it's not a bug.

  mysql-test/r/date_formats.result@1.33, 2007-02-08 12:53:17+04:00, ramil@mysql.com +1 -3
    After merge fix.
    Reverted fix for 19370 DateTime datatype in MySQL has two bugs in it
    as it's not a bug.

  mysql-test/r/strict.result@1.32, 2007-02-08 12:53:17+04:00, ramil@mysql.com +4 -10
    After merge fix.
    Reverted fix for 19370 DateTime datatype in MySQL has two bugs in it
    as it's not a bug.

  mysql-test/r/type_datetime.result@1.34, 2007-02-08 12:53:17+04:00, ramil@mysql.com +1 -3
    After merge fix.
    Reverted fix for 19370 DateTime datatype in MySQL has two bugs in it
    as it's not a bug.

  mysql-test/t/strict.test@1.25, 2007-02-08 12:53:17+04:00, ramil@mysql.com +0 -8
    After merge fix.
    Reverted fix for 19370 DateTime datatype in MySQL has two bugs in it
    as it's not a bug.

ChangeSet@1.1616.2970.1, 2007-02-08 11:56:18+04:00, ramil@mysql.com +2 -0
  Fix for bug #25301: Non-zero dates with year 0000 are invalid
  
  The 0000 year is valid.
  The ISO standard for "Representation of dates and times" says:
  "Calendar years are numbered in ascending order according to the 
  Gregorian calendar by values in the range [0000] to [9999]."
  
  Reverted fix for 21789: DATETIME with 0000-00-00 11:22:33 should be invalid, but is accepted
  as it's not a bug.
  
  Fix for 19370: DateTime datatype in MySQL has two bugs in it
  will be reverted during 4.1 -> 5.0 merging as it was pushed to the 
  5.0 tree.

  mysql-test/r/date_formats.result@1.15.1.11, 2007-02-08 11:56:17+04:00, ramil@mysql.com +18 -39
    Fix for bug #25301: Non-zero dates with year 0000 are invalid
      - reverted fix for bug #21789: DATETIME with 0000-00-00 11:22:33 should be invalid, but is accepted

  sql-common/my_time.c@1.6.5.1, 2007-02-08 11:56:17+04:00, ramil@mysql.com +1 -4
    Fix for bug #25301: Non-zero dates with year 0000 are invalid
      - reverted fix for bug #21789: DATETIME with 0000-00-00 11:22:33 should be invalid, but is accepted

ChangeSet@1.2294.56.3, 2007-01-29 15:17:40+00:00, lzhou@dev3-63.(none) +1 -0
  Bug#23354 Add explaination when ndb_mgm do restart

  ndb/src/mgmclient/CommandInterpreter.cpp@1.73, 2007-01-29 15:17:35+00:00, lzhou@dev3-63.(none) +3 -0
    Add printout to indicate the usage of "-n"

ChangeSet@1.2327.3.3, 2006-12-22 09:29:28+04:00, ramil@mysql.com +4 -0
  Fix for bug #21976: Unnecessary warning with count(decimal)
  
  We use val_int() calls (followed by null_value check) to determine 
  nullness in some Item_sum_count' and Item_sum_count_distinct' methods, 
  as a side effect we get extra warnings raised in the val_int().
  Fix: use is_null() instead.

  mysql-test/r/func_group.result@1.53.1.1, 2006-12-22 09:29:26+04:00, ramil@mysql.com +10 -0
    Fix for bug #21976: Unnecessary warning with count(decimal)
      - test result.

  mysql-test/t/func_group.test@1.49.1.1, 2006-12-22 09:29:26+04:00, ramil@mysql.com +11 -0
    Fix for bug #21976: Unnecessary warning with count(decimal)
      - test case.

  sql/item.h@1.209.3.1, 2006-12-22 09:29:26+04:00, ramil@mysql.com +5 -6
    Fix for bug #21976: Unnecessary warning with count(decimal)
      - comment adjusted.
    

  sql/item_sum.cc@1.185.2.1, 2006-12-22 09:29:26+04:00, ramil@mysql.com +5 -27
    Fix for bug #21976: Unnecessary warning with count(decimal)
      - use is_null() to determine nullness.

ChangeSet@1.2216.61.2, 2006-09-07 18:51:00+04:00, kroki@moonlight.intranet +3 -0
  BUG#20492: Subsequent calls to stored procedure yield incorrect result
             if join is used
  
  For procedures with selects that use complicated joins with ON expression
  re-execution could erroneously ignore this ON expression, giving
  incorrect result.
  
  The problem was that optimized ON expression wasn't saved for
  re-execution.  The solution is to properly save it.

  mysql-test/r/sp.result@1.210.1.1, 2006-09-07 18:50:57+04:00, kroki@moonlight.intranet +26 -0
    Add result for bug#20492: Subsequent calls to stored procedure yield
    incorrect result if join is used.

  mysql-test/t/sp.test@1.198.1.1, 2006-09-07 18:50:57+04:00, kroki@moonlight.intranet +41 -0
    Add test case for bug#20492: Subsequent calls to stored procedure yield
    incorrect result if join is used.

  sql/sql_select.cc@1.439.6.1, 2006-09-07 18:50:58+04:00, kroki@moonlight.intranet +8 -3
    Save modified ON expression for re-execution.

