ChangeSet@1.2468.1.1, 2007-05-02 15:50:08+02:00, df@pippilotta.erinye.com +1 -0
  generate map files on windows

  CMakeLists.txt@1.7.1.1, 2007-05-02 15:50:06+02:00, df@pippilotta.erinye.com +3 -0
    Generate map files for executables

ChangeSet@1.2473, 2007-04-30 14:22:38+02:00, dfischer@mysql.com +2 -0
  create_manifest.js, mysql_manifest.cmake:
    add files for patch

  win/create_manifest.js@1.1, 2007-04-30 14:22:13+02:00, dfischer@mysql.com +85 -0
    add files for patch

  win/create_manifest.js@1.0, 2007-04-30 14:22:13+02:00, dfischer@mysql.com +0 -0

  win/mysql_manifest.cmake@1.1, 2007-04-30 14:22:19+02:00, dfischer@mysql.com +20 -0
    add files for patch

  win/mysql_manifest.cmake@1.0, 2007-04-30 14:22:19+02:00, dfischer@mysql.com +0 -0

ChangeSet@1.2472, 2007-04-30 13:30:58+02:00, dfischer@mysql.com +1 -0
  Makefile.am:
    fix typo

  win/Makefile.am@1.5, 2007-04-30 13:30:46+02:00, dfischer@mysql.com +1 -1
    fix typo

ChangeSet@1.2471, 2007-04-30 11:41:19+02:00, dfischer@mysql.com +10 -0
  backport vista manifest patch

  CMakeLists.txt@1.8, 2007-04-30 11:41:04+02:00, dfischer@mysql.com +27 -0
    backport vista manifest patch

  client/CMakeLists.txt@1.6, 2007-04-30 11:41:04+02:00, dfischer@mysql.com +14 -0
    backport vista manifest patch

  extra/CMakeLists.txt@1.5, 2007-04-30 11:41:05+02:00, dfischer@mysql.com +7 -0
    backport vista manifest patch

  libmysql/CMakeLists.txt@1.3, 2007-04-30 11:41:05+02:00, dfischer@mysql.com +5 -0
    backport vista manifest patch

  myisam/CMakeLists.txt@1.3, 2007-04-30 11:41:05+02:00, dfischer@mysql.com +8 -0
    backport vista manifest patch

  server-tools/instance-manager/CMakeLists.txt@1.3, 2007-04-30 11:41:05+02:00, dfischer@mysql.com +5 -0
    backport vista manifest patch

  sql/CMakeLists.txt@1.7, 2007-04-30 11:41:08+02:00, dfischer@mysql.com +5 -0
    backport vista manifest patch

  win/Makefile.am@1.4, 2007-04-30 11:41:08+02:00, dfischer@mysql.com +2 -1
    backport vista manifest patch

  win/README@1.4, 2007-04-30 11:41:08+02:00, dfischer@mysql.com +2 -0
    backport vista manifest patch

  win/configure.js@1.5, 2007-04-30 11:41:08+02:00, dfischer@mysql.com +1 -0
    backport vista manifest patch

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

  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.2392.104.27, 2007-04-20 14:01:49+02:00, df@pippilotta.erinye.com +1 -0
  win32 build fix

  VC++Files/sql/mysqld.vcproj@1.13, 2007-04-20 14:01:48+02:00, df@pippilotta.erinye.com +3 -75
    win32 build fix

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.416.1.22, 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.188.1.9, 2007-04-17 12:31:58+02:00, serg@janus.mylan +3 -6
    reverted the fix for Bug#5507

  sql/sql_lex.cc@1.217.1.2, 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.416.1.21, 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.2392.104.26, 2007-04-16 15:00:16-04:00, cmiller@zippy.cornsilk.net +2 -0
  Bug#25347: mysqlcheck -A -r doesn't repair table marked as crashed
  
  Additional changes to test:  "flush tables" so that Windows releases
  the files.

  mysql-test/r/mysqlcheck.result@1.5, 2007-04-16 15:00:13-04:00, cmiller@zippy.cornsilk.net +26 -1
    Add "flush tables" to get windows to release the files, so that 
    we can test truncation properly.

  mysql-test/t/mysqlcheck.test@1.6, 2007-04-16 15:00:13-04:00, cmiller@zippy.cornsilk.net +8 -0
    Add "flush tables" to get windows to release the files, so that 
    we can test truncation properly.

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.188.1.8, 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.217.1.1, 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.20.1.1, 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.139.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.416.7.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.2392.104.25, 2007-04-10 16:47:07-04:00, cmiller@zippy.cornsilk.net +1 -0
  Use platform-independent mysqltest language.

  mysql-test/t/mysqlcheck.test@1.5, 2007-04-10 16:47:06-04:00, cmiller@zippy.cornsilk.net +3 -2
    Use platform-independent mysqltest language.

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.2392.104.24, 2007-04-06 09:15:18-04:00, cmiller@zippy.cornsilk.net +3 -0
  Changing the state of whether we're recording profiling information
  halfway through a query (as happens in "SET SESSION PROFILING = ...")
  has a few side-effects, the worst of which is a memory leak for
  prepared statements, which poke directly from the parser into the 
  profiling code (we don't have the query text when we need it) and 
  that overwrites a pointer to heap-allocated memory when the previous
  statement turns on profiling.
  
  Instead, now set a flag when we begin a new statement that tracks 
  whether profiling is on _at the start_ of the query.  Use that to
  track whether we gather info.
  
  Additionally, use that AND use the state of the profiling variable
  after the end of a query to know whether to store information about 
  the query that just finished.

  mysql-test/r/profiling.result@1.5, 2007-04-06 09:15:16-04:00, cmiller@zippy.cornsilk.net +126 -127
    Testing whether profiling is on at the beginning of a query and at
    the end of a query makes "SET SESSION PROFILING = ..." statements
    disappear from the profiling.  They were never reliable before.

  sql/sql_profile.cc@1.9, 2007-04-06 09:15:16-04:00, cmiller@zippy.cornsilk.net +15 -3
    Check to see if profiling was enabled at the beginning of this query
    before trying to store query_source.  This avoids a memory leak for
    prepared statements, which get here by direct means.
    
    If profiling was toggled in this query, then don't store this query
    profile.

  sql/sql_profile.h@1.5, 2007-04-06 09:15:16-04:00, cmiller@zippy.cornsilk.net +1 -0
    Keep track of whether profiling is on.

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.416.1.19, 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.2392.104.23, 2007-04-04 07:44:12-04:00, cmiller@zippy.cornsilk.net +1 -0
  Backport:
  
  B-g#27427: resolveip fails on hostnames with a leading digit
  
  We need inet_aton for the extra/resolveip tool.  Some OSes put this
  in nonstandard libraries.

  configure.in@1.425, 2007-04-04 07:44:10-04:00, cmiller@zippy.cornsilk.net +1 -0
    We need inet_aton for the extra/resolveip tool.

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.2392.104.22, 2007-04-03 19:52:24-04:00, cmiller@zippy.cornsilk.net +2 -0
  Unreported minor bug:  We start numbering query IDs at zero, which
  is a special case in "SHOW PROFILE FOR QUERY n".  No one can get
  the zero item (which is always the statement that turns on profiling),
  because zero represents the final item, internally.
  
  Now, order the queries starting at one.

  mysql-test/r/profiling.result@1.4, 2007-04-03 19:52:23-04:00, cmiller@zippy.cornsilk.net +127 -127
    Renumber the query IDs.

  sql/sql_profile.cc@1.8, 2007-04-03 19:52:23-04:00, cmiller@zippy.cornsilk.net +2 -2
    Start the profile_id_counter at 1, to overstep the special-case 
    value of zero.
    
    Unrelated, but looks similar: don't use -1 to initialize an unsigned 
    integer field.  That causes warnings in some environments.

ChangeSet@1.2392.104.21, 2007-04-03 19:50:55-04:00, cmiller@zippy.cornsilk.net +2 -0
  Backport:
  
  B-g#27501: 5.0 significantly more sys ("kernel") time than 4.1 \
        due to getrusage() calls
  
  Even if profiling is turned off, the parser makes calls to reset 
  the state at the beginning of each query.  That would eventually 
  instantiate a PROFILE_ENTRY, which does indeed capture resource 
  usage.
  
  Instead, now check that profiling is active before progressing
  far into the storage/expiration of old entries in the history.
  This has the pleasant side-effect that queries to toggle profiling
  are not recorded in the history.

  mysql-test/r/profiling.result@1.3, 2007-04-03 19:50:53-04:00, cmiller@zippy.cornsilk.net +1 -1
    Now after we turn off profiling, the beginning of the next query 
    refuses to enter the profiling code and it discards the info.

  sql/sql_profile.cc@1.7, 2007-04-03 19:50:53-04:00, cmiller@zippy.cornsilk.net +11 -0
    Add the same condition twice:  Once to abort storing previous 
    query information and the other to abort initialization for this 
    query that is starting.
    
    We do this symmetrically, before and after expiring old history 
    entries, so that the counts are correct.

ChangeSet@1.2392.104.20, 2007-04-03 19:47:19-04:00, cmiller@zippy.cornsilk.net +1 -0
  Backport:
  
  B-g#26600: table PROFILING in INFORMATION SCHEMA has wrong data type
  
  B-g#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.341.2.2, 2007-04-03 19:47:17-04:00, cmiller@zippy.cornsilk.net +9 -0
    Add floating-point types to Information_schema output.

ChangeSet@1.2392.104.19, 2007-04-03 19:45:28-04:00, cmiller@zippy.cornsilk.net +1 -0
  Backport:
  
  B-g#27060: SQL Profile utility may not be reporting right duration \
        for each step
  
  Whenever the profiler is reset at the beginning of a query, there's
  a "hidden" profiling entry that represents that point in time.  It 
  has no status description, as those are set by state changes and no
  such point has yet been encountered.  That profiling entry is not
  in the list of entries generated when we change states.
  
  The profiling code had the problem that each step of printing 
  profiling data subtracted the previous "step"'s data, but gave the
  label to that data of the current step, which is wrong.  The label/
  state refers to the period beginning with that profiling data, not
  ending with it.
  
  Now, give a label to the first profiling pseudo-entry, so that we 
  have a name to assign to the period that ends with the first state 
  change.  Now also use the state name of the previous step in showing 
  the delta values that end with this step.

  sql/sql_profile.cc@1.6, 2007-04-03 19:45:26-04:00, cmiller@zippy.cornsilk.net +61 -46
    Store a status of "initializing" whenever we construct the first
    profile entry -- the one that gets reset whenever we're starting 
    a new query, before the server sets a real status.
    
    Additionally, associate the previous status with the time period
    that ends with the current profile entry's stats.
    
    Since we need yet another piece of info from the previous profiling
    entry, take out the piecemeal ways we currently do it and make a
    general pointer to the whole thing.

ChangeSet@1.2392.104.18, 2007-04-03 18:12:31-04:00, cmiller@zippy.cornsilk.net +3 -0
  Backport:
  
  Patch contributed by Jocelyn Fournier.  CLA received 2007-02-27.
    
  B-g#25347: mysqlcheck -A -r doesn't repair table marked as crashed
    
  mysqlcheck tests nullness of the engine type to know whether the
  "table" is a view or not.  That also falsely catches tables that 
  are severly damaged.
    
  Instead, use SHOW FULL TABLES to test whether a "table" is a view
  or not.
    
  (Don't add new function.  Instead, get original data a smarter way.)
  
  Make it safe for use against databases before when views appeared.

  client/mysqlcheck.c@1.59, 2007-04-03 18:12:29-04:00, cmiller@zippy.cornsilk.net +15 -12
    Use SHOW FULL TABLES to test better whether a name in the table
    list is one of a view.  Checking that the engine is NULL is 
    insufficient.
    
    Implemented suggestion from jimw that involved removing most of 
    original patch and getting data a better way

  mysql-test/r/mysqlcheck.result@1.4, 2007-04-03 18:12:29-04:00, cmiller@zippy.cornsilk.net +10 -0
    Verify that tables that have NULL/unreadable engine types are 
    processed and not interpreted as views.

  mysql-test/t/mysqlcheck.test@1.4, 2007-04-03 18:12:29-04:00, cmiller@zippy.cornsilk.net +16 -0
    Verify that tables that have NULL/unreadable engine types are 
    processed and not interpreted as views.

ChangeSet@1.2392.104.17, 2007-04-03 17:59:52-04:00, cmiller@zippy.cornsilk.net +2 -0
  Backport:
  
  B-g#24795: SHOW PROFILE implementation
  
  Don't use memory roots to store profiling information, because
  memory roots make freeing the data a no-op, and thus long-running
  processes with profiling turned on the whole time could eventually 
  use all available memory.
  
  Instead, use regular heap allocation and deallocation calls to 
  manage profiling data.  Replace the leaky List usage with a similar-
  behaving structure named "Queue".

  sql/sql_profile.cc@1.5, 2007-04-03 17:59:50-04:00, cmiller@zippy.cornsilk.net +39 -72
    Don't use C++ iterators on our simple Queue implementation.  They're
    not implemented and we don't really need them.
    
    Rip out idea of swapping out the thd's mem_root.

  sql/sql_profile.h@1.4, 2007-04-03 17:59:50-04:00, cmiller@zippy.cornsilk.net +108 -3
    Rip out idea of needing a mem_root.
    
    Implement a Queue that looks and behaves very similarly to memroot-
    using List.

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.104.16, 2007-04-03 14:08:09-04:00, cmiller@zippy.cornsilk.net +3 -0
  Backport of Igor's patch for Bug#27362, March 22 2007.
  
  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.33.1.1, 2007-04-03 14:08:07-04:00, cmiller@zippy.cornsilk.net +5 -0
    Added a test case for bug #27362.

  mysql-test/t/func_in.test@1.27.1.1, 2007-04-03 14:08:07-04:00, cmiller@zippy.cornsilk.net +11 -0
    Added a test case for bug #27362.

  sql/item_cmpfunc.cc@1.240.1.2, 2007-04-03 14:08:07-04:00, cmiller@zippy.cornsilk.net +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.104.15, 2007-04-03 14:05:00-04:00, cmiller@zippy.cornsilk.net +2 -0
  The test suite erroneously removes backslashes.

  mysql-test/r/profiling.result@1.2, 2007-04-03 14:04:58-04:00, cmiller@zippy.cornsilk.net +1 -1
    The test suite erroneously removes backslashes.

  mysql-test/t/profiling.test@1.2, 2007-04-03 14:04:58-04:00, cmiller@zippy.cornsilk.net +1 -1
    The test suite erroneously removes backslashes.

ChangeSet@1.2392.104.14, 2007-04-03 13:26:19-04:00, cmiller@zippy.cornsilk.net +1 -0
  Listing all columns of a particular type tells us nothing at all.  
  The test fails, and it shouldn't.

  mysql-test/r/information_schema.result@1.123, 2007-04-03 13:26:17-04:00, cmiller@zippy.cornsilk.net +1 -1
    The query to generate this list is pretty bogus in any case.  Listing 
    all columns of a particular type tells us nothing at all.

ChangeSet@1.2392.89.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.2.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.96.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.7.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.360.1.14, 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.211.1.17, 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.138.2.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.108.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.138.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.416.1.18, 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.102.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.137.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.136.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.117.1.4, 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.132.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.135.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.2.1, 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.93.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.134.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.133.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.108.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.60.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.131.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.130.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.360.13.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.314.1.13, 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.211.1.16, 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.123.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.129.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.127.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.126.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.108.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.93.1.2, 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.360.14.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.138.1.2, 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.123.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.124.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.123.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.113.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.121.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.118.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.96.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.116.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.1616.2999.1, 2007-03-20 19:36:11+01:00, joerg@trift2. +2 -0
  Test "help": 
  Shift the ID values up into a range where they will not collide with those
  which we use for real data, when we fill the system tables.
  
  Will be merged up to 5.0 where it is needed for 5.0.38.

  mysql-test/r/help.result@1.4.1.1, 2007-03-20 19:36:09+01:00, joerg@trift2. +44 -44
    Fix the result file according to the changed ID values in "help.test".

  mysql-test/t/help.test@1.6.1.1, 2007-03-20 19:36:09+01:00, joerg@trift2. +22 -22
    Now that (at least in 5.0) the system tables are filled with real data,
    inserting rows vith ID values 1 .. 5 will fail in release build tests (it did in 5.0.38)
    like it should already have done in customer installations.
    
    Shift the ID values up into a high area where they will not conflict,
    also make the distinct for the different kinds of values (= unique throughout the test).
    
    No change to the logic.

ChangeSet@1.1616.2998.1, 2007-03-20 19:19:17+01:00, joerg@trift2. +1 -0
  Test "help": 
  Shift the ID values up into a range where they will not collide with those
  which we use for real data, when we fill the system tables.
  
  Will be merged up to 5.0 where it is needed for 5.0.38.

  mysql-test/t/help.test@1.7, 2007-03-20 19:19:15+01:00, joerg@trift2. +22 -22
    Now that (at least in 5.0) the system tables are filled with real data,
    inserting rows vith ID values 1 .. 5 will fail in release build tests (it did in 5.0.38)
    like it should already have done in customer installations.
    
    Shift the ID values up into a high area where they will not conflict,
    also make the distinct for the different kinds of values (= unique throughout the test).
    
    No change to the logic.

ChangeSet@1.1616.2997.1, 2007-03-20 19:09:28+01:00, tsmith@quadxeon.mysql.com +1 -0
  Bug #27231: Server crash when dumping into outfile with long FIELDS ENCLOSED BY option
  - Problem: data separators were copied to a fixed-size buffer
    on the stack; memcpy was used, without bounds checking; a
    server crash could result if long FIELDS ENCLOSED BY, etc.,
    was given
  - Fix: write the separators directly, instead of copying to
    a buffer first (in select_export::send_data())

  sql/sql_class.cc@1.105.1.109, 2007-03-20 18:59:23+01:00, tsmith@quadxeon.mysql.com +6 -8
    In select_export::send_data(), write data separators
    directly, instead of copying into a fixed-size memory
    buffer before writing.  This avoids a buffer overflow
    when very large separators are specified.

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.360.12.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.314.9.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.11.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.2392.104.10, 2007-03-20 15:12:50+01:00, kent@mysql.com +6 -0
  vio.vcproj, mysqld.vcproj, mysys.vcproj, libmysqld.vcproj, mysqldemb.vcproj:
    No need to set LICENSE or USE_SYMDIR from project files
  make_win_bin_dist:
    Changed location of SQL initialization files to be "share/"

  VC++Files/libmysqld/libmysqld.vcproj@1.8, 2007-03-20 14:59:06+01:00, kent@mysql.com +10 -10
    No need to set LICENSE or USE_SYMDIR from project files

  VC++Files/mysqldemb/mysqldemb.vcproj@1.5, 2007-03-20 14:59:06+01:00, kent@mysql.com +10 -10
    No need to set LICENSE or USE_SYMDIR from project files

  VC++Files/mysys/mysys.vcproj@1.13, 2007-03-20 14:59:06+01:00, kent@mysql.com +3 -3
    No need to set LICENSE or USE_SYMDIR from project files

  VC++Files/sql/mysqld.vcproj@1.10.1.2, 2007-03-20 14:59:06+01:00, kent@mysql.com +4 -4
    No need to set LICENSE or USE_SYMDIR from project files

  VC++Files/vio/vio.vcproj@1.3, 2007-03-20 14:59:06+01:00, kent@mysql.com +1 -1
    No need to set LICENSE or USE_SYMDIR from project files

  scripts/make_win_bin_dist@1.12, 2007-03-20 14:57:45+01:00, kent@mysql.com +3 -0
    Changed location of SQL initialization files to be "share/"

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.112.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.111.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.110.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.211.1.14, 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.104.9, 2007-03-19 22:41:16+01:00, kent@mysql.com +3 -0
  mysys.vcproj:
    Removed accidently added my_winsem.c
  make_win_bin_dist:
    Corrected test for relwithdebinfo target
  mysql.sln:
    Specify that comp_err depends on zlib

  VC++Files/mysql.sln@1.17, 2007-03-19 21:14:15+01:00, kent@mysql.com +1 -0
    Specify that comp_err depends on zlib

  VC++Files/mysys/mysys.vcproj@1.12, 2007-03-19 21:13:24+01:00, kent@mysql.com +0 -3
    Removed accidently added my_winsem.c

  scripts/make_win_bin_dist@1.11, 2007-03-19 22:41:03+01:00, kent@mysql.com +1 -1
    Corrected test for relwithdebinfo target

ChangeSet@1.2392.104.8, 2007-03-19 16:45:37+01:00, kent@mysql.com +1 -0
  make_win_bin_dist:
    Restore accidently removed line

  scripts/make_win_bin_dist@1.10, 2007-03-19 16:45:29+01:00, kent@mysql.com +1 -0
    Restore accidently removed line

ChangeSet@1.2392.104.7, 2007-03-19 16:18:10+01:00, kent@mysql.com +46 -0
  Many files:
    Major cleanup of old Visual Studio project files, aligning engines etc

  VC++Files/bdb/bdb.vcproj@1.3, 2007-03-19 16:17:48+01:00, kent@mysql.com +15 -2623
    Major cleanup of old Visual Studio project files, aligning engines etc

  VC++Files/client/mysql.vcproj@1.2, 2007-03-19 16:17:48+01:00, kent@mysql.com +18 -178
    Major cleanup of old Visual Studio project files, aligning engines etc

  VC++Files/client/mysql_upgrade.vcproj@1.2, 2007-03-19 16:17:48+01:00, kent@mysql.com +19 -103
    Major cleanup of old Visual Studio project files, aligning engines etc

  VC++Files/client/mysqladmin.vcproj@1.2, 2007-03-19 16:17:48+01:00, kent@mysql.com +19 -103
    Major cleanup of old Visual Studio project files, aligning engines etc

  VC++Files/client/mysqlclient.vcproj@1.3, 2007-03-19 16:17:48+01:00, kent@mysql.com +24 -2832
    Major cleanup of old Visual Studio project files, aligning engines etc

  VC++Files/client/mysqldump.vcproj@1.3, 2007-03-19 16:17:48+01:00, kent@mysql.com +23 -131
    Major cleanup of old Visual Studio project files, aligning engines etc

  VC++Files/client/mysqlimport.vcproj@1.2, 2007-03-19 16:17:48+01:00, kent@mysql.com +19 -103
    Major cleanup of old Visual Studio project files, aligning engines etc

  VC++Files/client/mysqlshow.vcproj@1.2, 2007-03-19 16:17:48+01:00, kent@mysql.com +19 -103
    Major cleanup of old Visual Studio project files, aligning engines etc

  VC++Files/client/mysqltest.vcproj@1.2, 2007-03-19 16:17:48+01:00, kent@mysql.com +19 -128
    Major cleanup of old Visual Studio project files, aligning engines etc

  VC++Files/comp_err/comp_err.vcproj@1.2, 2007-03-19 16:17:48+01:00, kent@mysql.com +73 -18
    Major cleanup of old Visual Studio project files, aligning engines etc

  VC++Files/dbug/dbug.vcproj@1.2, 2007-03-19 16:17:48+01:00, kent@mysql.com +32 -104
    Major cleanup of old Visual Studio project files, aligning engines etc

  VC++Files/heap/heap.vcproj@1.2, 2007-03-19 16:17:48+01:00, kent@mysql.com +50 -818
    Major cleanup of old Visual Studio project files, aligning engines etc

  VC++Files/innobase/innobase.vcproj@1.3, 2007-03-19 16:17:48+01:00, kent@mysql.com +14 -2614
    Major cleanup of old Visual Studio project files, aligning engines etc

  VC++Files/libmysql/libmysql.vcproj@1.3, 2007-03-19 16:17:48+01:00, kent@mysql.com +19 -1817
    Major cleanup of old Visual Studio project files, aligning engines etc

  VC++Files/libmysqld/examples/test_libmysqld.vcproj@1.2, 2007-03-19 16:17:48+01:00, kent@mysql.com +73 -41
    Major cleanup of old Visual Studio project files, aligning engines etc

  VC++Files/libmysqld/libmysqld.vcproj@1.7, 2007-03-19 16:17:48+01:00, kent@mysql.com +459 -4013
    Major cleanup of old Visual Studio project files, aligning engines etc

  VC++Files/libmysqltest/myTest.vcproj@1.2, 2007-03-19 16:17:48+01:00, kent@mysql.com +35 -51
    Major cleanup of old Visual Studio project files, aligning engines etc

  VC++Files/my_print_defaults/my_print_defaults.vcproj@1.2, 2007-03-19 16:17:48+01:00, kent@mysql.com +31 -116
    Major cleanup of old Visual Studio project files, aligning engines etc

  VC++Files/myisam/myisam.vcproj@1.2, 2007-03-19 16:17:48+01:00, kent@mysql.com +41 -1737
    Major cleanup of old Visual Studio project files, aligning engines etc

  VC++Files/myisam_ftdump/myisam_ftdump.vcproj@1.2, 2007-03-19 16:17:48+01:00, kent@mysql.com +20 -37
    Major cleanup of old Visual Studio project files, aligning engines etc

  VC++Files/myisamchk/myisamchk.vcproj@1.2, 2007-03-19 16:17:48+01:00, kent@mysql.com +30 -116
    Major cleanup of old Visual Studio project files, aligning engines etc

  VC++Files/myisamlog/myisamlog.vcproj@1.2, 2007-03-19 16:17:48+01:00, kent@mysql.com +20 -106
    Major cleanup of old Visual Studio project files, aligning engines etc

  VC++Files/myisammrg/myisammrg.vcproj@1.2, 2007-03-19 16:17:48+01:00, kent@mysql.com +54 -726
    Major cleanup of old Visual Studio project files, aligning engines etc

  VC++Files/myisampack/myisampack.vcproj@1.2, 2007-03-19 16:17:48+01:00, kent@mysql.com +19 -105
    Major cleanup of old Visual Studio project files, aligning engines etc

  VC++Files/mysql.sln@1.16, 2007-03-19 16:17:48+01:00, kent@mysql.com +1233 -1148
    Major cleanup of old Visual Studio project files, aligning engines etc

  VC++Files/mysqlbinlog/mysqlbinlog.vcproj@1.3, 2007-03-19 16:17:48+01:00, kent@mysql.com +15 -123
    Major cleanup of old Visual Studio project files, aligning engines etc

  VC++Files/mysqlcheck/mysqlcheck.vcproj@1.2, 2007-03-19 16:17:48+01:00, kent@mysql.com +22 -106
    Major cleanup of old Visual Studio project files, aligning engines etc

  VC++Files/mysqldemb/mysqldemb.vcproj@1.4, 2007-03-19 16:17:48+01:00, kent@mysql.com +358 -2579
    Major cleanup of old Visual Studio project files, aligning engines etc

  VC++Files/mysqlserver/mysqlserver.vcproj@1.2, 2007-03-19 16:17:48+01:00, kent@mysql.com +20 -18
    Major cleanup of old Visual Studio project files, aligning engines etc

  VC++Files/mysys/mysys.vcproj@1.11, 2007-03-19 16:17:48+01:00, kent@mysql.com +55 -4385
    Major cleanup of old Visual Studio project files, aligning engines etc

  VC++Files/perror/perror.vcproj@1.2, 2007-03-19 16:17:48+01:00, kent@mysql.com +21 -110
    Major cleanup of old Visual Studio project files, aligning engines etc

  VC++Files/regex/regex.vcproj@1.2, 2007-03-19 16:17:48+01:00, kent@mysql.com +14 -126
    Major cleanup of old Visual Studio project files, aligning engines etc

  VC++Files/replace/replace.vcproj@1.2, 2007-03-19 16:17:48+01:00, kent@mysql.com +20 -103
    Major cleanup of old Visual Studio project files, aligning engines etc

  VC++Files/sql/gen_lex_hash.vcproj@1.2, 2007-03-19 16:17:48+01:00, kent@mysql.com +27 -22
    Major cleanup of old Visual Studio project files, aligning engines etc

  VC++Files/sql/mysqld.vcproj@1.10.1.1, 2007-03-19 16:17:48+01:00, kent@mysql.com +222 -8039
    Major cleanup of old Visual Studio project files, aligning engines etc

  VC++Files/strings/strings.vcproj@1.3, 2007-03-19 16:17:48+01:00, kent@mysql.com +14 -782
    Major cleanup of old Visual Studio project files, aligning engines etc

  VC++Files/test1/test1.vcproj@1.2, 2007-03-19 16:17:48+01:00, kent@mysql.com +20 -37
    Major cleanup of old Visual Studio project files, aligning engines etc

  VC++Files/tests/mysql_client_test.vcproj@1.2, 2007-03-19 16:17:48+01:00, kent@mysql.com +21 -39
    Major cleanup of old Visual Studio project files, aligning engines etc

  VC++Files/thr_test/thr_test.vcproj@1.2, 2007-03-19 16:17:48+01:00, kent@mysql.com +18 -36
    Major cleanup of old Visual Studio project files, aligning engines etc

  VC++Files/vio/vio.vcproj@1.2, 2007-03-19 16:17:48+01:00, kent@mysql.com +14 -78
    Major cleanup of old Visual Studio project files, aligning engines etc

  VC++Files/zlib/zlib.vcproj@1.2, 2007-03-19 16:17:48+01:00, kent@mysql.com +16 -315
    Major cleanup of old Visual Studio project files, aligning engines etc

  extra/yassl/taocrypt/taocrypt.vcproj@1.5, 2007-03-19 16:17:48+01:00, kent@mysql.com +16 -374
    Major cleanup of old Visual Studio project files, aligning engines etc

  extra/yassl/yassl.vcproj@1.5, 2007-03-19 16:17:48+01:00, kent@mysql.com +16 -230
    Major cleanup of old Visual Studio project files, aligning engines etc

  ndb/src/cw/cpcc-win32/C++/CPC_GUI.vcproj@1.2, 2007-03-19 16:17:48+01:00, kent@mysql.com +19 -19
    Major cleanup of old Visual Studio project files, aligning engines etc

  scripts/make_win_bin_dist@1.9, 2007-03-19 16:17:48+01:00, kent@mysql.com +0 -1
    Major cleanup of old Visual Studio project files, aligning engines etc

  server-tools/instance-manager/mysqlmanager.vcproj@1.8, 2007-03-19 16:17:48+01:00, kent@mysql.com +17 -8
    Major cleanup of old Visual Studio project files, aligning engines etc

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.2392.107.1, 2007-03-19 15:24:07+01:00, joerg@trift2. +1 -0
  netware/Makefile.am  :  "libmysql.imp" must survive a "make clean" for the NetWare builds.

  netware/Makefile.am@1.20.1.2, 2007-03-19 15:24:04+01:00, joerg@trift2. +2 -1
    "libmysql.imp" must survive a "make clean" for the NetWare builds.

ChangeSet@1.2392.104.4, 2007-03-18 10:47:15+01:00, kent@mysql.com +1 -0
  make_win_bin_dist:
    - Support both "release" and "relwithdebinfo" targets
    - Copy ".pdb" and ".pdb" files for the server and instance manager
    - Removed the examples directory, unsupported
    - Handle both old and new builds in the same script, "-debug" and "-nt"
      extensions, directory "data" and "share" in different location

  scripts/make_win_bin_dist@1.7, 2007-03-18 10:42:35+01:00, kent@mysql.com +54 -34
    - Support both "release" and "relwithdebinfo" targets
    - Copy ".pdb" and ".pdb" files for the server and instance manager
    - Removed the examples directory, unsupported
    - Handle both old and new builds in the same script, "-debug" and "-nt"
      extensions, directory "data" and "share" in different location

ChangeSet@1.2392.104.3, 2007-03-17 19:45:01+01:00, joerg@trift2. +1 -0
  Fix a failure in test "func_in" on some 64-bit big-endian hosts in first 5.0.38 builds.

  sql/item_cmpfunc.cc@1.240, 2007-03-17 19:44:58+01:00, joerg@trift2. +2 -2
    Ensure both operands of a comparison are cast to "ulonglong", not just one only.
    Without this, some 64-bit big-endian hosts failed test "func_in" when 5.0.38 builds were started.
    
    Patch provided by Timothy.

ChangeSet@1.2392.104.2, 2007-03-16 20:56:16+01:00, joerg@trift2. +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
  
  Changeset coded today by Magnus Svensson, just the application to 5.0.38 is by Joerg Bruehe.

  BitKeeper/deleted/.del-init_db.sql~e2b8d0c8390e8023@1.8.1.1, 2007-03-16 20:47:21+01:00, joerg@trift2. +0 -0
    Delete: netware/init_db.sql

  BitKeeper/deleted/.del-test_db.sql@1.4.1.1, 2007-03-16 20:47:45+01:00, joerg@trift2. +0 -0
    Delete: netware/test_db.sql

  BitKeeper/etc/ignore@1.243.1.1, 2007-03-16 20:56:13+01:00, joerg@trift2. +2 -0
    Added netware/init_db.sql netware/test_db.sql to the ignore list

  mysql-test/install_test_db.sh@1.38.1.1, 2007-03-16 20:56:13+01:00, joerg@trift2. +8 -12
    Use mysql_install_db from install_test_db(which is used by mysql-test-run-shell)
    to install the system tables

  mysql-test/mysql-test-run.pl@1.208.1.1, 2007-03-16 20:56:13+01:00, joerg@trift2. +11 -3
    Look for the mysql_system_tables*.sql also in share/mysql

  netware/Makefile.am@1.20.1.1, 2007-03-16 20:56:13+01:00, joerg@trift2. +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.122.1.1, 2007-03-16 20:56:13+01:00, joerg@trift2. +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.437.1.1, 2007-03-16 20:56:13+01:00, joerg@trift2. +3 -2
    Update comment remindging to update the MySQL system table definitions
    when adding a new SQL_MODE

  sql/sql_acl.h@1.52.1.1, 2007-03-16 20:56:13+01:00, joerg@trift2. +1 -1
    Update comment reminding to update the MySQL System tables
    when changing the ACL defines

ChangeSet@1.2392.104.1, 2007-03-16 19:56:16+01:00, joerg@trift2. +2 -0
  Fix bug#27212, test case "loaddata": Take the file to read from the binary package.

  mysql-test/r/loaddata.result@1.26, 2007-03-16 19:56:11+01:00, joerg@trift2. +3 -3
    Fix bug#27212:  Do not try to read a file which is not contained in a binary distribution,
    because it will be missing when the tests are run during release build or by a customer.

  mysql-test/t/loaddata.test@1.20, 2007-03-16 19:56:11+01:00, joerg@trift2. +2 -2
    Fix bug#27212:  Do not try to read a file which is not contained in a binary distribution,
    because it will be missing when the tests are run during release build or by a customer.

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.7.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.211.1.13, 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.103.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.10.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.101.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.100.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.10.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.99.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.90.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.90.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.416.1.17, 2007-03-15 19:01:47+01:00, jbruehe@mysql.com +2 -2
    Raise version number after cloning 5.0.38

ChangeSet@1.2392.95.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.314.1.11, 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.211.1.11, 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.93.1, 2007-03-15 11:51:35+03:00, dlenev@mockturtle.local +3 -0
  Fix for bug #25966 "2MB per second endless memory consumption after LOCK
  TABLE ... WRITE".
  
  Memory and CPU hogging occured when connection which had to wait for table
  lock was serviced by thread which previously serviced connection that was
  killed (note that connections can reuse threads if thread cache is enabled).
  One possible scenario which exposed this problem was when thread which
  provided binlog dump to replication slave was implicitly/automatically
  killed when the same slave reconnected and started pulling data through
  different thread/connection.
  The problem also occured when one killed particular query in connection
  (using KILL QUERY) and later this connection had to wait for some table
  lock.
  
  This problem was caused by the fact that thread-specific mysys_var::abort
  variable, which indicates that waiting operations on mysys layer should
  be aborted (this includes waiting for table locks), was set by kill
  operation but was never reset back. So this value was "inherited" by the
  following statements or even other connections (which reused the same
  physical thread). Such discrepancy between this variable and THD::killed
  flag broke logic on SQL-layer and caused CPU and memory hogging.
  
  This patch tries to fix this problem by properly resetting this member.
  
  There is no test-case associated with this patch since it is hard to test
  for memory/CPU hogging conditions in our test-suite.

  sql/mysqld.cc@1.597, 2007-03-15 11:51:32+03:00, dlenev@mockturtle.local +6 -0
    We should not forget to reset THD::mysys_var::abort after kill operation
    if we are going to use thread to which this operation was applied for
    handling of other connections.

  sql/sp_head.cc@1.236.1.1, 2007-03-15 11:51:33+03:00, dlenev@mockturtle.local +1 -0
    We should not forget to reset THD::mysys_var::abort after kill operation
    if we are going to use thread to which this operation was applied for
    handling of further statements.

  sql/sql_parse.cc@1.593.12.2, 2007-03-15 11:51:33+03:00, dlenev@mockturtle.local +3 -0
    We should not forget to reset THD::mysys_var::abort after kill operation
    if we are going to use thread to which this operation was applied for
    handling of further statements.

ChangeSet@1.1616.2992.3, 2007-03-15 11:30:17+03:00, dlenev@mockturtle.local +1 -0
  Fix for bug #25966 "2MB per second endless memory consumption after LOCK
  TABLE ... WRITE".
  
  CPU hogging occured when connection which had to wait for table lock was
  serviced by thread which previously serviced connection that was killed
  (note that connections can reuse threads if thread cache is enabled).
  One possible scenario which exposed this problem was when thread which
  provided binlog dump to replication slave was implicitly/automatically
  killed when the same slave reconnected and started pulling data through
  different thread/connection.
  In 5.* versions memory hogging was added to CPU hogging. Moreover in
  those versions the problem also occured when one killed particular query
  in connection (using KILL QUERY) and later this connection had to wait for
  some table lock.
  
  This problem was caused by the fact that thread-specific mysys_var::abort
  variable, which indicates that waiting operations on mysys layer should
  be aborted (this includes waiting for table locks), was set by kill
  operation but was never reset back. So this value was "inherited" by the
  following statements or even other connections (which reused the same
  physical thread). Such discrepancy between this variable and THD::killed
  flag broke logic on SQL-layer and caused CPU and memory hogging.
  
  This patch tries to fix this problem by properly resetting this member.
  
  There is no test-case associated with this patch since it is hard to test
  for memory/CPU hogging conditions in our test-suite.

  sql/mysqld.cc@1.356.98.40, 2007-03-15 11:30:16+03:00, dlenev@mockturtle.local +6 -0
    We should not forget to reset THD::mysys_var::abort after kill operation
    if we are going to use thread to which this operation was applied for
    handling of other connections.

ChangeSet@1.2392.92.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.91.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.1346.1.867, 2007-03-14 18:28:16+01:00, kent@mysql.com +1 -0
  EXCEPTIONS-CLIENT:
    Updated to version 0.6 of the text

  EXCEPTIONS-CLIENT@1.2, 2007-03-14 18:28:10+01:00, kent@mysql.com +4 -2
    Updated to version 0.6 of the text

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.1346.1.866, 2007-03-14 14:27:46+01:00, kent@mysql.com +1 -0
  configure.in:
    Added test for sched_yield() possibly in -lposix4 on Solaris

  configure.in@1.191.1.153, 2007-03-14 14:27:40+01:00, kent@mysql.com +3 -0
    Added test for sched_yield() possibly in -lposix4 on Solaris

ChangeSet@1.2392.64.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.88.4, 2007-03-14 02:30:05+04:00, svoj@mysql.com +1 -0
  Removed tabs.

  myisam/mi_open.c@1.105, 2007-03-14 02:30:03+04:00, svoj@mysql.com +1 -1
    Removed tabs.

ChangeSet@1.1616.2992.2, 2007-03-13 18:02:06+04:00, svoj@mysql.com +5 -0
  BUG#26881 - Large MERGE tables report incorrect specification when no
              differences in tables
  Certain merge tables were wrongly reported as having incorrect definition:
  - Some fields that are 1 byte long (e.g. TINYINT, CHAR(1)), might
    be internally casted (in certain cases) to a different type on a
    storage engine layer. (affects 4.1 and up)
  - If tables in a merge (and a MERGE table itself) had short VARCHAR column (less
    than 4 bytes) and at least one (but not all) tables were ALTER'ed (even to an
    identical table: ALTER TABLE xxx ENGINE=yyy), table definitions went ouf of
    sync. (affects 4.1 only)
  
  This is fixed by relaxing a check for underlying conformance and setting
  field type to FIELD_TYPE_STRING in case varchar is shorter than 4
  when a table is created.

  myisam/mi_create.c@1.37.1.14, 2007-03-13 18:02:04+04:00, svoj@mysql.com +4 -0
    Added a comment.

  mysql-test/r/merge.result@1.32.1.14, 2007-03-13 18:02:04+04:00, svoj@mysql.com +13 -0
    A test case for bug#26881.

  mysql-test/t/merge.test@1.28.1.15, 2007-03-13 18:02:04+04:00, svoj@mysql.com +17 -0
    A test case for bug#26881.

  sql/ha_myisam.cc@1.115.1.50, 2007-03-13 18:02:04+04:00, svoj@mysql.com +36 -1
    Relaxed some checks performed by check_definition():
    As comparing of fulltext keys (and key segments) is not yet implemented,
    only return an error in case one of keys is fulltext and other is not.
    Otherwise, if both keys are fulltext, accept them as is.
    
    As comparing of spatial keys (and key segments) is not yet implemented,
    only return an error in case one of keys is spatial and other is not.
    Otherwise, if both keys are spatial, accept them as is.
    
    A workaround to handle situation when field is casted from FIELD_SKIP_ZERO
    to FIELD_NORMAL. This could happen only in case field length is 1 and row
    format is fixed.

  sql/sql_parse.cc@1.271.1.225, 2007-03-13 18:02:05+04:00, svoj@mysql.com +7 -1
    When a table that has varchar field shorter than 4 is created, field type is
    set to FIELD_TYPE_VAR_STRING. Later, when a table is modified using alter
    table, field type is changed to FIELD_TYPE_STRING (see Field_string::type).
    That means HA_OPTION_PACK_RECORD flag might be lost and thus null_bit might
    be shifted by alter table, in other words alter table doesn't create 100%
    equal table definition.
    
    This is usually not a problem, since when a table is created/altered,
    definition on a storage engine layer is based on one that is passed from
    sql layer. But it is a problem for merge engine - null_bit is shifted when
    a table (merge or underlying) is altered.
    
    Set field type to FIELD_TYPE_STRING in case FIELD_TYPE_VAR_STRING is shorter
    than 4 when a table is created as it is done in Field::type.

ChangeSet@1.2392.62.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.1616.2877.62, 2007-03-12 21:27:07+01:00, kent@mysql.com +1 -0
  configure.in:
    Restored accidently removed line to check for zlib

  configure.in@1.201.64.26, 2007-03-12 21:26:03+01:00, kent@mysql.com +2 -0
    Restored accidently removed line to check for zlib

ChangeSet@1.2392.87.2, 2007-03-12 14:52:37+01:00, kent@mysql.com +2 -0
  Makefile.am, CMakeLists.txt:
    Removed references to my_winsem.c

  mysys/CMakeLists.txt@1.4, 2007-03-12 14:52:30+01:00, kent@mysql.com +1 -1
    Removed references to my_winsem.c

  mysys/Makefile.am@1.76, 2007-03-12 14:52:30+01:00, kent@mysql.com +1 -1
    Removed references to my_winsem.c

ChangeSet@1.1616.2877.61, 2007-03-12 13:18:48+01:00, kent@mysql.com +2 -0
  mysys_ia64.dsp, mysys.vcproj:
    Removed references to unused files

  VC++Files/mysys/mysys.vcproj@1.1.1.2, 2007-03-12 13:18:03+01:00, kent@mysql.com +0 -43
    Removed unused files

  VC++Files/mysys/mysys_ia64.dsp@1.2.1.2, 2007-03-12 13:18:03+01:00, kent@mysql.com +0 -4
    Removed unused files

ChangeSet@1.2341.98.1, 2007-03-12 13:15:43+01:00, df@pippilotta.erinye.com +1 -0
  add missing test cases to windows binary distribution

  scripts/make_win_bin_dist@1.5.1.1, 2007-03-12 13:15:41+01:00, df@pippilotta.erinye.com +1 -0
    add missing test cases to windows binary distribution

ChangeSet@1.1346.1.865, 2007-03-12 13:12:42+01:00, kent@mysql.com +7 -0
  Makefile.am, configure.in, mysys.dsp:
    Removed unused files
  .del-my_winsem.c:
    Delete: mysys/my_winsem.c
  .del-my_semaphore.c:
    Delete: mysys/my_semaphore.c
  .del-my_semaphore.h:
    Delete: include/my_semaphore.h

  BitKeeper/deleted/.del-my_semaphore.c@1.3.1.1, 2007-03-12 13:10:40+01:00, kent@mysql.com +0 -0
    Delete: mysys/my_semaphore.c

  BitKeeper/deleted/.del-my_semaphore.h@1.8, 2007-03-12 13:10:40+01:00, kent@mysql.com +0 -0
    Delete: include/my_semaphore.h

  BitKeeper/deleted/.del-my_winsem.c@1.4, 2007-03-12 13:10:40+01:00, kent@mysql.com +0 -0
    Delete: mysys/my_winsem.c

  VC++Files/mysys/mysys.dsp@1.6.1.8, 2007-03-12 13:12:09+01:00, kent@mysql.com +0 -4
    Removed unused files

  configure.in@1.191.1.152, 2007-03-12 13:12:09+01:00, kent@mysql.com +0 -3
    Removed unused files

  include/Makefile.am@1.29.1.12, 2007-03-12 13:12:09+01:00, kent@mysql.com +1 -1
    Removed unused files

  mysys/Makefile.am@1.29.1.17, 2007-03-12 13:12:09+01:00, kent@mysql.com +1 -1
    Removed unused files

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.83.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.85.1, 2007-03-10 19:55:34+03:00, evgen@moonbone.local +3 -0
  Bug#15757: Wrong SUBSTRING() result when a tmp table was employed.
  
  When the SUBSTRING() function was used over a LONGTEXT field the max_length of
  the SUBSTRING() result was wrongly calculated and set to 0. As the max_length
  parameter is used while tmp field creation it limits the length of the result
  field and leads to printing an empty string instead of the correct result.
  
  Now the Item_func_substr::fix_length_and_dec() function correctly calculates
  the max_length parameter.

  mysql-test/r/func_str.result@1.126.3.1, 2007-03-10 19:55:10+03:00, evgen@moonbone.local +11 -0
    Added a test case for the bug#15757: Wrong SUBSTRING() result when a tmp table was employed.

  mysql-test/t/func_str.test@1.99.2.1, 2007-03-10 19:55:04+03:00, evgen@moonbone.local +11 -0
    Added a test case for the bug#15757: Wrong SUBSTRING() result when a tmp table was employed.

  sql/item_strfunc.cc@1.295.2.1, 2007-03-10 19:55:10+03:00, evgen@moonbone.local +3 -4
    Bug#15757: Wrong SUBSTRING() result when a tmp table was employed.
    Now the Item_func_substr::fix_length_and_dec() function correctly calculates
    the max_length parameter.

ChangeSet@1.2392.84.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.593.1.17, 2007-03-10 17:44:23+04:00, holyfoot@mysql.com +1 -1
    default condition fixed

ChangeSet@1.2392.83.1, 2007-03-10 02:47:47-08:00, igor@olga.mysql.com +3 -0
  Fixed bug #26830: a crash for the query with a subselect containing ROLLUP.
  Crash happened because the function get_best_group_min_max detected
  joins with ROLLUP incorrectly.

  mysql-test/r/olap.result@1.36, 2007-03-10 02:47:44-08:00, igor@olga.mysql.com +9 -0
    Added a test case for bug #26830.

  mysql-test/t/olap.test@1.27, 2007-03-10 02:47:44-08:00, igor@olga.mysql.com +15 -0
    Added a test case for bug #26830.

  sql/opt_range.cc@1.241, 2007-03-10 02:47:45-08:00, igor@olga.mysql.com +1 -1
    Fixed bug #26830: a crash for the query with a subselect containing ROLLUP.
    Crash happened because the function get_best_group_min_max detected
    joins with ROLLUP incorrectly.

ChangeSet@1.2392.76.4, 2007-03-10 11:46:20+07:00, tomas@poseidon.mysql.com +1 -0
  disabling _new_ unstable test case

  mysql-test/t/disabled.def@1.45, 2007-03-10 11:46:13+07:00, tomas@poseidon.mysql.com +1 -0
    disabling _new_ unstable test case

ChangeSet@1.2392.73.5, 2007-03-09 23:37:33+01:00, knielsen@ymer.(none) +2 -0
  BUG#27018: Partial blob write inside blob clobbers data after the write.
  
  When doing partial blob update with NdbBlob::writeData(), zero-padding
  after the write was wrongly done, causing part of the old blob value
  to be overwritten with zeros (or spaces for text field).
  
  Fixed by only padding when needed (when writing at end of the blob).

  ndb/src/ndbapi/NdbBlob.cpp@1.33, 2007-03-09 23:37:29+01:00, knielsen@ymer.(none) +3 -1
    Do not pad rest of blob part after the write, unless it is a write at the
    end of the blob.

  ndb/test/ndbapi/testBlobs.cpp@1.32, 2007-03-09 23:37:29+01:00, knielsen@ymer.(none) +53 -1
    Add test case.

ChangeSet@1.2392.81.1, 2007-03-10 00:29:02+03:00, evgen@moonbone.local +12 -0
  Bug#22331: Wrong WHERE in EXPLAIN EXTENDED when all expressions were optimized
  away.
  
  Additional fix for bug#22331. Now Item_field prints its value in the case of
  the const field.

  mysql-test/r/explain.result@1.20, 2007-03-10 00:18:45+03:00, evgen@moonbone.local +3 -3
    Corrected test case after fix for bug#22331.

  mysql-test/r/func_default.result@1.6, 2007-03-10 00:18:44+03:00, evgen@moonbone.local +1 -1
    Corrected test case after fix for bug#22331.

  mysql-test/r/func_regexp.result@1.11, 2007-03-10 00:18:43+03:00, evgen@moonbone.local +1 -1
    Corrected test case after fix for bug#22331.

  mysql-test/r/func_str.result@1.126.2.1, 2007-03-10 00:18:43+03:00, evgen@moonbone.local +3 -3
    Corrected test case after fix for bug#22331.

  mysql-test/r/func_test.result@1.35, 2007-03-10 00:18:42+03:00, evgen@moonbone.local +1 -1
    Corrected test case after fix for bug#22331.

  mysql-test/r/having.result@1.27, 2007-03-10 00:18:42+03:00, evgen@moonbone.local +1 -1
    Corrected test case after fix for bug#22331.

  mysql-test/r/subselect.result@1.172.1.3, 2007-03-10 00:18:41+03:00, evgen@moonbone.local +11 -11
    Corrected test case after fix for bug#22331.

  mysql-test/r/union.result@1.87.1.1, 2007-03-10 00:18:40+03:00, evgen@moonbone.local +1 -1
    Corrected test case after fix for bug#22331.

  mysql-test/r/varbinary.result@1.18, 2007-03-10 00:18:36+03:00, evgen@moonbone.local +1 -1
    Corrected test case after fix for bug#22331.

  sql/item.cc@1.251.3.1, 2007-03-10 00:19:26+03:00, evgen@moonbone.local +19 -2
    Bug#22331: Wrong WHERE in EXPLAIN EXTENDED when all expressions were optimized
    away.
    Added the print() member function to the Item_field class.

  sql/item.h@1.221, 2007-03-10 00:19:10+03:00, evgen@moonbone.local +1 -0
    Bug#22331: Wrong WHERE in EXPLAIN EXTENDED when all expressions were optimized
    away.
    Added the print() member function to the Item_field class.

  sql/sql_union.cc@1.140, 2007-03-10 00:18:58+03:00, evgen@moonbone.local +6 -0
    Bug#22331: Wrong WHERE in EXPLAIN EXTENDED when all expressions were optimized
    away.
    Cleanup of the SELECT_LEX::order_list list.

ChangeSet@1.2392.80.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.256.10.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.1616.2991.3, 2007-03-09 16:19:42+01:00, istruewing@chilla.local +1 -0
  Bug#25673 - spatial index corruption, error 126 incorrect key file for table
  Fixed a compiler warning, deteced by pushbuild only.

  myisam/rt_index.c@1.17.2.3, 2007-03-09 16:19:40+01:00, istruewing@chilla.local +1 -1
    Bug#25673 - spatial index corruption, error 126 incorrect key file for table
    Fixed a compiler warning, deteced by pushbuild only.

ChangeSet@1.2377.51.3, 2007-03-09 20:34:00+07:00, tomas@poseidon.mysql.com +2 -0
  added error code for failing send signal and timeout waiting for node failure
  added error code for failing send signal and timeout waiting for node failure

  ndb/src/ndbapi/NdbDictionaryImpl.cpp@1.95.1.2, 2007-03-09 20:33:54+07:00, tomas@poseidon.mysql.com +4 -0
    added error code for failing send signal and timeout waiting for node failure

  ndb/src/ndbapi/ndberror.c@1.56, 2007-03-09 20:33:54+07:00, tomas@poseidon.mysql.com +2 -0
    added error code for failing send signal and timeout waiting for node failure

ChangeSet@1.2341.97.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.9.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.75.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.78.1, 2007-03-09 12:47:12+02:00, gkodinov@magare.gmz +3 -0
  Bug #26281:
   Fixed boundry checks in the INSERT() function:
   were one off.

  mysql-test/r/func_str.result@1.126.1.2, 2007-03-09 12:47:11+02:00, gkodinov@magare.gmz +12 -0
    Bug #26281: test case

  mysql-test/t/func_str.test@1.99.1.2, 2007-03-09 12:47:11+02:00, gkodinov@magare.gmz +8 -0
    Bug #26281: test case

  sql/item_strfunc.cc@1.295.1.1, 2007-03-09 12:47:11+02:00, gkodinov@magare.gmz +5 -5
    Bug #26281: fixed boundry checks

ChangeSet@1.2392.77.1, 2007-03-09 01:45:32-08:00, igor@olga.mysql.com +3 -0
  Fixed bug #26661: crash when order by clause in a union
  construct references invalid name.
  Derived tables currently cannot use outer references.
  Thus there is no outer context for them.
  The 4.1 code takes this fact into account while the 
  Item_field::fix_outer_field code of 5.0 lost the check that blocks
  any attempts to resolve names in outer context for derived tables.

  mysql-test/r/union.result@1.88, 2007-03-09 01:45:30-08:00, igor@olga.mysql.com +11 -0
    Added a test case for bug #26661.

  mysql-test/t/union.test@1.98, 2007-03-09 01:45:30-08:00, igor@olga.mysql.com +13 -0
    Added a test case for bug #26661.

  sql/item.cc@1.251.1.2, 2007-03-09 01:45:30-08:00, igor@olga.mysql.com +6 -1
    Fixed bug #26661.
    Derived tables currently cannot use outer references.
    Thus there is no outer context for them.
    The 4.1 code takes this fact into account while the 
    Item_field::fix_outer_field code of 5.0 lost the check that blocks
    any attempts to resolve names in outer context for derived tables.

ChangeSet@1.2377.51.2, 2007-03-09 16:39:13+07:00, tomas@poseidon.mysql.com +2 -0
  ndb single user basic test

  mysql-test/r/ndb_single_user.result@1.1, 2007-03-09 16:39:03+07:00, tomas@poseidon.mysql.com +46 -0
    ndb single user basic test

  mysql-test/r/ndb_single_user.result@1.0, 2007-03-09 16:39:03+07:00, tomas@poseidon.mysql.com +0 -0
    BitKeeper file /home/tomas/mysql-5.0-telco-gca/mysql-test/r/ndb_single_user.result

  mysql-test/t/ndb_single_user.test@1.1, 2007-03-09 16:39:03+07:00, tomas@poseidon.mysql.com +84 -0
    ndb single user basic test

  mysql-test/t/ndb_single_user.test@1.0, 2007-03-09 16:39:03+07:00, tomas@poseidon.mysql.com +0 -0
    BitKeeper file /home/tomas/mysql-5.0-telco-gca/mysql-test/t/ndb_single_user.test

ChangeSet@1.2392.1.75, 2007-03-09 13:37:06+04:00, holyfoot@mysql.com +1 -0
  aftermerge fix

  mysql-test/r/view.result@1.197, 2007-03-09 13:37:05+04:00, holyfoot@mysql.com +37 -0
    merging

ChangeSet@1.2392.55.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.2377.51.1, 2007-03-09 15:37:10+07:00, tomas@poseidon.mysql.com +3 -0
  
  Bug #25275 SINGLE USER MODE prevents ALTER on non-ndb tables for other mysqld nodes
  - correction of part 1
      add ndb_waiter option to wait for single user mode

  ndb/src/kernel/blocks/dbdict/Dbdict.cpp@1.71.1.3, 2007-03-09 15:37:02+07:00, tomas@poseidon.mysql.com +21 -15
    Bug #25275 SINGLE USER MODE prevents ALTER on non-ndb tables for other mysqld nodes
    - correction of part 1

  ndb/src/kernel/blocks/dbdict/Dbdict.hpp@1.24.1.2, 2007-03-09 15:37:03+07:00, tomas@poseidon.mysql.com +2 -0
    Bug #25275 SINGLE USER MODE prevents ALTER on non-ndb tables for other mysqld nodes
    - correction of part 1

  ndb/tools/waiter.cpp@1.27, 2007-03-09 15:37:03+07:00, tomas@poseidon.mysql.com +11 -1
    add ndb_waiter option to wait for single user mode

ChangeSet@1.2392.48.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.48.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.360.11.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.1616.2991.2, 2007-03-08 19:22:43+01:00, istruewing@chilla.local +1 -0
  Bug#25673 - spatial index corruption, error 126 incorrect key file for table
  After backport fix.
  Added forgotten DBUG_RETURNs, which was detected in 5.1 only.

  myisam/rt_index.c@1.17.2.2, 2007-03-08 19:22:41+01:00, istruewing@chilla.local +3 -3
    Bug#25673 - spatial index corruption, error 126 incorrect key file for table
    After backport fix.
    Added forgotten DBUG_RETURNs, which was detected in 5.1 only.

ChangeSet@1.2392.55.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.54.11, 2007-03-08 19:38:21+03:00, evgen@moonbone.local +1 -0
  sql_select.cc:
    Postfix for bug#22331.

  sql/sql_select.cc@1.495.1.5, 2007-03-08 19:37:19+03:00, evgen@moonbone.local +2 -1
    Postfix for bug#22331.

ChangeSet@1.2392.74.2, 2007-03-08 12:08:59+01:00, istruewing@chilla.local +1 -0
  Bug#25673 - spatial index corruption, error 126 incorrect key file for table
  After merge fix

  mysql-test/r/gis-rtree.result@1.25, 2007-03-08 12:08:56+01:00, istruewing@chilla.local +1 -0
    Bug#25673 - spatial index corruption, error 126 incorrect key file for table
    After merge fix

ChangeSet@1.2392.48.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.145.1.1, 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.1616.2991.1, 2007-03-08 09:54:37+01:00, istruewing@chilla.local +5 -0
  Bug#25673 - spatial index corruption, error 126
            incorrect key file for table
  
  In certain cases it could happen that deleting a row could
  corrupt an RTREE index.
  
  According to Guttman's algorithm, page underflow is handled
  by storing the page in a list for later re-insertion. The
  keys from the stored pages have to be inserted into the
  remaining pages of the same level of the tree. Hence the
  level number is stored in the re-insertion list together
  with the page.
  
  In the MySQL RTree implementation the level counts from zero
  at the root page, increasing numbers for levels down the tree.
  
  If during re-insertion of the keys the tree height grows, all
  level numbers become invalid. The remaining keys will be
  inserted at the wrong level.
  
  The fix is to increment the level numbers stored in the
  reinsert list after a split of the root block during reinsertion.

  myisam/rt_index.c@1.17.2.1, 2007-03-08 09:54:35+01:00, istruewing@chilla.local +75 -25
    Bug#25673 - spatial index corruption, error 126
                incorrect key file for table
    Added a loop in rtree_delete() to increment the level numbers
    stored in the reinsert list after a split of the root block
    during reinsertion.
    Added comments and DBUG statements.

  myisam/rt_key.c@1.8.1.1, 2007-03-08 09:54:35+01:00, istruewing@chilla.local +12 -5
    Bug#25673 - spatial index corruption, error 126
                incorrect key file for table
    Added DBUG statements.

  myisam/rt_split.c@1.11.2.3, 2007-03-08 09:54:35+01:00, istruewing@chilla.local +5 -2
    Bug#25673 - spatial index corruption, error 126
                incorrect key file for table
    Added DBUG statements.

  mysql-test/r/gis-rtree.result@1.8.1.7, 2007-03-08 09:54:35+01:00, istruewing@chilla.local +552 -0
    Bug#25673 - spatial index corruption, error 126
                incorrect key file for table
    Added the test result.

  mysql-test/t/gis-rtree.test@1.9.1.6, 2007-03-08 09:54:35+01:00, istruewing@chilla.local +556 -0
    Bug#25673 - spatial index corruption, error 126
                incorrect key file for table
    Added a test.

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.2392.62.12, 2007-03-08 08:15:30+01:00, tsmith@quadxeon.mysql.com +1 -0
  comp_err.c:  return ha_checksum from checksum_format_specifier() - more correct, avoid a compiler warning

  extra/comp_err.c@1.28.1.1, 2007-03-08 08:15:05+01:00, tsmith@quadxeon.mysql.com +2 -2
    return ha_checksum from checksum_format_specifier() - more correct, avoid a compiler warning

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.2392.72.1, 2007-03-07 23:49:46+01:00, tsmith@quadxeon.mysql.com +1 -0
  update test results for bdb_gis after merge of fix for b26038

  mysql-test/r/bdb_gis.result@1.4, 2007-03-07 23:49:21+01:00, tsmith@quadxeon.mysql.com +2 -2
    update test results for bdb_gis after merge of fix for b26038

ChangeSet@1.2392.54.10, 2007-03-08 00:27:42+03:00, evgen@moonbone.local +3 -0
  sql_select.cc:
    Postfix for bug#22331 for windows platform.
  explain.test, explain.result:
    Cleanup after bugfix#22331.

  mysql-test/r/explain.result@1.19, 2007-03-08 00:27:00+03:00, evgen@moonbone.local +1 -0
    Cleanup after bugfix#22331.

  mysql-test/t/explain.test@1.12, 2007-03-08 00:26:50+03:00, evgen@moonbone.local +1 -0
    Cleanup after bugfix#22331.

  sql/sql_select.cc@1.495.1.4, 2007-03-08 00:27:05+03:00, evgen@moonbone.local +1 -1
    Postfix for bug#22331 for windows platform.

ChangeSet@1.2392.71.1, 2007-03-07 20:25:57+01:00, df@pippilotta.erinye.com +1 -0
  adjust version string in mysql-5.0-community commit trigger

  BitKeeper/triggers/post-commit@1.42, 2007-03-07 20:25:55+01:00, df@pippilotta.erinye.com +1 -1
    adjust version string in trigger

ChangeSet@1.2392.70.1, 2007-03-07 22:11:57+03:00, evgen@moonbone.local +3 -0
  Bug#25373: Stored functions wasn't compared correctly which leads to a wrong
  result.
  
  For built-in functions like sqrt() function names are hard-coded and can be
  compared by pointer. But this isn't the case for a used-defined stored
  functions - names there are dynamical and should be compared as strings.
  
  Now the Item_func::eq() function employs my_strcasecmp() function to compare
  used-defined stored functions names.

  mysql-test/r/sp.result@1.218.2.1, 2007-03-07 22:05:53+03:00, evgen@moonbone.local +13 -0
    Added a test case for bug#25373: Stored functions wasn't compared correctly which leads to a wrong result.

  mysql-test/t/sp.test@1.208.2.1, 2007-03-07 22:05:47+03:00, evgen@moonbone.local +15 -0
    Added a test case for bug#25373: Stored functions wasn't compared correctly which leads to a wrong result.

  sql/item_func.cc@1.322.1.1, 2007-03-07 22:05:57+03:00, evgen@moonbone.local +7 -2
    Bug#25373: Stored functions wasn't compared correctly which leads to a wrong
    result.
    Now the Item_func::eq() function employs my_strcasecmp() function to compare
    used-defined stored functions names.

ChangeSet@1.2377.29.8, 2007-03-07 21:44:58+03:00, evgen@moonbone.local +8 -0
  Bug#22331: Wrong WHERE in EXPLAIN EXTENDED when all expressions were optimized
  away.
  
  During optimization stage the WHERE conditions can be changed or even
  be removed at all if they know for sure to be true of false. Thus they aren't
  showed in the EXPLAIN EXTENDED which prints conditions after optimization.
  
  Now if all elements of an Item_cond were removed this Item_cond is substituted
  for an Item_int with the int value of the Item_cond.
  If there were conditions that were totally optimized away then values of the
  saved cond_value and having_value will be printed instead.

  mysql-test/r/explain.result@1.18, 2007-03-07 21:31:36+03:00, evgen@moonbone.local +29 -0
    Added a test case for the bug#22331: Wrong WHERE in EXPLAIN EXTENDED when all expressions were optimized away.

  mysql-test/r/func_test.result@1.34, 2007-03-07 21:31:34+03:00, evgen@moonbone.local +1 -1
    Corrected test case result after fix for bug#22331.

  mysql-test/r/subselect.result@1.172.2.1, 2007-03-07 21:31:33+03:00, evgen@moonbone.local +8 -8
    Corrected test case result after fix for bug#22331.

  mysql-test/t/explain.test@1.11, 2007-03-07 21:31:28+03:00, evgen@moonbone.local +14 -0
    Added a test case for the bug#22331: Wrong WHERE in EXPLAIN EXTENDED when all expressions were optimized away.

  sql/sql_lex.cc@1.209.5.1, 2007-03-07 21:43:19+03:00, evgen@moonbone.local +1 -0
    Bug#22331: Wrong WHERE in EXPLAIN EXTENDED when all expressions were optimized
    away.
    The initialization of the cond_value and the having_value variables.

  sql/sql_lex.h@1.233.8.1, 2007-03-07 21:42:15+03:00, evgen@moonbone.local +2 -0
    Bug#22331: Wrong WHERE in EXPLAIN EXTENDED when all expressions were optimized
    away.
    The cond_value and the having_value variables are
    added to the SELECT_LEX class.

  sql/sql_select.cc@1.488.1.3, 2007-03-07 21:40:05+03:00, evgen@moonbone.local +18 -5
    Bug#22331: Wrong WHERE in EXPLAIN EXTENDED when all expressions were optimized
    away.
    Now if all elements of an Item_cond were removed this Item_cond is substituted
    for an Item_int with the int value of the Item_cond.
    If there were conditions that were totally optimized away then values of the
    saved cond_value and having_value will be printed instead.

  sql/sql_select.h@1.116, 2007-03-07 21:44:25+03:00, evgen@moonbone.local +1 -1
    Bug#22331: Wrong WHERE in EXPLAIN EXTENDED when all expressions were optimized
    away.
    Now having_value is also stored in the JOIN class.

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.48.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.2392.62.9, 2007-03-07 10:46:38-05:00, iggy@recycle.(none) +1 -0
  Bug#25222 Win32 HANDLE leak in my_sopen()
  - When attempting to associate a Windows File handle to a C run-time file
  handle there is an upper bound.  Once reached, the newly created handles
  will cause a memory leak since they are not properly associated with a
  handle that can later be cleaned up.

  mysys/my_open.c@1.28, 2007-03-07 10:46:36-05:00, iggy@recycle.(none) +6 -1
    Bug#25222 Win32 HANDLE leak in my_sopen()
    - Check for failure in _open_osfhandle and close allocated HANDLE on failure.

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.68.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.2392.48.18, 2007-03-07 14:03:44+03:00, kostja@bodhi.local +1 -0
  A fix for the windows build (harmless warning).

  sql/sql_lex.cc@1.216, 2007-03-07 14:03:41+03:00, kostja@bodhi.local +1 -1
    A fix for the windows build.

ChangeSet@1.2392.69.1, 2007-03-07 12:24:46+03:00, kostja@bodhi.local +10 -0
  A fix for Bug#26750 "valgrind leak in sp_head" (and post-review
  fixes).
  
  The legend: on a replication slave, in case a trigger creation
  was filtered out because of application of replicate-do-table/
  replicate-ignore-table rule, the parsed definition of a trigger was not 
  cleaned up properly. LEX::sphead member was left around and leaked 
  memory. Until the actual implementation of support of 
  replicate-ignore-table rules for triggers by the patch for Bug 24478 it 
  was never the case that "case SQLCOM_CREATE_TRIGGER"
  was not executed once a trigger was parsed,
  so the deletion of lex->sphead there worked and the memory did not leak.
  
  The fix: 
  
  The real cause of the bug is that there is no 1 or 2 places where
  we can clean up the main LEX after parse. And the reason we 
  can not have just one or two places where we clean up the LEX is
  asymmetric behaviour of MYSQLparse in case of success or error. 
  
  One of the root causes of this behaviour is the code in Item::Item()
  constructor. There, a newly created item adds itself to THD::free_list
  - a single-linked list of Items used in a statement. Yuck. This code
  is unaware that we may have more than one statement active at a time,
  and always assumes that the free_list of the current statement is
  located in THD::free_list. One day we need to be able to explicitly
  allocate an item in a given Query_arena.
  Thus, when parsing a definition of a stored procedure, like
  CREATE PROCEDURE p1() BEGIN SELECT a FROM t1; SELECT b FROM t1; END;
  we actually need to reset THD::mem_root, THD::free_list and THD::lex
  to parse the nested procedure statement (SELECT *).
  The actual reset and restore is implemented in semantic actions
  attached to sp_proc_stmt grammar rule.
  The problem is that in case of a parsing error inside a nested statement
  Bison generated parser would abort immediately, without executing the
  restore part of the semantic action. This would leave THD in an 
  in-the-middle-of-parsing state.
  This is why we couldn't have had a single place where we clean up the LEX
  after MYSQLparse - in case of an error we needed to do a clean up
  immediately, in case of success a clean up could have been delayed.
  This left the door open for a memory leak.
  
  One of the following possibilities were considered when working on a fix:
  - patch the replication logic to do the clean up. Rejected
  as breaks module borders, replication code should not need to know the
  gory details of clean up procedure after CREATE TRIGGER.
  - wrap MYSQLparse with a function that would do a clean up.
  Rejected as ideally we should fix the problem when it happens, not
  adjust for it outside of the problematic code.
  - make sure MYSQLparse cleans up after itself by invoking the clean up
  functionality in the appropriate places before return. Implemented in 
  this patch.
  - use %destructor rule for sp_proc_stmt to restore THD - cleaner
  than the prevoius approach, but rejected
  because needs a careful analysis of the side effects, and this patch is 
  for 5.0, and long term we need to use the next alternative anyway
  - make sure that sp_proc_stmt doesn't juggle with THD - this is a 
  large work that will affect many modules.
  
  Cleanup: move main_lex and main_mem_root from Statement to its
  only two descendants Prepared_statement and THD. This ensures that
  when a Statement instance was created for purposes of statement backup,
  we do not involve LEX constructor/destructor, which is fairly expensive.
  In order to track that the transformation produces equivalent 
  functionality please check the respective constructors and destructors
  of Statement, Prepared_statement and THD - these members were
  used only there.
  This cleanup is unrelated to the patch.

  sql/log_event.cc@1.228, 2007-03-07 12:24:41+03:00, kostja@bodhi.local +2 -2
    THD::main_lex is private and should not be used.

  sql/mysqld.cc@1.592.2.1, 2007-03-07 12:24:42+03:00, kostja@bodhi.local +0 -12
    Move MYSQLerror to sql_yacc.yy as it depends on LEX headers now.

  sql/sql_class.cc@1.256.9.1, 2007-03-07 12:24:42+03:00, kostja@bodhi.local +14 -18
    Cleanup: move main_lex and main_mem_root to THD and Prepared_statement

  sql/sql_class.h@1.314.8.1, 2007-03-07 12:24:42+03:00, kostja@bodhi.local +39 -16
    Cleanup: move main_lex and main_mem_root to THD and Prepared_statement

  sql/sql_lex.cc@1.215, 2007-03-07 12:24:42+03:00, kostja@bodhi.local +30 -0
    Implement st_lex::restore_lex()

  sql/sql_lex.h@1.240, 2007-03-07 12:24:42+03:00, kostja@bodhi.local +4 -0
    Declare st_lex::restore_lex().

  sql/sql_parse.cc@1.593.11.1, 2007-03-07 12:24:42+03:00, kostja@bodhi.local +7 -27
    Consolidate the calls to unit.cleanup() and deletion of lex->sphead
    in mysql_parse (COM_QUERY handler)

  sql/sql_prepare.cc@1.196, 2007-03-07 12:24:42+03:00, kostja@bodhi.local +32 -18
    No need to delete lex->sphead to restore memory roots now in case of a 
    parse error - this is done automatically inside MYSQLparse

  sql/sql_trigger.cc@1.65, 2007-03-07 12:24:42+03:00, kostja@bodhi.local +2 -5
    This code could lead to double deletion apparently, as in case
    of an error lex.sphead was never reset.

  sql/sql_yacc.yy@1.509, 2007-03-07 12:24:42+03:00, kostja@bodhi.local +394 -327
    Trap all returns from the parser to ensure that MySQL-specific cleanup
    is invoked: we need to restore the global state of THD and LEX in 
    case of a parsing error. In case of a parsing success this happens as 
    part of normal grammar reduction process.

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.2377.39.8, 2007-03-07 10:37:30+07:00, tomas@poseidon.mysql.com +1 -0
  source code indentation alignment with 5.1, no real change

  ndb/src/ndbapi/NdbRecAttr.cpp@1.28, 2007-03-07 10:37:19+07:00, tomas@poseidon.mysql.com +193 -189
    source code indentation alignment with 5.1, no real change

ChangeSet@1.2377.39.7, 2007-03-07 08:11:16+07:00, tomas@poseidon.mysql.com +1 -0
  ndb -
    fix printout
    crashes testSystemRestart -n SR_UNDO

  ndb/src/kernel/blocks/dbdih/DbdihMain.cpp@1.66.1.1, 2007-03-07 08:11:07+07:00, tomas@poseidon.mysql.com +1 -1
    fix printout
    crashes testSystemRestart -n SR_UNDO

ChangeSet@1.2392.66.2, 2007-03-06 14:55:52-07:00, tsmith@siva.hindu.god +1 -0
  Bug #25075: sql_class.cc doesn't compile with --without-query-cache
  
  Wrap query_cache_init_query() call with #ifdef HAVE_QUERY_CACHE in THD::THD()

  sql/sql_class.cc@1.256.2.3, 2007-03-06 14:55:48-07:00, tsmith@siva.hindu.god +2 -0
    Bug #25075: sql_class.cc doesn't compile with --without-query-cache
    
    Wrap query_cache_init_query() call with #ifdef HAVE_QUERY_CACHE in THD::THD()

ChangeSet@1.2392.66.1, 2007-03-06 14:47:26-07:00, tsmith@siva.hindu.god +1 -0
  Fix for bug #25595 "missing DBUG_RETURN in function "mysql_stat""

  libmysql/libmysql.c@1.252.1.1, 2007-03-06 14:47:21-07:00, tsmith@siva.hindu.god +1 -1
    Fix for bug #25595 "missing DBUG_RETURN in function "mysql_stat""
    
    Use DBUG_RETURN instead of return

ChangeSet@1.2392.48.16, 2007-03-06 14:30:28-07:00, malff@weblab.(none) +2 -0
  Manual merge

  mysql-test/r/trigger.result@1.55, 2007-03-06 14:30:25-07:00, malff@weblab.(none) +37 -0
    Manual merge

  mysql-test/t/trigger.test@1.62, 2007-03-06 14:30:25-07:00, malff@weblab.(none) +74 -0
    Manual merge

ChangeSet@1.2392.65.1, 2007-03-06 23:58:10+03:00, evgen@moonbone.local +3 -0
  Bug#25376: Incomplete setup of ORDER BY clause results in a wrong result.
  
  Functions over sum functions wasn't set up correctly for the ORDER BY clause
  which leads to a wrong order of the result set.
  
  The split_sum_func() function is called now for each ORDER BY item that
  contains a sum function to set it up correctly.

  mysql-test/r/order_by.result@1.59.1.1, 2007-03-06 23:49:17+03:00, evgen@moonbone.local +8 -0
    Added a test case for bug#25376: Incomplete setup of ORDER BY clause results in a wrong result.

  mysql-test/t/order_by.test@1.42.1.1, 2007-03-06 23:49:15+03:00, evgen@moonbone.local +8 -0
    Added a test case for bug#25376: Incomplete setup of ORDER BY clause results in a wrong result.

  sql/sql_select.cc@1.495.3.1, 2007-03-06 23:49:29+03:00, evgen@moonbone.local +11 -0
    Bug#25376: Incomplete setup of ORDER BY clause results in a wrong result.
    The split_sum_func() function is called now for each ORDER BY item that
    contains a sum function to set it up correctly.

ChangeSet@1.2377.48.3, 2007-03-06 18:52:00+02:00, gkodinov@macbook.gmz +2 -0
  Bug#19342: additional test case for code coverage

  mysql-test/r/func_in.result@1.33, 2007-03-06 18:51:53+02:00, gkodinov@macbook.gmz +7 -1
    Bug#19342: additional test case for code coverage

  mysql-test/t/func_in.test@1.27, 2007-03-06 18:51:54+02:00, gkodinov@macbook.gmz +5 -1
    Bug#19342: additional test case for code coverage

ChangeSet@1.2377.49.1, 2007-03-05 19:42:07-07:00, malff@weblab.(none) +18 -0
  Bug#8407 (Stored functions/triggers ignore exception handler)
  Bug 18914 (Calling certain SPs from triggers fail)
  Bug 20713 (Functions will not not continue for SQLSTATE VALUE '42S02')
  Bug 21825 (Incorrect message error deleting records in a table with a
    trigger for inserting)
  Bug 22580 (DROP TABLE in nested stored procedure causes strange dependency
    error)
  Bug 25345 (Cursors from Functions)
  
  
  This fix resolves a long standing issue originally reported with bug 8407,
  which affect the behavior of Stored Procedures, Stored Functions and Trigger
  in many different ways, causing symptoms reported by all the bugs listed.
  In all cases, the root cause of the problem traces back to 8407 and how the
  server locks tables involved with sub statements.
  
  Prior to this fix, the implementation of stored routines would:
  - compute the transitive closure of all the tables referenced by a top level
  statement
  - open and lock all the tables involved
  - execute the top level statement
  "transitive closure of tables" means collecting:
  - all the tables,
  - all the stored functions,
  - all the views,
  - all the table triggers
  - all the stored procedures
  involved, and recursively inspect these objects definition to find more
  references to more objects, until the list of every object referenced does
  not grow any more.
  This mechanism is known as "pre-locking" tables before execution.
  The motivation for locking all the tables (possibly) used at once is to
  prevent dead locks.
  
  One problem with this approach is that, if the execution path the code
  really takes during runtime does not use a given table, and if the table is
  missing, the server would not execute the statement.
  This in particular has a major impact on triggers, since a missing table
  referenced by an update/delete trigger would prevent an insert trigger to run.
  
  Another problem is that stored routines might define SQL exception handlers
  to deal with missing tables, but the server implementation would never give
  user code a chance to execute this logic, since the routine is never
  executed when a missing table cause the pre-locking code to fail.
  
  With this fix, the internal implementation of the pre-locking code has been
  relaxed of some constraints, so that failure to open a table does not
  necessarily prevent execution of a stored routine.
  
  In particular, the pre-locking mechanism is now behaving as follows:
  
  1) the first step, to compute the transitive closure of all the tables
  possibly referenced by a statement, is unchanged.
  
  2) the next step, which is to open all the tables involved, only attempts
  to open the tables added by the pre-locking code, but silently fails without
  reporting any error or invoking any exception handler is the table is not
  present. This is achieved by trapping internal errors with
  Prelock_error_handler
  
  3) the locking step only locks tables that were successfully opened.
  
  4) when executing sub statements, the list of tables used by each statements
  is evaluated as before. The tables needed by the sub statement are expected
  to be already opened and locked. Statement referencing tables that were not
  opened in step 2) will fail to find the table in the open list, and only at
  this point will execution of the user code fail.
  
  5) when a runtime exception is raised at 4), the instruction continuation
  destination (the next instruction to execute in case of SQL continue
  handlers) is evaluated.
  This is achieved with sp_instr::exec_open_and_lock_tables()
  
  6) if a user exception handler is present in the stored routine, that
  handler is invoked as usual, so that ER_NO_SUCH_TABLE exceptions can be
  trapped by stored routines. If no handler exists, then the runtime execution
  will fail as expected.
  
  With all these changes, a side effect is that view security is impacted, in
  two different ways.
  
  First, a view defined as "select stored_function()", where the stored
  function references a table that may not exist, is considered valid.
  The rationale is that, because the stored function might trap exceptions
  during execution and still return a valid result, there is no way to decide
  when the view is created if a missing table really cause the view to be invalid.
  
  Secondly, testing for existence of tables is now done later during
  execution. View security, which consist of trapping errors and return a
  generic ER_VIEW_INVALID (to prevent disclosing information) was only
  implemented at very specific phases covering *opening* tables, but not
  covering the runtime execution. Because of this existing limitation,
  errors that were previously trapped and converted into ER_VIEW_INVALID are
  not trapped, causing table names to be reported to the user.
  This change is exposing an existing problem, which is independent and will
  be resolved separately.

  mysql-test/r/information_schema_db.result@1.9.1.1, 2007-03-05 19:42:04-07:00, malff@weblab.(none) +3 -3
    Revised the pre-locking code implementation, aligned the tests.

  mysql-test/r/sp-error.result@1.111, 2007-03-05 19:42:04-07:00, malff@weblab.(none) +137 -6
    Revised the pre-locking code implementation, aligned the tests.

  mysql-test/r/sp.result@1.218.1.1, 2007-03-05 19:42:04-07:00, malff@weblab.(none) +40 -2
    Revised the pre-locking code implementation, aligned the tests.

  mysql-test/r/trigger.result@1.50.1.1, 2007-03-05 19:42:04-07:00, malff@weblab.(none) +37 -0
    Revised the pre-locking code implementation, aligned the tests.

  mysql-test/r/view.result@1.186.2.1, 2007-03-05 19:42:04-07:00, malff@weblab.(none) +3 -3
    Revised the pre-locking code implementation, aligned the tests.

  mysql-test/t/sp-error.test@1.112, 2007-03-05 19:42:04-07:00, malff@weblab.(none) +187 -6
    Revised the pre-locking code implementation, aligned the tests.

  mysql-test/t/sp.test@1.208.1.1, 2007-03-05 19:42:04-07:00, malff@weblab.(none) +49 -4
    Revised the pre-locking code implementation, aligned the tests.

  mysql-test/t/trigger.test@1.58.1.1, 2007-03-05 19:42:04-07:00, malff@weblab.(none) +74 -0
    Revised the pre-locking code implementation, aligned the tests.

  sql/lock.cc@1.93.1.1, 2007-03-05 19:42:04-07:00, malff@weblab.(none) +1 -1
    table->placeholder now checks for schema_table

  sql/mysqld.cc@1.582.21.1, 2007-03-05 19:42:04-07:00, malff@weblab.(none) +8 -0
    my_message_sql(): invoke internal exception handlers

  sql/sp_head.cc@1.230.4.1, 2007-03-05 19:42:04-07:00, malff@weblab.(none) +40 -9
    exec_open_and_lock_tables(): open and lock tables, or return the
    continuation destination of this instruction

  sql/sp_head.h@1.90.1.1, 2007-03-05 19:42:04-07:00, malff@weblab.(none) +24 -0
    exec_open_and_lock_tables(): open and lock tables, or return the
    continuation destination of this instruction

  sql/sql_base.cc@1.360.10.1, 2007-03-05 19:42:04-07:00, malff@weblab.(none) +94 -8
    Prelock_error_handler: delay open table errors until execution

  sql/sql_class.cc@1.256.8.1, 2007-03-05 19:42:04-07:00, malff@weblab.(none) +32 -0
    THD: add internal error handler, as an exception mechanism.

  sql/sql_class.h@1.314.6.1, 2007-03-05 19:42:04-07:00, malff@weblab.(none) +67 -0
    THD: add internal error handler, as an exception mechanism.

  sql/sql_update.cc@1.205.7.1, 2007-03-05 19:42:04-07:00, malff@weblab.(none) +1 -1
    table->placeholder now checks for schema_table

  sql/table.cc@1.240.4.1, 2007-03-05 19:42:04-07:00, malff@weblab.(none) +3 -1
    st_table_list::hide_view_error(): masked more errors for view security

  sql/table.h@1.137.2.1, 2007-03-05 19:42:04-07:00, malff@weblab.(none) +1 -1
    table->placeholder now checks for schema_table, and unopened tables

ChangeSet@1.2392.1.71, 2007-03-05 17:16:16+01:00, msvensson@pilot.blaudden +1 -0
  Fix VC++ warning, "conversion from ha_checksum to char"

  extra/comp_err.c@1.29, 2007-03-05 17:16:15+01:00, msvensson@pilot.blaudden +1 -1
    Fix VC++ warning, "conversion from ha_checksum to char"

ChangeSet@1.2392.60.2, 2007-03-05 14:02:29+01:00, tnurnberg@mysql.com +1 -0
  Bug#21103: DATE column not compared as DATE
  
  When comparing a DATE field with a DATETIME constant, we now compare
  as DATETIMEs, not as DATEs.  Fix BDB queries to still work.

  mysql-test/r/ps_6bdb.result@1.47, 2007-03-05 14:02:26+01:00, tnurnberg@mysql.com +6 -6
    Bug#21103: DATE column not compared as DATE
    
    When comparing a DATE field with a DATETIME constant, we now compare
    as DATETIMEs, not as DATEs.  Fix BDB queries to still work.

ChangeSet@1.1616.2987.1, 2007-03-05 11:52:28+01:00, istruewing@chilla.local +3 -0
  Bug#26464 - insert delayed + update + merge = corruption
  
  Using INSERT DELAYED on MERGE tables could lead to table
  corruptions.
  
  The manual lists a couple of storage engines, which can be
  used with INSERT DELAYED. MERGE is not in this list.
  
  The attempt to try it anyway has not been rejected yet.
  This bug was not detected earlier as it can work under
  special circumstances. Most notable is low concurrency.
  
  To be safe, this patch rejects any attempt to use INSERT
  DELAYED on MERGE tables.

  mysql-test/r/merge.result@1.32.1.13, 2007-03-05 11:52:25+01:00, istruewing@chilla.local +5 -0
    Bug#26464 - insert delayed + update + merge = corruption
    Added test result.

  mysql-test/t/merge.test@1.28.1.14, 2007-03-05 11:52:26+01:00, istruewing@chilla.local +9 -0
    Bug#26464 - insert delayed + update + merge = corruption
    Added test.

  sql/ha_myisammrg.h@1.35.1.5, 2007-03-05 11:52:26+01:00, istruewing@chilla.local +1 -1
    Bug#26464 - insert delayed + update + merge = corruption
    Removed HA_CAN_INSERT_DELAYED flag from table_flags().
    The insert delayed thread upgrades the lock from the first
    entry in MYSQL_LOCK::locks only. Hence it is incapable to
    handle MERGE tables, which have as many entries in this
    array as they have MyISAM sub-tables.

ChangeSet@1.2392.63.3, 2007-03-05 11:42:03+01:00, msvensson@pilot.blaudden +2 -0
  Remove ssl_des.test and ssl_des.result

  BitKeeper/deleted/.del-ssl_des.result@1.2, 2007-03-05 11:41:44+01:00, msvensson@pilot.blaudden +0 -0
    Delete: mysql-test/r/ssl_des.result

  BitKeeper/deleted/.del-ssl_des.test@1.3, 2007-03-05 11:41:37+01:00, msvensson@pilot.blaudden +0 -0
    Delete: mysql-test/t/ssl_des.test

ChangeSet@1.2392.63.2, 2007-03-05 10:07:22+01:00, msvensson@pilot.blaudden +2 -0
  Bug#21781 Replication slave io thread hangs
   - Add test case that shows how slave server hangs in "STOP SLAVE"
     when run on MySQL version 5.0.33 compiled with OpenSSL.
     Works fine with latest version of MySQL since that problem
     has been fixed by patch for bug#24148. The fix has been noted in
     the changelog for MySQL 5.0.36

  mysql-test/r/rpl_ssl.result@1.1, 2007-03-05 10:07:21+01:00, msvensson@pilot.blaudden +93 -0
    New BitKeeper file ``mysql-test/r/rpl_ssl.result''

  mysql-test/r/rpl_ssl.result@1.0, 2007-03-05 10:07:21+01:00, msvensson@pilot.blaudden +0 -0

  mysql-test/t/rpl_ssl.test@1.1, 2007-03-05 10:07:21+01:00, msvensson@pilot.blaudden +60 -0
    New BitKeeper file ``mysql-test/t/rpl_ssl.test''

  mysql-test/t/rpl_ssl.test@1.0, 2007-03-05 10:07:21+01:00, msvensson@pilot.blaudden +0 -0

ChangeSet@1.2392.63.1, 2007-03-05 10:03:42+01:00, msvensson@pilot.blaudden +13 -0
  Add "have_ssl" as synonym for "have_openssl"

  mysql-test/t/ssl_des.test@1.2, 2007-03-05 10:03:40+01:00, msvensson@pilot.blaudden +1 -1
    Add "have_ssl" as synonym for "have_openssl"

  mysql-test/include/have_ssl.inc@1.6, 2007-03-05 10:03:40+01:00, msvensson@pilot.blaudden +2 -2
    Add "have_ssl" as synonym for "have_openssl"

  mysql-test/include/have_ssl.inc@1.5, 2007-03-02 16:51:17+01:00, msvensson@pilot.blaudden +0 -0
    Rename: mysql-test/include/have_openssl.inc -> mysql-test/include/have_ssl.inc

  mysql-test/r/have_ssl.require@1.5, 2007-03-05 10:03:40+01:00, msvensson@pilot.blaudden +1 -1
    Add "have_ssl" as synonym for "have_openssl"

  mysql-test/r/have_ssl.require@1.4, 2007-03-02 16:51:58+01:00, msvensson@pilot.blaudden +0 -0
    Rename: mysql-test/r/have_openssl.require -> mysql-test/r/have_ssl.require

  mysql-test/t/func_des_encrypt.test@1.3, 2007-03-05 10:03:40+01:00, msvensson@pilot.blaudden +1 -1
    Add "have_ssl" as synonym for "have_openssl"

  mysql-test/t/func_encrypt.test@1.8, 2007-03-05 10:03:40+01:00, msvensson@pilot.blaudden +1 -1
    Add "have_ssl" as synonym for "have_openssl"

  mysql-test/t/openssl_1.test@1.18, 2007-03-05 10:03:40+01:00, msvensson@pilot.blaudden +4 -3
    Add "have_ssl" as synonym for "have_openssl"
    Correct comment

  mysql-test/t/rpl_openssl.test@1.21, 2007-03-05 10:03:40+01:00, msvensson@pilot.blaudden +1 -1
    Add "have_ssl" as synonym for "have_openssl"

  mysql-test/t/ssl.test@1.4, 2007-03-05 10:03:40+01:00, msvensson@pilot.blaudden +1 -1
    Add "have_ssl" as synonym for "have_openssl"

  mysql-test/t/ssl_compress.test@1.4, 2007-03-05 10:03:40+01:00, msvensson@pilot.blaudden +1 -1
    Add "have_ssl" as synonym for "have_openssl"

  mysql-test/t/ssl_connect.test@1.2, 2007-03-05 10:03:40+01:00, msvensson@pilot.blaudden +1 -1
    Add "have_ssl" as synonym for "have_openssl"

  sql/mysql_priv.h@1.429.2.9, 2007-03-05 10:03:40+01:00, msvensson@pilot.blaudden +1 -1
    Add "have_ssl" as synonym for "have_openssl"

  sql/mysqld.cc@1.582.1.20, 2007-03-05 10:03:40+01:00, msvensson@pilot.blaudden +5 -5
    Add "have_ssl" as synonym for "have_openssl"

  sql/set_var.cc@1.176.1.5, 2007-03-05 10:03:40+01:00, msvensson@pilot.blaudden +3 -1
    Add "have_ssl" as synonym for "have_openssl"

ChangeSet@1.1616.2986.1, 2007-03-05 09:52:40+01:00, msvensson@pilot.blaudden +1 -0
  Bug #26792 Add DBX debugger support to mysql-test-run.pl
   - Add --debugger=dbx
   - Fix --debugger=devenv, --debugger=DevEnv and --debugger=/path/devenv

  mysql-test/mysql-test-run.pl@1.8.20.7, 2007-03-05 09:52:39+01:00, msvensson@pilot.blaudden +20 -6
    Add support for --debugger=dbx to mysql-test-run.pl
    Fix case senitive match for vc, vcexpress or deven
    Make it possible to use full path to debugger for
    --debugger=/path/vcexpress

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.54.7, 2007-03-04 19:54:35-08:00, igor@olga.mysql.com +7 -0
  Fixed bug #26560.
  The flag alias_name_used was not set on for the outer references
  in subqueries. It resulted in replacement of any outer reference
  resolved against an alias for a full field name when the frm 
  representation of a view with a subquery was generated. 
  If the subquery and the outer query referenced the same table in
  their from lists this replacement effectively changed the meaning
  of the view and led to wrong results for selects from this view. 
  
  Modified several functions to ensure setting the right value of
  the alias_name_used flag for outer references resolved against
  aliases.
   

  mysql-test/r/view.result@1.191.1.1, 2007-03-04 19:54:30-08:00, igor@olga.mysql.com +37 -0
    Added a test case for bug #26560.
    

  mysql-test/t/view.test@1.176.1.1, 2007-03-04 19:54:30-08:00, igor@olga.mysql.com +40 -0
    Added a test case for bug #26560.

  sql/item.cc@1.251.1.1, 2007-03-04 19:54:30-08:00, igor@olga.mysql.com +17 -9
    Fixed bug #26560.
    Made the function resolve_ref_in_select_and_group analyze the return
    value of the last parameter with the type of the name resolution for
    the submitted reference. If the reference has been resolved against 
    an alias name from select list then its flag alias_name_used is set on.
    Now this value is used in Item_field::fix_outer_field to initialize the flag
    when the item_ref object is created for an outer reference.
    Added a parameter for the second Item_ref::Item_ref constructor to initialize
    properly the flag alias_name_used. The default value of the parameter is FALSE.
    If this flag is set on at the creation of an object by this constructor it
    will never be changed. Corrected appropriately the Item_ref::set_properties
    function.
    The function Item_ref::print now prints alias name for an outer reference
    if the flag alias_name_used is set on.  

  sql/item.h@1.220, 2007-03-04 19:54:30-08:00, igor@olga.mysql.com +7 -3
    Fixed bug #26560.
    Added a parameter for the second Item_ref::Item_ref constructor to initialize
    properly the flag alias_name_used. The default value of the parameter is FALSE.
    A similar change has been applied to the first Item_direct_ref::Item_direct_ref
    constructor.

  sql/mysql_priv.h@1.429.1.6, 2007-03-04 19:54:30-08:00, igor@olga.mysql.com +21 -1
    Fixed bug #26560.
    Added an an enumeration type enum_resolution_type to return info on
    how the function find_item_in_list has resolved the submitted item.
    The type is used only for this function.

  sql/sql_base.cc@1.360.8.3, 2007-03-04 19:54:30-08:00, igor@olga.mysql.com +69 -52
    Fixed bug #26560.
    Made the last parameter of the function find_field_in_tables return
    more detailed information on how the submitted item has been resolved.
    Now it says whether the item has been resolved
      against an alias name,
      or as a field name without alias,
      or as a field name hidden by alias, 
      or was resolved ignoring alias. 

  sql/sql_select.cc@1.495.1.1, 2007-03-04 19:54:30-08:00, igor@olga.mysql.com +4 -4
    Fixed bug #26560.
    Took into account the new type of the last parameter of the function
    find_item_in_list. 

ChangeSet@1.1616.2984.1, 2007-03-04 00:47:42+03:00, evgen@sunlight.local +4 -0
  Bug#25126: Wrongly resolved field leads to a crash.
  
  When the ORDER BY clause gets fixed it's allowed to search in the current
  item_list in order to find aliased fields and expressions. This is ok for a
  SELECT but wrong for an UPDATE statement. If the ORDER BY clause will
  contain a non-existing field which is mentioned in the UPDATE set list
  then the server will crash due to using of non-existing (0x0) field.
  
  When an Item_field is getting fixed it's allowed to search item list for
  aliased expressions and fields only for selects.

  mysql-test/r/update.result@1.22.1.9, 2007-03-04 00:46:39+03:00, evgen@sunlight.local +4 -0
    Added a test case for bug#25126: Wrongly resolved field leads to a crash.

  mysql-test/t/update.test@1.19.1.10, 2007-03-04 00:46:43+03:00, evgen@sunlight.local +8 -0
    Added a test case for bug#25126: Wrongly resolved field leads to a crash.

  sql/sql_base.cc@1.145.1.131, 2007-03-04 00:45:51+03:00, evgen@sunlight.local +30 -1
    Bug#25126: Wrongly resolved field leads to a crash.
    When an Item_field is getting fixed it's allowed to search item list for
    aliased expressions and fields only for selects.

  sql/sql_select.cc@1.216.125.20, 2007-03-04 00:46:24+03:00, evgen@sunlight.local +2 -5
    Bug#25126: Wrongly resolved field leads to a crash.
    When an Item_field is getting fixed it's allowed to search item list for
    aliased expressions and fields only for selects.

ChangeSet@1.2392.54.6, 2007-03-02 19:32:46+02:00, gkodinov@magare.gmz +1 -0
  fixed win32 warnings

  sql/item_cmpfunc.h@1.143.2.2, 2007-03-02 19:32:45+02:00, gkodinov@magare.gmz +1 -1
    fixed win32 warnings

ChangeSet@1.2377.48.2, 2007-03-02 19:27:32+02:00, gkodinov@macbook.gmz +1 -0
  fixed win32 warning

  sql/item_cmpfunc.h@1.139.2.2, 2007-03-02 19:27:26+02:00, gkodinov@macbook.gmz +1 -1
    fixed win32 warning

ChangeSet@1.1616.2982.6, 2007-03-02 16:32:27+01:00, joerg@trift2. +1 -0
  More man pages for the RPMs.

  support-files/mysql.spec.sh@1.83.1.49, 2007-03-02 16:32:25+01:00, joerg@trift2. +2 -0
    More man pages.

ChangeSet@1.1346.894.2, 2007-03-02 16:30:22+01:00, joerg@trift2. +1 -0
  Another man page in the RPMs.

  support-files/mysql.spec.sh@1.61.1.39, 2007-03-02 16:30:21+01:00, joerg@trift2. +1 -0
    Another man page.

ChangeSet@1.2377.48.1, 2007-03-02 16:25:56+02:00, gkodinov@macbook.gmz +5 -0
  Bug #19342:
  Several problems here :
   1. The conversion to double of an hex string const item
   was not taking into account the unsigned flag.
   
   2. IN was not behaving in the same was way as comparisons
   when performed over an INT/DATE/DATETIME/TIMESTAMP column
   and a constant. The ordinary comparisons in that case 
   convert the constant to an INTEGER value and do int 
   comparisons. Fixed the IN to do the same.
   
   3. IN is not taking into account the unsigned flag when 
   calculating <expr> IN (<int_const1>, <int_const2>, ...).
   Extended the implementation of IN to store and process
   the unsigned flag for its arguments.

  mysql-test/r/func_in.result@1.32, 2007-03-02 16:25:48+02:00, gkodinov@macbook.gmz +66 -0
    Bug #19342: test case

  mysql-test/t/func_in.test@1.26, 2007-03-02 16:25:48+02:00, gkodinov@macbook.gmz +58 -0
    Bug #19342: test case

  sql/item.h@1.213.6.1, 2007-03-02 16:25:49+02:00, gkodinov@macbook.gmz +4 -1
    Bug #19342: correct handling of sign in conersion to real.

  sql/item_cmpfunc.cc@1.231.2.1, 2007-03-02 16:25:50+02:00, gkodinov@macbook.gmz +125 -5
    Bug #19342: exteneded the IN values list
     to support unsigned longlong values.
     Correct comparison of integers in IN with
     regard of signedness.
     Compare DATE/DATETIME/TIMESTAMP values as
     integers in IN.

  sql/item_cmpfunc.h@1.139.2.1, 2007-03-02 16:25:50+02:00, gkodinov@macbook.gmz +15 -2
    Bug #19342: exteneded the IN values list
     to support unsigned longlong values.
     Correct comparison of integers in IN with
     regard of signedness.

ChangeSet@1.2392.60.1, 2007-03-02 15:23:13+01:00, tnurnberg@mysql.com +9 -0
  Bug #21103: DATE column not compared as DATE
  
  If we compare two items A and B, with B being (a constant) of a
  larger type, then A gets promoted to B's type for comparison if
  it's a constant, function, or CAST() column, but B gets demoted
  to A's type if A is a (not explicitly CAST()) column. This is
  counter-intuitive and not mandated by the standard.
   
  Disabling optimisation where it would be lossy so field value
  will properly get promoted and compared as binary string (rather
  than as integers).

  mysql-test/include/ps_conv.inc@1.6, 2007-03-02 15:23:09+01:00, tnurnberg@mysql.com +6 -6
    Bug #21103: DATE column not compared as DATE
    
    When comparing a DATE field with a DATETIME constant, we now compare
    as DATETIMEs, not as DATEs.  Fix certain queries to still work.

  mysql-test/r/func_time.result@1.79.1.2, 2007-03-02 15:23:10+01:00, tnurnberg@mysql.com +17 -0
    Bug #21103: DATE column not compared as DATE
    
    When comparing a DATE field with a DATETIME constant, we now compare
    as DATETIMEs, not as DATEs.  Show that everything works as expected.

  mysql-test/r/ps_2myisam.result@1.45, 2007-03-02 15:23:10+01:00, tnurnberg@mysql.com +6 -6
    Bug #21103: DATE column not compared as DATE
    
    When comparing a DATE field with a DATETIME constant, we now compare
    as DATETIMEs, not as DATEs.  Fix certain queries to still work.

  mysql-test/r/ps_3innodb.result@1.48, 2007-03-02 15:23:10+01:00, tnurnberg@mysql.com +6 -6
    Bug #21103: DATE column not compared as DATE
    
    When comparing a DATE field with a DATETIME constant, we now compare
    as DATETIMEs, not as DATEs.  Fix certain queries to still work.

  mysql-test/r/ps_4heap.result@1.44, 2007-03-02 15:23:10+01:00, tnurnberg@mysql.com +6 -6
    Bug #21103: DATE column not compared as DATE
    
    When comparing a DATE field with a DATETIME constant, we now compare
    as DATETIMEs, not as DATEs.  Fix certain queries to still work.

  mysql-test/r/ps_5merge.result@1.45, 2007-03-02 15:23:10+01:00, tnurnberg@mysql.com +12 -12
    Bug #21103: DATE column not compared as DATE
    
    When comparing a DATE field with a DATETIME constant, we now compare
    as DATETIMEs, not as DATEs.  Fix certain queries to still work.

  mysql-test/r/ps_7ndb.result@1.48, 2007-03-02 15:23:10+01:00, tnurnberg@mysql.com +6 -6
    Bug #21103: DATE column not compared as DATE
    
    When comparing a DATE field with a DATETIME constant, we now compare
    as DATETIMEs, not as DATEs.  Fix certain queries to still work.

  mysql-test/t/func_time.test@1.66.1.2, 2007-03-02 15:23:10+01:00, tnurnberg@mysql.com +13 -0
    Bug #21103: DATE column not compared as DATE
    
    When comparing a DATE field with a DATETIME constant, we now compare
    as DATETIMEs, not as DATEs.  Show that everything works as expected.

  sql/field.cc@1.335.3.1, 2007-03-02 15:23:10+01:00, tnurnberg@mysql.com +13 -10
    Bug #21103: DATE column not compared as DATE
    
    #0 stores the date only as a 3-byte integer; save_in_field() in
    #1 saves 'this' in field's format (DATE), #2 "converts a constant
    item to an int and replaces the original item" -- consequently,
    this replaces the Item_string "2006-11-06 04:08:36.0" with the
    Item_int_with_ref 20061106.
    
    #0  Field_newdate::store (this=0x8d26880, from=0x8d5e658 "2006-11-06
    04:08:36.0", len=21, cs=0x88022c0) at field.cc:5344
    #1  0x0817e3b0 in Item_string::save_in_field (this=0x8d5e670, field=0x8d26880, no_conversions=true) at item.cc:4340
    #2  0x081b22ae in convert_constant_item (thd=0x8d25240, field=0x8d26880, item=0x8d5e74c) at item_cmpfunc.cc:245
    #3  0x081b8a36 in Item_bool_func2::fix_length_and_dec (this=0x8d5e6f8) at item_cmpfunc.cc:309
    #4  0x081a3427 in Item_func::fix_fields (this=0x8d5e6f8, thd=0x8d25240, ref=0x8d5f5fc) at item_func.cc:190
    #5  0x0825bc2d in setup_conds (thd=0x8d25240, tables=0x8d5e410, leaves=0x8d5e410, conds=0x8d5f5fc) at sql_base.cc:4941
    ...
    
    Disabling optimisation where it would be lossy so field value will
    properly get promoted and compared as binary string (rather than as
    integers).

ChangeSet@1.2392.1.68, 2007-03-02 15:21:01+01:00, msvensson@pilot.blaudden +1 -0
  Add hint about using --help to see what options are available

  BUILD/SETUP.sh@1.64, 2007-03-02 15:21:00+01:00, msvensson@pilot.blaudden +1 -0
    Add hint about using --help to see what options are available

ChangeSet@1.2392.58.1, 2007-03-02 14:08:32+01:00, joerg@trift2. +1 -0
  Add the man pages for NDB to the RPMs.

  support-files/mysql.spec.sh@1.167, 2007-03-02 14:08:29+01:00, joerg@trift2. +21 -6
    Add the man pages for NDB.

ChangeSet@1.1616.2982.4, 2007-03-02 14:05:43+01:00, joerg@trift2. +1 -0
  Add the man pages for NDB to the RPMs.

  support-files/mysql.spec.sh@1.83.1.47, 2007-03-02 14:05:40+01:00, joerg@trift2. +19 -5
    Add the man pages for NDB.

ChangeSet@1.1346.894.1, 2007-03-02 14:03:28+01:00, joerg@trift2. +1 -0
  Add missing man pages to the RPMs.

  support-files/mysql.spec.sh@1.61.1.38, 2007-03-02 14:03:27+01:00, joerg@trift2. +9 -0
    Add missing man pages.

ChangeSet@1.2392.48.13, 2007-03-02 15:05:16+03:00, kostja@bodhi.local +1 -0
  Freeze the number of conflicts. We should not introduce any more
  conflicts without proper analysis and documentation of the nature of
  the conflict.

  sql/sql_yacc.yy@1.508, 2007-03-02 15:05:13+03:00, kostja@bodhi.local +5 -0
    Freeze the number of conflicts. We should not introduce any more
    conflicts without proper analysis and documentation of the nature of
    the conflict.

ChangeSet@1.2392.48.12, 2007-03-02 14:29:51+03:00, kostja@bodhi.local +1 -0
  Rename a macro to better reflect the action taken.

  sql/sql_yacc.yy@1.507, 2007-03-02 14:29:48+03:00, kostja@bodhi.local +19 -19
    Rename: YYERROR_UNLESS -> YYABORT_UNLESS
    yyerror doesn't have to abort of the parser, whereas this macro
    does explicitly call YYABORT.

ChangeSet@1.2392.42.2, 2007-03-02 15:09:44+04:00, ramil@mysql.com +7 -0
  after merge fix (bug #26038)
  
  Item_func_geometry_from_text::val_str() should set null_value
  in case of wrong data.

  mysql-test/include/gis_generic.inc@1.4, 2007-03-02 15:09:43+04:00, ramil@mysql.com +2 -2
    after merge fix
    
    Item_func_geometry_from_text::val_str() should set null_value
    in case of wrong data.

  mysql-test/r/archive_gis.result@1.4, 2007-03-02 15:09:43+04:00, ramil@mysql.com +2 -2
    after merge fix
    
    Item_func_geometry_from_text::val_str() should set null_value
    in case of wrong data.

  mysql-test/r/gis.result@1.41, 2007-03-02 15:09:43+04:00, ramil@mysql.com +46 -4
    after merge fix
    
    Item_func_geometry_from_text::val_str() should set null_value
    in case of wrong data.

  mysql-test/r/innodb_gis.result@1.4, 2007-03-02 15:09:43+04:00, ramil@mysql.com +2 -2
    after merge fix
    
    Item_func_geometry_from_text::val_str() should set null_value
    in case of wrong data.

  mysql-test/r/ndb_gis.result@1.5, 2007-03-02 15:09:43+04:00, ramil@mysql.com +4 -4
    after merge fix
    
    Item_func_geometry_from_text::val_str() should set null_value
    in case of wrong data.

  mysql-test/t/gis.test@1.34, 2007-03-02 15:09:43+04:00, ramil@mysql.com +2 -2
    after merge fix
    
    Item_func_geometry_from_text::val_str() should set null_value
    in case of wrong data.

  sql/item_geofunc.cc@1.27.1.4, 2007-03-02 15:09:43+04:00, ramil@mysql.com +2 -5
    after merge fix
    
    Item_func_geometry_from_text::val_str() should set null_value
    in case of wrong data.

ChangeSet@1.2392.54.3, 2007-03-02 13:25:41+03:00, evgen@sunlight.local +1 -0
  sql_base.cc:
    Post fix for bug#25122.

  sql/sql_base.cc@1.360.8.2, 2007-03-02 13:23:54+03:00, evgen@sunlight.local +2 -1
    Post fix for bug#25122.

ChangeSet@1.2392.57.1, 2007-03-02 12:14:50+02:00, gkodinov@magare.gmz +3 -0
  Bug #26537: item_unhex() was not expected 
  to return NULL for non-NULL arguments.
  This is not the case as it can return NULL
  for invalid hexidecimal strings.
  Fixed by setting the maybe_null flag.

  mysql-test/r/func_str.result@1.126.1.1, 2007-03-02 12:14:49+02:00, gkodinov@magare.gmz +6 -0
    Bug #26537: test case

  mysql-test/t/func_str.test@1.99.1.1, 2007-03-02 12:14:49+02:00, gkodinov@magare.gmz +6 -0
    Bug #26537: test case

  sql/item_strfunc.h@1.121, 2007-03-02 12:14:49+02:00, gkodinov@magare.gmz +5 -1
    Bug #26537: item_unhex() can return NULLs
    even for guaranteed non-null arguments.

ChangeSet@1.2377.47.1, 2007-03-01 19:20:47-07:00, malff@weblab.(none) +3 -0
  Bug#26093 (SELECT BENCHMARK() for SELECT statements does not produce valid
    results)
  
  Before this fix, the function BENCHMARK() would fail to evaluate expressions
  like "(select avg(a) from t1)" in debug builds (with an assert),
  or would report a time of zero in non debug builds.
  
  The root cause is that evaluation of DECIMAL_RESULT expressions was not
  supported in Item_func_benchmark::val_int().
  
  This has been fixed by this change.

  mysql-test/r/func_misc.result@1.27, 2007-03-01 19:20:46-07:00, malff@weblab.(none) +44 -0
    Added support for DECIMAL_RESULT in Item_func_benchmark::val_int()

  mysql-test/t/func_misc.test@1.21, 2007-03-01 19:20:46-07:00, malff@weblab.(none) +57 -0
    Added support for DECIMAL_RESULT in Item_func_benchmark::val_int()

  sql/item_func.cc@1.317.9.1, 2007-03-01 19:20:46-07:00, malff@weblab.(none) +4 -0
    Added support for DECIMAL_RESULT in Item_func_benchmark::val_int()

ChangeSet@1.2377.39.6, 2007-03-02 09:06:05+07:00, tomas@poseidon.mysql.com +7 -0
  Bug #25275 SINGLE USER MODE prevents ALTER on non-ndb tables for other mysqld nodes
  (part 1)
  - add signal data
  - add ref in dict on create/drop table/index

  ndb/include/kernel/signaldata/AlterTable.hpp@1.7, 2007-03-02 09:05:59+07:00, tomas@poseidon.mysql.com +2 -1
    Bug #25275 SINGLE USER MODE prevents ALTER on non-ndb tables for other mysqld nodes
    (part 1)
    - add signal data
    - add ref in dict on create/drop table/index

  ndb/include/kernel/signaldata/CreateIndx.hpp@1.9, 2007-03-02 09:05:59+07:00, tomas@poseidon.mysql.com +2 -1
    Bug #25275 SINGLE USER MODE prevents ALTER on non-ndb tables for other mysqld nodes
    (part 1)
    - add signal data
    - add ref in dict on create/drop table/index

  ndb/include/kernel/signaldata/CreateTable.hpp@1.6, 2007-03-02 09:05:59+07:00, tomas@poseidon.mysql.com +2 -1
    Bug #25275 SINGLE USER MODE prevents ALTER on non-ndb tables for other mysqld nodes
    (part 1)
    - add signal data
    - add ref in dict on create/drop table/index

  ndb/include/kernel/signaldata/DropIndx.hpp@1.6, 2007-03-02 09:05:59+07:00, tomas@poseidon.mysql.com +2 -1
    Bug #25275 SINGLE USER MODE prevents ALTER on non-ndb tables for other mysqld nodes
    (part 1)
    - add signal data
    - add ref in dict on create/drop table/index

  ndb/include/kernel/signaldata/DropTable.hpp@1.6, 2007-03-02 09:05:59+07:00, tomas@poseidon.mysql.com +2 -1
    Bug #25275 SINGLE USER MODE prevents ALTER on non-ndb tables for other mysqld nodes
    (part 1)
    - add signal data
    - add ref in dict on create/drop table/index

  ndb/src/kernel/blocks/dbdict/Dbdict.cpp@1.71.1.2, 2007-03-02 09:05:59+07:00, tomas@poseidon.mysql.com +41 -0
    Bug #25275 SINGLE USER MODE prevents ALTER on non-ndb tables for other mysqld nodes
    (part 1)
    - add signal data
    - add ref in dict on create/drop table/index

  ndb/src/ndbapi/ndberror.c@1.55, 2007-03-02 09:05:59+07:00, tomas@poseidon.mysql.com +1 -0
    Bug #25275 SINGLE USER MODE prevents ALTER on non-ndb tables for other mysqld nodes
    (part 1)
    - add signal data
    - add ref in dict on create/drop table/index

ChangeSet@1.2377.39.5, 2007-03-02 08:56:22+07:00, tomas@poseidon.mysql.com +1 -0
  Bug #26720 Infinite loop on unknown signal in logging function
  - terminate printing

  ndb/src/common/debugger/signaldata/PackedSignal.cpp@1.3, 2007-03-02 08:56:14+07:00, tomas@poseidon.mysql.com +2 -0
    Bug #26720 Infinite loop on unknown signal in logging function
    - terminate printing

ChangeSet@1.2392.55.2, 2007-03-02 00:54:02+01:00, kent@mysql.com +1 -0
  mysql.sln:
    Correction of embedded build types

  VC++Files/mysql.sln@1.15, 2007-03-02 00:04:10+01:00, kent@mysql.com +4 -4
    Correction of embedded build types

ChangeSet@1.2392.55.1, 2007-03-01 23:48:22+01:00, kent@mysql.com +1 -0
  mysql.sln:
    Disabled build of all embedded server libraries, "libmysqld.ldd"
    "mysqldemb.lib" and "mysqlserver.lib"

  VC++Files/mysql.sln@1.14, 2007-03-01 23:45:55+01:00, kent@mysql.com +15 -22
    Disabled build of all embedded server libraries, "libmysqld.ldd"
    "mysqldemb.lib" and "mysqlserver.lib"

ChangeSet@1.2392.48.10, 2007-03-01 15:10:14-07:00, malff@weblab.(none) +2 -0
  Manual merge of 5.0 into 5.0-runtime

  mysql-test/r/subselect.result@1.176, 2007-03-01 15:10:11-07:00, malff@weblab.(none) +51 -9
    Manual merge

  mysql-test/t/subselect.test@1.143, 2007-03-01 15:10:11-07:00, malff@weblab.(none) +28 -0
    Manual merge

ChangeSet@1.2392.15.6, 2007-03-02 00:09:22+03:00, evgen@moonbone.local +7 -0
  Bug#25122: Views based on a self-joined table aren't insertable.
  
  When INSERT is done over a view the table being inserted into is 
  checked to be unique among all views tables. But if the view contains
  self-joined table an error will be thrown even if all tables are used under
  different aliases.
  
  The unique_table() function now also checks tables' aliases when needed.

  sql/mysql_priv.h@1.429.11.1, 2007-03-02 00:09:02+03:00, evgen@moonbone.local +2 -1
    Bug#25122:  Views based on a self-joined table aren't insertable.
    Updated prototype of the unique_table() function.

  sql/sql_base.cc@1.360.7.1, 2007-03-02 00:09:04+03:00, evgen@moonbone.local +7 -2
    Bug#25122:  Views based on a self-joined table aren't insertable.
    Now the unique_table() function checks tables' aliases when needed.

  sql/sql_delete.cc@1.188.2.1, 2007-03-02 00:09:05+03:00, evgen@moonbone.local +2 -2
    Bug#25122:  Views based on a self-joined table aren't insertable.
    Updated calls to the unique_table() function.

  sql/sql_insert.cc@1.211.4.6, 2007-03-02 00:09:05+03:00, evgen@moonbone.local +2 -2
    Bug#25122:  Views based on a self-joined table aren't insertable.
    Updated calls to the unique_table() function.

  sql/sql_load.cc@1.102.3.1, 2007-03-02 00:09:06+03:00, evgen@moonbone.local +1 -1
    Bug#25122:  Views based on a self-joined table aren't insertable.
    Updated calls to the unique_table() function.

  sql/sql_parse.cc@1.593.9.1, 2007-03-02 00:09:06+03:00, evgen@moonbone.local +2 -2
    Bug#25122:  Views based on a self-joined table aren't insertable.
    Updated calls to the unique_table() function.

  sql/sql_update.cc@1.205.6.1, 2007-03-02 00:09:07+03:00, evgen@moonbone.local +3 -3
    Bug#25122:  Views based on a self-joined table aren't insertable.
    Updated calls to the unique_table() function.

ChangeSet@1.2392.1.67, 2007-03-01 20:59:08+01:00, msvensson@pilot.blaudden +2 -0
  After merge fixes

  mysql-test/r/mysqlbinlog.result@1.33, 2007-03-01 20:59:07+01:00, msvensson@pilot.blaudden +1 -2
    After merge fixes

  mysql-test/t/mysqlbinlog.test@1.44, 2007-03-01 20:59:07+01:00, msvensson@pilot.blaudden +1 -2
    After merge fixes

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.1616.2983.5, 2007-03-01 19:09:43+01:00, msvensson@pilot.blaudden +1 -0
  Add two more USE_CYGWIN ifdefs to mysqltest

  client/mysqltest.c@1.92.21.52, 2007-03-01 19:09:42+01:00, msvensson@pilot.blaudden +4 -0
    Add two more USE_CYGWIN ifdefs to mysqltest

ChangeSet@1.1616.2983.4, 2007-03-01 18:31:09+01:00, msvensson@pilot.blaudden +1 -0
  Fix bug in mtr.pl where slave wes using same query log file as master

  mysql-test/mysql-test-run.pl@1.8.20.6, 2007-03-01 18:31:09+01:00, msvensson@pilot.blaudden +1 -1
    Fix bug in mtr.pl where slave wes using same query log file as master

ChangeSet@1.1616.2983.3, 2007-03-01 18:30:29+01:00, msvensson@pilot.blaudden +1 -0
  Don't set the "is_windows" flag if using cygwin

  client/mysqltest.c@1.92.21.51, 2007-03-01 18:30:28+01:00, msvensson@pilot.blaudden +2 -0
    Don't set the "is_windows" flag if using cygwin

ChangeSet@1.2392.54.1, 2007-03-01 15:28:10+02:00, gkodinov@magare.gmz +1 -0
  Correctly recognize Intel Core2Duo Extreme
  in build.

  BUILD/check-cpu@1.19, 2007-03-01 15:28:09+02:00, gkodinov@magare.gmz +4 -0
    Correctly recognize Intel Core2Duo Extreme.

ChangeSet@1.1616.2969.24, 2007-03-01 11:41:29+01:00, msvensson@pilot.blaudden +1 -0
  MySQL versions before 5.0 still use cygwin, no need
  to convert path

  mysql-test/lib/mtr_misc.pl@1.5.1.7, 2007-03-01 11:41:29+01:00, msvensson@pilot.blaudden +6 -0
    MySQL versions before 5.0 still use cygwin, no need
    to convert path

ChangeSet@1.2392.52.1, 2007-03-01 10:40:48+01:00, rafal@quant.(none) +2 -0
  Removing two more compilation warnings.

  sql/slave.cc@1.294, 2007-03-01 10:38:17+01:00, rafal@quant.(none) +2 -0
    Guard declaration of variable to avoid "unused variable" warning.

  sql/sql_repl.cc@1.155.1.3, 2007-03-01 10:38:17+01:00, rafal@quant.(none) +2 -0
    Guard declaration of variable to avoid "unused variable" warning.

ChangeSet@1.2392.47.3, 2007-03-01 11:28:33+02:00, jani@a88-113-38-195.elisa-laajakaista.fi +2 -0
  Fixed compiler warnings.

  client/mysqltest.c@1.279, 2007-03-01 11:28:30+02:00, jani@a88-113-38-195.elisa-laajakaista.fi +1 -1
    Fixed a compiler warning.

  support-files/compiler_warnings.supp@1.8, 2007-03-01 11:28:30+02:00, jani@a88-113-38-195.elisa-laajakaista.fi +2 -0
    Suppressed compiler warnings on Win 64.

ChangeSet@1.2392.47.2, 2007-03-01 10:52:25+02:00, jani@a88-113-38-195.elisa-laajakaista.fi +2 -0
  Disabled compiler warnings.

  sql/ha_archive.cc@1.83, 2007-03-01 10:52:22+02:00, jani@a88-113-38-195.elisa-laajakaista.fi +3 -1
    Fixed a warning from unused computed value. This block is
    only used in debug mode and changes nothing.

  support-files/compiler_warnings.supp@1.7, 2007-03-01 10:52:22+02:00, jani@a88-113-38-195.elisa-laajakaista.fi +1 -0
    Disabled a warning from BDB.

ChangeSet@1.2392.48.6, 2007-03-01 12:26:07+04:00, bar@mysql.com +2 -0
  Fix for wrong replace command.

  mysql-test/r/mysqlbinlog.result@1.31, 2007-03-01 12:26:05+04:00, bar@mysql.com +7 -7
    Fix for wrong replace command.

  mysql-test/t/mysqlbinlog.test@1.42, 2007-03-01 12:26:05+04:00, bar@mysql.com +1 -1
    Fix for wrong replace command.

ChangeSet@1.2392.51.1, 2007-03-01 11:52:25+04:00, bar@mysql.com +2 -0
  Renaming recenly added test case, because of name conflict
  when merging into 5.1.

  mysql-test/r/rpl_loaddata_charset.result@1.2, 2007-03-01 11:50:27+04:00, bar@mysql.com +0 -0
    Rename: mysql-test/r/rpl_loaddata2.result -> mysql-test/r/rpl_loaddata_charset.result

  mysql-test/t/rpl_loaddata_charset.test@1.2, 2007-03-01 11:50:13+04:00, bar@mysql.com +0 -0
    Rename: mysql-test/t/rpl_loaddata2.test -> mysql-test/t/rpl_loaddata_charset.test

ChangeSet@1.2392.50.1, 2007-03-01 08:41:13+01:00, rafal@quant.(none) +4 -0
  Fixes of compilation warnings and errors.

  sql/mysql_priv.h@1.432.1.1, 2007-03-01 08:41:12+01:00, rafal@quant.(none) +1 -1
    Removing compiler warning "NULL used in arithmetic"

  sql/mysqld.cc@1.592, 2007-03-01 08:41:12+01:00, rafal@quant.(none) +1 -1
    First argument to WARN_DEPRECATED is supposed to be a pointer (to THD structure)

  sql/sql_insert.cc@1.211.9.1, 2007-03-01 08:41:12+01:00, rafal@quant.(none) +2 -0
    Removing compiler warning "unused variable". Apparently query is not used when compiling libmysqld.

  sql/sql_yacc.yy@1.502.2.1, 2007-03-01 08:41:12+01:00, rafal@quant.(none) +1 -0
    Removing compiler error "Macro already defined"

ChangeSet@1.2392.48.2, 2007-03-01 11:23:12+04:00, bar@mysql.com +2 -0
  Additional fix for bug N 15126
  Replacing local directory.

  mysql-test/r/mysqlbinlog.result@1.30, 2007-03-01 11:23:09+04:00, bar@mysql.com +7 -7
    Additional fix for bug N 15126

  mysql-test/t/mysqlbinlog.test@1.41, 2007-03-01 11:23:09+04:00, bar@mysql.com +1 -0
    Additional fix for bug N 15126

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.2377.39.4, 2007-03-01 08:34:59+07:00, tomas@poseidon.mysql.com +2 -0
  ndb - rel5.1.16 NdbRecAttr print of blob length assumed uint64 aligned buffer
  ndb - 5.1.16 uint64 align for ndb_restore
  (backport)

  ndb/src/ndbapi/NdbRecAttr.cpp@1.27, 2007-03-01 08:34:52+07:00, tomas@poseidon.mysql.com +19 -19
     ndb - rel5.1.16 NdbRecAttr print of blob length assumed uint64 aligned buffer
    (backport)

  ndb/tools/restore/Restore.cpp@1.29, 2007-03-01 08:34:52+07:00, tomas@poseidon.mysql.com +6 -1
     ndb - 5.1.16 uint64 align for ndb_restore
    (backport)

ChangeSet@1.1346.891.8, 2007-02-28 22:30:50+01:00, kent@mysql.com +1 -0
  Makefile.am:
    EXCEPTIONS-CLIENT is now static part of repository

  Docs/Makefile.am@1.38.1.18, 2007-02-28 22:30:09+01:00, kent@mysql.com +1 -1
    EXCEPTIONS-CLIENT is now static part of repository

ChangeSet@1.1346.891.7, 2007-02-28 22:09:09+01:00, kent@mysql.com +2 -0
  Makefile.am:
    EXCEPTIONS-CLIENT is now static part of repository
  EXCEPTIONS-CLIENT:
    BitKeeper file /home/kent/bk/tmp/mysql-4.0/EXCEPTIONS-CLIENT

  Docs/Makefile.am@1.38.1.17, 2007-02-28 22:07:29+01:00, kent@mysql.com +0 -3
    EXCEPTIONS-CLIENT is now static part of repository

  EXCEPTIONS-CLIENT@1.1, 2007-02-28 21:54:33+01:00, kent@mysql.com +117 -0
    BitKeeper file /home/kent/bk/tmp/mysql-4.0/EXCEPTIONS-CLIENT

  EXCEPTIONS-CLIENT@1.0, 2007-02-28 21:54:33+01:00, kent@mysql.com +0 -0

ChangeSet@1.2392.47.1, 2007-02-28 22:23:35+02:00, jani@ua141d10.elisa.omakaista.fi +12 -0
  Fixed compiler warnings.

  client/mysql_upgrade.c@1.18, 2007-02-28 22:23:33+02:00, jani@ua141d10.elisa.omakaista.fi +20 -9
    Fixed problem with mysql_upgrade being dependent
    on local my.cnf files and problem with memory not being freed.

  client/mysqltest.c@1.278, 2007-02-28 22:23:33+02:00, jani@ua141d10.elisa.omakaista.fi +1 -1
    Changed type to avoid warning.

  cmd-line-utils/readline/xmalloc.c@1.9, 2007-02-28 22:23:33+02:00, jani@ua141d10.elisa.omakaista.fi +3 -4
    Fix to avoid warning.

  include/my_dbug.h@1.21.1.1, 2007-02-28 22:23:33+02:00, jani@ua141d10.elisa.omakaista.fi +2 -0
    To disable parts from code in non-debug more.

  sql/field.cc@1.339.1.1, 2007-02-28 22:23:33+02:00, jani@ua141d10.elisa.omakaista.fi +3 -3
    Fixed warning.

  sql/ha_archive.cc@1.82, 2007-02-28 22:23:33+02:00, jani@ua141d10.elisa.omakaista.fi +1 -1
    Fixed warning.

  sql/ha_berkeley.cc@1.167, 2007-02-28 22:23:33+02:00, jani@ua141d10.elisa.omakaista.fi +3 -3
    Added casts to avoid warnings.

  sql/ha_ndbcluster.cc@1.299.1.1, 2007-02-28 22:23:33+02:00, jani@ua141d10.elisa.omakaista.fi +22 -7
    Fixed warnings.

  sql/log.cc@1.202.1.1, 2007-02-28 22:23:33+02:00, jani@ua141d10.elisa.omakaista.fi +2 -2
    Added casts to avoid warnings.

  sql/slave.cc@1.291.1.1, 2007-02-28 22:23:33+02:00, jani@ua141d10.elisa.omakaista.fi +2 -0
    Avoid warning.

  sql/sql_repl.cc@1.155.3.1, 2007-02-28 22:23:33+02:00, jani@ua141d10.elisa.omakaista.fi +2 -0
    Avoid warning.

  support-files/compiler_warnings.supp@1.6, 2007-02-28 22:23:33+02:00, jani@ua141d10.elisa.omakaista.fi +53 -3
    Added disabled warnings to compiler_warnings.supp file.
    These are backported mainly from 5.1 suppress file, but there
    are some additional new ones.

ChangeSet@1.2392.46.1, 2007-02-28 21:05:39+01:00, msvensson@pilot.blaudden +1 -0
  Bug #25074 mysql_upgrade test can't give consistent results
   - Tell the programs executed by mysql_upgrade to only read
    from the defaults file generated by msyql_upgrade
   - Fix memory leaks

  client/mysql_upgrade.c@1.14.1.4, 2007-02-28 21:05:38+01:00, msvensson@pilot.blaudden +65 -55
    - Always generate defaults file used for the programs executed
      by mysql_upgrade.
    - Set the executed programs to read options _only_ from the
      generated defaults file 
    - Add DBUG printouts
    - Add comments
    - Fix memory leaks
    - Change one 'my_delete'(delete a file) to 'my_free'(free memory)
    - Free memory allocated by 'load_default'

ChangeSet@1.2392.1.63, 2007-02-28 20:44:49+01:00, msvensson@pilot.blaudden +2 -0
  Bug #20166 mysql-test-run.pl does not test system privilege tables creation
   - No .sql files in mysql-test/lib/ anymore, don't copy them

  scripts/make_binary_distribution.sh@1.120.1.1, 2007-02-28 20:44:48+01:00, msvensson@pilot.blaudden +0 -1
    No need to copy mysql-test/lib/*.sql there are no sql files there anymore

  scripts/make_win_bin_dist@1.6, 2007-02-28 20:44:48+01:00, msvensson@pilot.blaudden +0 -1
    No need to copy mysql-test/lib/*.sql there are no sql files there anymore

ChangeSet@1.1616.2981.1, 2007-02-28 16:37:50+01:00, msvensson@pilot.blaudden +1 -0
  Bug#24878 mysql server doesn't log incident time in "mysqld got signal 11" error messages
   - Add printout of current time when mysqld is killed by an
     unhandled signal

  sql/mysqld.cc@1.356.115.1, 2007-02-28 16:37:50+01:00, msvensson@pilot.blaudden +10 -1
    Add printout of current time before the "mysqld got signal %d" message
    Hopefully we don't crash in the calls to 'time' or 'localtime_r'
    but if that should start to happen we can move the printout of
    time further down. At least it's now below the check for segfault
    inside of segfault handler. 

ChangeSet@1.2392.45.1, 2007-02-28 18:34:35+04:00, svoj@mysql.com +3 -0
  BUG#26238 - inserted delayed always inserts 0 for BIT columns
  
  INSERT DELAYED inserts garbage for BIT columns.
  
  When delayed thread clones TABLE object, it didn't adjusted bit_ptr
  to newly created record (though it correctly adjusts ptr and null_ptr).
  
  This is fixed by correctly adjusting bit_ptr when performing a clone.
  With this fix BIT values are stored correctly by INSERT DELAYED.

  mysql-test/r/delayed.result@1.13, 2007-02-28 18:34:33+04:00, svoj@mysql.com +7 -0
    A test case for BUG#26238.

  mysql-test/t/delayed.test@1.17, 2007-02-28 18:34:33+04:00, svoj@mysql.com +8 -0
    A test case for BUG#26238.

  sql/field.h@1.192.1.9, 2007-02-28 18:34:34+04:00, svoj@mysql.com +6 -1
    Added move_field() to Field_bit class. When moving a field, adjust
    bit_ptr also, which is specific to Field_bit class.

ChangeSet@1.2392.1.60, 2007-02-28 15:15:38+01:00, msvensson@pilot.blaudden +2 -0
  Bug#20166 mysql-test-run.pl does not test system privilege tables creation
   - Null merge 4.1 patch

  mysql-test/Makefile.am@1.88, 2007-02-28 15:15:36+01:00, msvensson@pilot.blaudden +1 -6
    Null merge to 4.1 patch

  scripts/Makefile.am@1.58, 2007-02-28 15:15:36+01:00, msvensson@pilot.blaudden +0 -1
    No need to clean mysql_create_system_tablesa anyomre

ChangeSet@1.2392.39.6, 2007-02-28 18:13:23+04:00, bar@mysql.com +3 -0
  Additional test changes for
  Bug N 15126 character_set_database is not replicated (LOAD DATA INFILE need it)
  Positions of some binlog events were changed because of
  additional logging of @@collation_database.

  mysql-test/r/ctype_cp932_binlog.result@1.7, 2007-02-28 18:13:20+04:00, bar@mysql.com +9 -9
    Additional test changes for
    Bug N 15126 character_set_database is not replicated (LOAD DATA INFILE need it)
    Positions of some binlog events were changed because of
    additional logging of @@collation_database.

  mysql-test/r/ctype_cp932_notembedded.result@1.2, 2007-02-28 18:13:20+04:00, bar@mysql.com +3 -3
    Additional test changes for
    Bug N 15126 character_set_database is not replicated (LOAD DATA INFILE need it)
    Positions of some binlog events were changed because of
    additional logging of @@collation_database.

  mysql-test/t/ctype_cp932_binlog.test@1.4, 2007-02-28 18:13:20+04:00, bar@mysql.com +1 -1
    Additional test changes for
    Bug N 15126 character_set_database is not replicated (LOAD DATA INFILE need it)
    Positions of some binlog events were changed because of
    additional logging of @@collation_database.

ChangeSet@1.1616.2969.22, 2007-02-28 15:03:47+01:00, msvensson@pilot.blaudden +4 -0
  Bug#20166 mysql-test-run.pl does not test system privilege tables creation
   - Build lib/init-db.sql from the output of mysql_create_system_tables
   - Remove mysql-test/init_db.sql and mysql-test/lib/init_db.sql
   - Leave netware/init_db.sql until 5.0 where we should soon have possibility
     to test with mysql-test-run.pl

  BitKeeper/deleted/.del-init_db.sql@1.2.1.1, 2007-02-28 15:01:02+01:00, msvensson@pilot.blaudden +0 -0
    Delete: mysql-test/init_db.sql

  BitKeeper/deleted/.del-init_db.sql~a77d572c39d5a1f8@1.4.1.2, 2007-02-28 15:01:05+01:00, msvensson@pilot.blaudden +0 -0
    Delete: mysql-test/lib/init_db.sql

  BitKeeper/etc/ignore@1.153.1.88, 2007-02-28 15:03:46+01:00, msvensson@pilot.blaudden +1 -0
    Added mysql-test/lib/init_db.sql to the ignore list

  mysql-test/Makefile.am@1.39.1.21, 2007-02-28 15:03:46+01:00, msvensson@pilot.blaudden +6 -1
    Build lib/init_db.sql from the output of mysql_create_system_tables

ChangeSet@1.2392.39.5, 2007-02-28 17:32:18+04:00, bar@mysql.com +2 -0
  After merge fix

  mysql-test/r/mysqlbinlog.result@1.29, 2007-02-28 17:32:15+04:00, bar@mysql.com +0 -1
    After merge fix

  mysql-test/t/mysqlbinlog.test@1.40, 2007-02-28 17:32:15+04:00, bar@mysql.com +0 -2
    After merge fix

ChangeSet@1.2392.1.58, 2007-02-28 14:26:58+01:00, msvensson@pilot.blaudden +6 -0
  Bug#20166 mysql-test-run.pl does not test system privilege tables creation
   - Split out initial data in mysql_system_tables.sql to  it's own file
   - Use file from mysql_install_db and mysql-test-run

  mysql-test/mysql-test-run.pl@1.202, 2007-02-28 14:26:57+01:00, msvensson@pilot.blaudden +10 -4
    - Add mysql_system_tables_data.sql as part of the bootstrap
    - Remove the addition of pid to end of bootstrap.sql, now
      to file used for bootstrap will be $opt_vardir/tmp/bootstrap.sql
    - Improve error message descibing how to find cause of a
      failed bootstrap

  scripts/Makefile.am@1.57, 2007-02-28 14:26:57+01:00, msvensson@pilot.blaudden +9 -7
    - Rename mysql_fix_privileg_tables.sql.in to mysql_system_tables_fix.sql
    - Build mysql_fix_privilege_tables from mysql_system_tables.sql and
      mysql_system_tables_fix.sql
    - Add mysql_system_tables_fix.sql to EXTRA_DIST

  scripts/mysql_install_db.sh@1.71, 2007-02-28 14:26:57+01:00, msvensson@pilot.blaudden +11 -1
    - Use mysql_system_tables_data.sql file when bootstrapping
      mysql, it will contain initial data for MysQL system tables

  scripts/mysql_system_tables.sql@1.4, 2007-02-28 14:26:57+01:00, msvensson@pilot.blaudden +0 -10
    Move initial data for system tables to it's own file

  scripts/mysql_system_tables_data.sql@1.1, 2007-02-28 14:26:57+01:00, msvensson@pilot.blaudden +13 -0
    Move initial data for system tables to it's own file

  scripts/mysql_system_tables_data.sql@1.0, 2007-02-28 14:26:57+01:00, msvensson@pilot.blaudden +0 -0

  scripts/mysql_system_tables_fix.sql@1.44, 2007-02-28 11:37:38+01:00, msvensson@pilot.blaudden +0 -0
    Rename: scripts/mysql_fix_privilege_tables.sql.in -> scripts/mysql_system_tables_fix.sql

ChangeSet@1.2341.96.1, 2007-02-28 17:06:57+04:00, bar@mysql.com +11 -0
  Bug#15126 character_set_database is not replicated (LOAD DATA INFILE need it)
  This patch fixes problem that LOAD DATA could use different
  character sets when loading files on master and on slave sides:
  - Adding replication of thd->variables.collation_database
  - Adding optional character set clause into LOAD DATA
  
  Note, the second way, with explicit CHARACTER SET clause
  should be the recommended way to load data using an alternative
  character set.
  The old way, using "SET @@character_set_database=xxx" should be
  gradually depricated.

  mysql-test/r/mysqlbinlog.result@1.26.2.1, 2007-02-28 17:06:54+04:00, bar@mysql.com +58 -0
    Adding test case

  mysql-test/r/rpl_loaddata2.result@1.1, 2007-02-28 17:06:54+04:00, bar@mysql.com +37 -0
    New BitKeeper file ``mysql-test/r/rpl_loaddata2.result''

  mysql-test/r/rpl_loaddata2.result@1.0, 2007-02-28 17:06:54+04:00, bar@mysql.com +0 -0
    BitKeeper file /home/bar/mysql-5.0.b15126/mysql-test/r/rpl_loaddata2.result

  mysql-test/std_data/loaddata6.dat@1.1, 2007-02-28 17:06:54+04:00, bar@mysql.com +1 -0
    New BitKeeper file ``mysql-test/std_data/loaddata6.dat''

  mysql-test/std_data/loaddata6.dat@1.0, 2007-02-28 17:06:54+04:00, bar@mysql.com +0 -0
    BitKeeper file /home/bar/mysql-5.0.b15126/mysql-test/std_data/loaddata6.dat

  mysql-test/t/mysqlbinlog.test@1.36.3.1, 2007-02-28 17:06:54+04:00, bar@mysql.com +24 -0
    Adding test case

  mysql-test/t/rpl_loaddata2.test@1.1, 2007-02-28 17:06:55+04:00, bar@mysql.com +33 -0
    New BitKeeper file ``mysql-test/t/rpl_loaddata2.test''

  mysql-test/t/rpl_loaddata2.test@1.0, 2007-02-28 17:06:55+04:00, bar@mysql.com +0 -0
    BitKeeper file /home/bar/mysql-5.0.b15126/mysql-test/t/rpl_loaddata2.test

  sql/log_event.cc@1.223.1.2, 2007-02-28 17:06:54+04:00, bar@mysql.com +44 -4
    Adding logging of thd->variables.collation_database

  sql/log_event.h@1.130.1.2, 2007-02-28 17:06:54+04:00, bar@mysql.com +4 -1
    Adding declarations

  sql/sql_class.cc@1.256.6.1, 2007-02-28 17:06:54+04:00, bar@mysql.com +1 -0
    Exchange character set is null by default

  sql/sql_class.h@1.314.5.1, 2007-02-28 17:06:54+04:00, bar@mysql.com +1 -0
    Adding character set into sql_exchange

  sql/sql_load.cc@1.102.2.1, 2007-02-28 17:06:54+04:00, bar@mysql.com +2 -1
    - Using exchange character set (if it was specified in LOAD DATA syntax)
    - Using thd->variables.collation_database by default

  sql/sql_yacc.yy@1.498.8.1, 2007-02-28 17:06:54+04:00, bar@mysql.com +7 -0
    Adding optional character set clause into LOAD DATA syntax

ChangeSet@1.2392.19.12, 2007-02-28 16:03:38+03:00, kostja@bodhi.local +1 -0
  Add more comments to open_table and open_tables. No real changes.

  sql/sql_base.cc@1.360.6.1, 2007-02-28 16:03:35+03:00, kostja@bodhi.local +111 -5
    Add more comments to open_table and open_tables. No real changes.

ChangeSet@1.1616.2969.21, 2007-02-28 13:47:41+01:00, msvensson@pilot.blaudden +1 -0
  When using a --mem=<dir> the memdir must be removed to assure
  afresh start

  mysql-test/mysql-test-run.pl@1.8.20.5, 2007-02-28 13:47:40+01:00, msvensson@pilot.blaudden +10 -0
    When using a --mem=<dir> the memdir must be removed to assure
    afresh start

ChangeSet@1.2392.43.1, 2007-02-28 11:23:00+01:00, joerg@trift2. +1 -0
  A binary package should also contain the "mysqld-debug" server (backport from 5.1).

  scripts/make_binary_distribution.sh@1.121, 2007-02-28 11:22:57+01:00, joerg@trift2. +2 -1
    A binary package should also contain the "mysqld-debug" server (backport from 5.1).

ChangeSet@1.1616.2969.20, 2007-02-28 10:52:51+01:00, msvensson@pilot.blaudden +1 -0
  Bug#26416 mysql-test-run exits with "Hangup" when piped to grep
   - Thanks to Christian for the patch!

  mysql-test/lib/mtr_process.pl@1.15.1.18, 2007-02-28 10:52:50+01:00, msvensson@pilot.blaudden +2 -8
    Avoid printout of "Hangup" when script exits by using
    POSIX::kill

ChangeSet@1.1616.2969.19, 2007-02-28 10:37:32+01:00, msvensson@pilot.blaudden +1 -0
  Bug#26686 mysql-test-run.pl aborts when waitpid returns -1
   - Add error handling for waitpid returns -1 for "simple run of command"

  mysql-test/lib/mtr_process.pl@1.15.1.17, 2007-02-28 10:37:31+01:00, msvensson@pilot.blaudden +20 -9
    - Add error handling for waitpid returns -1
    when a simple command is run.
    - Add missing return
    - Add mtr_errors where the program should never come 
    - Remove an else to improve program readability
    - Change mtr_debug to mtr_warning for "Got EAGAIN from fork()..." 

ChangeSet@1.1616.2969.17, 2007-02-28 10:05:51+01:00, msvensson@pilot.blaudden +1 -0
  Use cygwin for --exec and --system in mysqltest for MySQL before 5.0

  client/mysqltest.c@1.92.21.49, 2007-02-28 10:05:50+01:00, msvensson@pilot.blaudden +5 -0
    Use cygwin for --exec and --system in mysqltest for MySQL before 5.0

ChangeSet@1.1616.2980.1, 2007-02-28 09:10:38+01:00, msvensson@pilot.blaudden +1 -0
  Bug#19410 Test 'kill' fails on Windows + SCO
  - Use "mysql_stmt_field_count" to determine if there is a need to
  call "mysql_stmt_store_result"

  client/mysqltest.c@1.92.26.1, 2007-02-28 09:10:37+01:00, msvensson@pilot.blaudden +2 -1
    Only call 'mysql_stmt_store_result' if 'mysql_stmt_field_count' is
    greater than 0 indicating that this query has a result set.
    This change is mainly since if mysql_stmt_store_result fails
    the value returned by mysql_stmt_field_count will be reset.

ChangeSet@1.2392.38.1, 2007-02-27 10:32:45-05:00, cbell@mysql_cab_desk. +1 -0
  BUG#20141 "User-defined variables are not replicated properly for 
            SF/Triggers in SBR mode."
  BUG#14914 "SP: Uses of session variables in routines are not always replicated"
  BUG#25167 "Dupl. usage of user-variables in trigger/function is not replicated
            correctly"
  
  This patch corrects a minor error in the previous patch for BUG#20141. This patch
  corrects an errant code change to sp_head.cc. The comments for the first patch follow:
  
  User-defined variables used inside of stored functions/triggers in
  statements which did not update tables directly were not replicated.
  We also had problems with replication of user-defined variables which
  were used in triggers (or stored functions called from table-updating
  statements) more than once.
  
  This patch addresses the first issue by enabling logging of all
  references to user-defined variables in triggers/stored functions
  and not only references from table-updating statements.
  
  The second issue stemmed from the fact that for user-defined
  variables used from triggers or stored functions called from
  table-updating statements we were writing binlog events for each
  reference instead of only one event for the first reference.
  This problem is already solved for stored functions called from
  non-updating statements with help of "event unioning" mechanism.
  So the patch simply extends this mechanism to the case affected.
  It also fixes small problem in this mechanism which caused wrong
  logging of references to user-variables in cases when non-updating
  statement called several stored functions which used the same
  variable and some of these function calls were omitted from binlog
  as they were not updating any tables.

  sql/sp_head.cc@1.234, 2007-02-27 10:32:40-05:00, cbell@mysql_cab_desk. +1 -1
    BUG#20141 "User-defined variables are not replicated properly for 
              SF/Triggers in SBR mode."
    
    This patch corrects a minor error in the previous patch for BUG#20141. The code:
    
    q= ::query_id; 
    
    was an errant line of code that was not intended to be in the patch. Instead, the
    correct line of code is:
    
    q= global_query_id;

ChangeSet@1.2392.1.57, 2007-02-27 15:28:19+01:00, msvensson@pilot.blaudden +1 -0
  Bug#23669 mysql.proc not created in default install
   - Remove DEFAULT values for blob's in mysql_system_tables.sql

  scripts/mysql_system_tables.sql@1.3, 2007-02-27 15:28:18+01:00, msvensson@pilot.blaudden +1 -1
    Remove attempt to set default value for blob columns since
    they can't have any. Depending on 'sql_mode' the default values
    has either been silently dropped or thrown an error as reported
    by the bug. 

ChangeSet@1.2392.37.1, 2007-02-27 14:18:12+01:00, msvensson@pilot.blaudden +2 -0
  Bug#26678 SSL tests fail on win64
   - Import a patch from yaSSL CVS that uses "word" instead
  of "unsigned long" in three function's that uses sizeof to find
  out the word size being used. NOTE! long is 32 bit also on 
  64 bit windows.

  extra/yassl/taocrypt/include/misc.hpp@1.17, 2007-02-27 12:05:12+01:00, msvensson@pilot.blaudden +3 -3
    Import patch yassl.diff

  extra/yassl/taocrypt/src/misc.cpp@1.20, 2007-02-27 12:05:13+01:00, msvensson@pilot.blaudden +3 -3
    Import patch yassl.diff

ChangeSet@1.2392.22.6, 2007-02-27 14:10:27+01:00, msvensson@pilot.blaudden +1 -0
  Bug#20166 mysql-test-run.pl does not test system privilege tables creation
   - Escape undercore character in mysql.db to only allow
    access test_% and not test%

  scripts/mysql_system_tables.sql@1.2, 2007-02-27 14:10:26+01:00, msvensson@pilot.blaudden +1 -1
    underscore is a wildcard character so it need to be
    expaed to only match one _

ChangeSet@1.2392.35.2, 2007-02-27 12:37:17+04:00, gluh@mysql.com +1 -0
  removed unused variable

  sql/sql_select.cc@1.495, 2007-02-27 12:37:15+04:00, gluh@mysql.com +0 -1
    removed unused variable

ChangeSet@1.2392.36.1, 2007-02-27 11:01:58+04:00, ramil@mysql.com +2 -0
  Fix for bug #25834: Test failure in "func_group"
  
  Round the results of std() for some calls with double arguments
  to avoid double math precision problems.

  mysql-test/r/func_group.result@1.59, 2007-02-27 11:01:57+04:00, ramil@mysql.com +15 -15
    Fix for bug #25834: Test failure in "func_group"
    
    Round the results of std() for some calls with double arguments
    to avoid double math precision problems.

  mysql-test/t/func_group.test@1.54, 2007-02-27 11:01:57+04:00, ramil@mysql.com +3 -3
    Fix for bug #25834: Test failure in "func_group"
    
    Round the results of std() for some calls with double arguments
    to avoid double math precision problems.

ChangeSet@1.1616.2877.53, 2007-02-26 20:35:28+01:00, gbichot@dl145h.mysql.com +1 -0
  Fix for BUG#26050 "LOAD DATA INFILE breaks ACID"; the ok must be sent
  to the client only after the binlog write and engine commit.
  No testcase for this bug, as to reproduce it, we need to "kill -9" mysqld,
  which we cannot do in the testsuite. But, I tested by hand.

  sql/sql_load.cc@1.46.3.43, 2007-02-26 20:33:55+01:00, gbichot@dl145h.mysql.com +3 -1
    D in ACID means that once the client got the ok from the server, the data
    is durable on disk. Implies that the ok must be sent after the binlog write
    and after the engine commit, not before.

ChangeSet@1.1616.2969.16, 2007-02-26 14:52:51+01:00, msvensson@pilot.blaudden +1 -0
  Only allow a version number to be read from "/etc/debian_version"

  mysql-test/mysql-test-run.pl@1.8.20.4, 2007-02-26 14:52:50+01:00, msvensson@pilot.blaudden +1 -1
    Only allow a version number to be read from "/etc/debian_version"

ChangeSet@1.2392.22.5, 2007-02-26 14:49:41+01:00, msvensson@pilot.blaudden +1 -0
  Remove another spurious "

  scripts/mysql_fix_privilege_tables.sql.in@1.43, 2007-02-26 14:49:40+01:00, msvensson@pilot.blaudden +1 -1
    Remove another spurious "

ChangeSet@1.2392.22.4, 2007-02-26 14:48:41+01:00, msvensson@pilot.blaudden +1 -0
  Remove spurious "

  scripts/mysql_fix_privilege_tables.sql.in@1.42, 2007-02-26 14:48:40+01:00, msvensson@pilot.blaudden +1 -1
    Remove spurious "

ChangeSet@1.2341.95.1, 2007-02-26 15:25:43+04:00, bar@mysql.com +5 -0
  Bug#24478 DROP TRIGGER is not caught by replicate-*-table filters
  Problem: DROP TRIGGER was not properly handled in combination
  with slave filters, which made replication stop
  Fix: loading table name before checking slave filters when
  dropping a trigger.

  mysql-test/r/rpl_replicate_do.result@1.34, 2007-02-26 15:25:40+04:00, bar@mysql.com +34 -0
    Adding test case

  mysql-test/t/rpl_replicate_do.test@1.26, 2007-02-26 15:25:40+04:00, bar@mysql.com +32 -0
    Adding test case

  sql/sql_parse.cc@1.590.12.1, 2007-02-26 15:25:40+04:00, bar@mysql.com +25 -0
    Loading table name when dropping a trigger
    before checking slave filtering rules.

  sql/sql_trigger.cc@1.60.2.1, 2007-02-26 15:25:40+04:00, bar@mysql.com +1 -5
    Making add_table_for_trigger() public

  sql/sql_trigger.h@1.22.2.1, 2007-02-26 15:25:40+04:00, bar@mysql.com +4 -0
    Making add_table_for_trigger() public

ChangeSet@1.2392.22.3, 2007-02-26 11:49:24+01:00, msvensson@pilot.blaudden +31 -0
  Bug#20166 mysql-test-run.pl does not test system privilege tables creation
   - Use mysql_system_tables.sql to create MySQL system tables in
     all places where we create them(mysql_install_db, mysql-test-run-pl
     and mysql_fix_privilege_tables.sql)

  BitKeeper/deleted/.del-init_db.sql@1.5, 2007-02-26 11:48:43+01:00, msvensson@pilot.blaudden +0 -0
    Rename: mysql-test/init_db.sql -> BitKeeper/deleted/.del-init_db.sql

  BitKeeper/deleted/.del-init_db.sql~a77d572c39d5a1f8@1.15, 2007-02-26 11:48:43+01:00, msvensson@pilot.blaudden +0 -0
    Rename: mysql-test/lib/init_db.sql -> BitKeeper/deleted/.del-init_db.sql~a77d572c39d5a1f8

  BitKeeper/deleted/.del-mysql_create_system_tables.sh@1.31, 2007-02-26 11:48:43+01:00, msvensson@pilot.blaudden +0 -0
    Rename: scripts/mysql_create_system_tables.sh -> BitKeeper/deleted/.del-mysql_create_system_tables.sh

  BitKeeper/etc/ignore@1.241.1.1, 2007-02-26 11:49:23+01:00, msvensson@pilot.blaudden +1 -0
    Added scripts/mysql_fix_privilege_tables.sql to the ignore list

  mysql-test/Makefile.am@1.86, 2007-02-26 11:49:23+01:00, msvensson@pilot.blaudden +0 -2
    lib/init_db.sql has been removed

  mysql-test/include/add_anonymous_users.inc@1.1, 2007-02-26 11:49:23+01:00, msvensson@pilot.blaudden +7 -0
    New BitKeeper file ``mysql-test/include/add_anonymous_users.inc''

  mysql-test/include/add_anonymous_users.inc@1.0, 2007-02-26 11:49:23+01:00, msvensson@pilot.blaudden +0 -0

  mysql-test/include/delete_anonymous_users.inc@1.1, 2007-02-26 11:49:23+01:00, msvensson@pilot.blaudden +5 -0
    New BitKeeper file ``mysql-test/include/delete_anonymous_users.inc''

  mysql-test/include/delete_anonymous_users.inc@1.0, 2007-02-26 11:49:23+01:00, msvensson@pilot.blaudden +0 -0

  mysql-test/mysql-test-run.pl@1.200, 2007-02-26 11:49:23+01:00, msvensson@pilot.blaudden +37 -34
    - Build var/tmp/bootstrap.sql from mysql_system_tables.sql,
    mysql_test_data_timezone.sql and fill_help_tables.sql and use
    it when bootsraping the system tables to use during test. 

  mysql-test/r/create.result@1.124, 2007-02-26 11:49:23+01:00, msvensson@pilot.blaudden +2 -0
    Update result file

  mysql-test/r/derived.result@1.58, 2007-02-26 11:49:23+01:00, msvensson@pilot.blaudden +2 -0
    Update result file

  mysql-test/r/join.result@1.41, 2007-02-26 11:49:23+01:00, msvensson@pilot.blaudden +1 -1
    Update result file

  mysql-test/r/mysql_upgrade.result@1.2, 2007-02-26 11:49:23+01:00, msvensson@pilot.blaudden +0 -30
    Update result file

  mysql-test/r/sp-security.result@1.32, 2007-02-26 11:49:23+01:00, msvensson@pilot.blaudden +3 -3
    Update result file

  mysql-test/t/create.test@1.84, 2007-02-26 11:49:23+01:00, msvensson@pilot.blaudden +3 -1
    Add user mysqltest_1 before trying to connect as that user - no
    anon users by default anymore

  mysql-test/t/derived.test@1.53, 2007-02-26 11:49:23+01:00, msvensson@pilot.blaudden +6 -1
    Add user mysqltest_1 before trying to connect as that user - no
    anon users by default anymore

  mysql-test/t/grant2.test@1.38, 2007-02-26 11:49:23+01:00, msvensson@pilot.blaudden +4 -0
    Add anonymous users for part of thes that need it.

  mysql-test/t/grant_cache.test@1.18, 2007-02-26 11:49:23+01:00, msvensson@pilot.blaudden +6 -0
    Add anonymous users for part of thes that need it.

  mysql-test/t/init_connect.test@1.9, 2007-02-26 11:49:23+01:00, msvensson@pilot.blaudden +4 -0
    Add anonymous users for part of thes that need it.

  mysql-test/t/lock_multi.test@1.22, 2007-02-26 11:49:23+01:00, msvensson@pilot.blaudden +6 -0
    Add anonymous users for part of thes that need it.

  mysql-test/t/ndb_basic.test@1.38, 2007-02-26 11:49:23+01:00, msvensson@pilot.blaudden +3 -3
    Connect as "root", blank user will take currently logged in
    username

  mysql-test/t/ndb_index_ordered.test@1.28, 2007-02-26 11:49:23+01:00, msvensson@pilot.blaudden +2 -2
    Connect as "root", blank user will take currently logged in
    username

  mysql-test/t/ndb_multi.test@1.11, 2007-02-26 11:49:23+01:00, msvensson@pilot.blaudden +2 -2
    Connect as "root", blank user will take currently logged in
    username

  mysql-test/t/overflow.test@1.9, 2007-02-26 11:49:23+01:00, msvensson@pilot.blaudden +1 -1
    Connect as root - no anonymous users by default anymore

  mysql-test/t/rpl_temporary.test@1.22.1.1, 2007-02-26 11:49:23+01:00, msvensson@pilot.blaudden +8 -2
    Add anonymous users for the test

  mysql-test/t/xa.test@1.8, 2007-02-26 11:49:23+01:00, msvensson@pilot.blaudden +1 -1
    Connect as "root", blank user wil pick currently logged in user

  scripts/Makefile.am@1.56, 2007-02-26 11:49:23+01:00, msvensson@pilot.blaudden +16 -6
    Remove mysql_create_system_tables.sh
    Add mysql_system_tables.sql and mysql_test_data_timezone.sql
    Build mysql_fix_privilege_tables.sql from mysql_system_tables.sql
    and mysql_fix_privilege_tables.sql.in

  scripts/mysql_fix_privilege_tables.sh@1.38, 2007-02-26 11:49:23+01:00, msvensson@pilot.blaudden +1 -5
    Update message describing what the script does

  scripts/mysql_install_db.sh@1.70, 2007-02-26 11:49:23+01:00, msvensson@pilot.blaudden +120 -81
    Use mysql_system_tables.sql to create the MySQL system tables
    Update comments and indentation
    Add more descriptive comments about --windows switch
    Reduce number of hardcoded names for the SQL files the script
    looks for

  scripts/mysql_system_tables.sql@1.1, 2007-02-26 11:49:23+01:00, msvensson@pilot.blaudden +65 -0
    New BitKeeper file ``scripts/mysql_system_tables.sql''

  scripts/mysql_system_tables.sql@1.0, 2007-02-26 11:49:23+01:00, msvensson@pilot.blaudden +0 -0

  scripts/mysql_fix_privilege_tables.sql.in@1.41, 2007-02-26 11:49:23+01:00, msvensson@pilot.blaudden +43 -222
    Remove the part that creates system tables as that will be added to
    mysql_fix_privileg_tables.sql from mysql_system_tables.sql
    Change all comments to use # 

  scripts/mysql_fix_privilege_tables.sql.in@1.40, 2007-02-26 11:48:43+01:00, msvensson@pilot.blaudden +0 -0
    Rename: scripts/mysql_fix_privilege_tables.sql -> scripts/mysql_fix_privilege_tables.sql.in

  scripts/mysql_test_data_timezone.sql@1.1, 2007-02-26 11:49:23+01:00, msvensson@pilot.blaudden +5 -0
    New BitKeeper file ``scripts/mysql_test_data_timezone.sql''

  scripts/mysql_test_data_timezone.sql@1.0, 2007-02-26 11:49:23+01:00, msvensson@pilot.blaudden +0 -0

ChangeSet@1.2392.1.53, 2007-02-26 09:24:03+01:00, msvensson@pilot.blaudden +1 -0
  Use binary file mode when writing the modified .TRG file to avoid CR/LF's being added on windows

  mysql-test/t/trigger-grant.test@1.9, 2007-02-26 09:24:02+01:00, msvensson@pilot.blaudden +2 -0
    Use binary file mode when writing the modified .TRG file to avoid CR/LF's being added on windows

ChangeSet@1.2392.1.52, 2007-02-26 09:16:22+01:00, msvensson@pilot.blaudden +2 -0
  Workaround non portable use of "grep" and "cut" by loading the whole processlist
  into temporary table and selecting the correct row with SQL

  mysql-test/include/get_binlog_dump_thread_id.inc@1.4, 2007-02-26 09:16:21+01:00, msvensson@pilot.blaudden +16 -3
    Workaround non portable use of "grep" and "cut" by loading the whole processlist
    into temporary table and selecting the correct row with SQL

  mysql-test/r/rpl_temporary.result@1.27, 2007-02-26 09:16:21+01:00, msvensson@pilot.blaudden +10 -1
    Workaround non portable use of "grep" and "cut" by loading the whole processlist
    into temporary table and selecting the correct row with SQL

ChangeSet@1.2392.17.8, 2007-02-26 08:11:10+01:00, knielsen@ymer.(none) +1 -0
  Compiler warning suppression fix: Add missing file to 'make dist'.

  support-files/Makefile.am@1.35, 2007-02-26 08:11:07+01:00, knielsen@ymer.(none) +2 -1
    Add missing file to 'make dist'.

ChangeSet@1.2392.33.3, 2007-02-26 09:01:43+03:00, evgen@sunlight.local +2 -0
  item.cc, item.h:
    Post fix for bug#23800.

  sql/item.cc@1.245.9.4, 2007-02-26 09:00:57+03:00, evgen@sunlight.local +1 -0
    Post fix for bug#23800.

  sql/item.h@1.213.1.11, 2007-02-26 09:00:36+03:00, evgen@sunlight.local +0 -1
    Post fix for bug#23800.

ChangeSet@1.2392.33.2, 2007-02-25 23:02:11+03:00, evgen@sunlight.local +1 -0
  item.h:
    Post fix for bug#23800.
    Copy the table name of an Item_outer_ref to the conventional memory.

  sql/item.h@1.213.1.10, 2007-02-25 23:01:05+03:00, evgen@sunlight.local +1 -0
    Post fix for bug#23800.
    Copy the table name of an Item_outer_ref to the conventional memory.

ChangeSet@1.2392.34.3, 2007-02-25 00:31:26+01:00, lars@mysql.com +1 -0
  log_on needed also in embedded server

  sql/sql_insert.cc@1.211.1.7, 2007-02-25 00:31:24+01:00, lars@mysql.com +0 -2
    log_on needed also in embedded server

ChangeSet@1.2392.32.1, 2007-02-24 23:04:15+03:00, evgen@moonbone.local +4 -0
  item.cc:
    Post fix for bug#23800.
    The Item_field constructor now increases the select_n_where_fields counter.
  sql_yacc.yy:
    Post fix for bug#23800.
    Take into account fields that might be added by subselects.
  sql_lex.h:
    Post fix for bug#23800.
    Added the select_n_where_fields variable to the st_select_lex class.
  sql_lex.cc:
    Post fix for bug#23800.
    Initialization of the select_n_where_fields variable.

  sql/item.cc@1.245.9.3, 2007-02-24 23:00:46+03:00, evgen@moonbone.local +3 -0
    Post fix for bug#23800.
    The Item_field constructor now increases the select_n_where_fields counter.

  sql/sql_lex.cc@1.209.3.2, 2007-02-24 22:55:10+03:00, evgen@moonbone.local +2 -0
    Post fix for bug#23800.
    Initialization of the select_n_where_fields variable.

  sql/sql_lex.h@1.233.7.2, 2007-02-24 22:58:14+03:00, evgen@moonbone.local +5 -0
    Post fix for bug#23800.
    Added the select_n_where_fields variable to the st_select_lex class.

  sql/sql_yacc.yy@1.498.7.2, 2007-02-24 23:02:49+03:00, evgen@moonbone.local +6 -0
    Post fix for bug#23800.
    Take into account fields that might be added by subselects.

ChangeSet@1.2392.19.11, 2007-02-24 13:18:09+03:00, anozdrin@booka.opbmk +1 -0
  Fix for BUG#22511: IM does not remove angel-pid-file on clean shutdown

  server-tools/instance-manager/mysqlmanager.cc@1.21, 2007-02-24 13:18:06+03:00, anozdrin@booka.opbmk +4 -0
    Delete IM-angel pid file on exit.

ChangeSet@1.2392.19.10, 2007-02-24 13:12:20+03:00, anozdrin@booka.opbmk +4 -0
  IM test suite fix.
  
  Log messages from shell-scripts were put to var/log/<test id>.log
  file. Now, this file is used by mysql-test-run.pl. So, move log
  messages to var/log/<test id>.script.log.

  mysql-test/t/kill_n_check.sh@1.6, 2007-02-24 13:12:18+03:00, anozdrin@booka.opbmk +1 -1
    Log messages from shell-scripts were put to var/log/<test id>.log
    file. Now, this file is used by mysql-test-run.pl. So, move log
    messages to var/log/<test id>.script.log.

  mysql-test/t/log.sh@1.3, 2007-02-24 13:12:18+03:00, anozdrin@booka.opbmk +1 -1
    Log messages from shell-scripts were put to var/log/<test id>.log
    file. Now, this file is used by mysql-test-run.pl. So, move log
    messages to var/log/<test id>.script.log.

  mysql-test/t/wait_for_process.sh@1.3, 2007-02-24 13:12:18+03:00, anozdrin@booka.opbmk +1 -1
    Log messages from shell-scripts were put to var/log/<test id>.log
    file. Now, this file is used by mysql-test-run.pl. So, move log
    messages to var/log/<test id>.script.log.

  mysql-test/t/wait_for_socket.sh@1.4, 2007-02-24 13:12:18+03:00, anozdrin@booka.opbmk +1 -1
    Log messages from shell-scripts were put to var/log/<test id>.log
    file. Now, this file is used by mysql-test-run.pl. So, move log
    messages to var/log/<test id>.script.log.

ChangeSet@1.2392.19.9, 2007-02-24 13:10:04+03:00, anozdrin@booka.opbmk +2 -0
  Fix shutdown delay option name according to The Manual.

  mysql-test/mysql-test-run.pl@1.196.2.3, 2007-02-24 13:09:58+03:00, anozdrin@booka.opbmk +1 -1
    Fix shutdown delay option name according to The Manual.

  server-tools/instance-manager/instance_options.cc@1.32.1.2, 2007-02-24 13:09:58+03:00, anozdrin@booka.opbmk +1 -1
    Fix shutdown delay option name according to The Manual.

ChangeSet@1.2392.1.51, 2007-02-24 08:18:57+01:00, msvensson@pilot.blaudden +1 -0
  Replace non portable system commmands in trigger-grant

  mysql-test/t/trigger-grant.test@1.8, 2007-02-24 08:18:56+01:00, msvensson@pilot.blaudden +13 -3
    Replace non portable system commmands in trigger-grant

ChangeSet@1.2392.19.8, 2007-02-23 21:51:33+03:00, anozdrin@alik.opbmk +1 -0
  Fix mysql-test-run.pl: IM in 5.0 uses old incorrect
  'shutdown_delay' option name.

  mysql-test/mysql-test-run.pl@1.196.2.2, 2007-02-23 21:51:31+03:00, anozdrin@alik.opbmk +1 -1
    IM in 5.0 uses old incorrect 'shutdown_delay' option name.

ChangeSet@1.2392.19.7, 2007-02-23 21:13:21+03:00, anozdrin@alik.opbmk +1 -0
  Fix result file.

  mysql-test/r/im_daemon_life_cycle.result@1.10, 2007-02-23 21:13:20+03:00, anozdrin@alik.opbmk +1 -1
    Fix result file.

ChangeSet@1.2341.93.1, 2007-02-23 12:58:56-05:00, cbell@mysql_cab_desk. +7 -0
  BUG#20141 "User-defined variables are not replicated properly for SF/
             Triggers in SBR mode."
  BUG#14914 "SP: Uses of session variables in routines are not always
             replicated"
  BUG#25167 "Dupl. usage of user-variables in trigger/function is not
             replicated correctly"
  
  User-defined variables used inside of stored functions/triggers in
  statements which did not update tables directly were not replicated.
  We also had problems with replication of user-defined variables which
  were used in triggers (or stored functions called from table-updating
  statements) more than once.
  
  This patch addresses the first issue by enabling logging of all
  references to user-defined variables in triggers/stored functions
  and not only references from table-updating statements.
  
  The second issue stemmed from the fact that for user-defined
  variables used from triggers or stored functions called from
  table-updating statements we were writing binlog events for each
  reference instead of only one event for the first reference.
  This problem is already solved for stored functions called from
  non-updating statements with help of "event unioning" mechanism.
  So the patch simply extends this mechanism to the case affected.
  It also fixes small problem in this mechanism which caused wrong
  logging of references to user-variables in cases when non-updating
  statement called several stored functions which used the same
  variable and some of these function calls were omitted from binlog
  as they were not updating any tables.

  mysql-test/r/rpl_user_variables.result@1.18, 2007-02-23 12:57:17-05:00, Chuck@mysql_cab_desk. +176 -0
    BUG#20141 - User-defined variables are not replicated properly for SF/Triggers in SBR mode.
    This patch adds the correct results for execution of the added test procedures to the
    rpl_user_variables test.

  mysql-test/t/rpl_user_variables.test@1.15, 2007-02-23 12:57:18-05:00, Chuck@mysql_cab_desk. +300 -3
    BUG#20141 - User-defined variables are not replicated properly for SF/Triggers in SBR mode.
    This patch adds additional tests to the rpl_user_variables test that test many of the
    different ways user-defined variables can be required to be replicated.

  sql/item_func.cc@1.317.8.1, 2007-02-23 12:57:18-05:00, Chuck@mysql_cab_desk. +8 -1
    BUG#20141 - User-defined variables are not replicated properly for SF/Triggers in SBR mode.
    To properly log accesses to user-defined variables from stored functions/triggers,
    the get_var_with_binlog() method needs to log references to such variables even from 
    non-table-updating statements within them.

  sql/log.cc@1.200.3.1, 2007-02-23 12:57:19-05:00, Chuck@mysql_cab_desk. +2 -2
    BUG#20141 - User-defined variables are not replicated properly for SF/Triggers in SBR mode.
    This patch modifies the start_union_events method to accept the query id from a parameter.
    This allows callers to set the query_id to the id of the sub statement such as a trigger
    or stored function. Which permits the code to identify when a user defined variable has
    been used by the statement and this already present in THD::user_var_event.
    
    Note:
    The changes to sql_class.cc, sp_head.cc, and log.cc are designed to allow the proper 
    replication of access to user-defined variables under a special test case (the last case 
    shown in rpl_user_variables.test).

  sql/sp_head.cc@1.230.2.1, 2007-02-23 12:57:19-05:00, Chuck@mysql_cab_desk. +17 -1
    BUG#20141 - User-defined variables are not replicated properly for SF/Triggers in SBR mode.
    This patch modifies the code to allow for cases where events for function calls have
    a separate union for each event and thus cannot use the query_id of the caller as the
    start of the union. Thus, we use an artifically created query_id to set the start of 
    the events.
    
    Note:
    The changes to sql_class.cc, sp_head.cc, and log.cc are designed to allow the proper 
    replication of access to user-defined variables under a special test case (the last case 
    shown in rpl_user_variables.test).

  sql/sql_class.cc@1.256.5.1, 2007-02-23 12:57:20-05:00, Chuck@mysql_cab_desk. +7 -0
    BUG#20141 - User-defined variables are not replicated properly for SF/Triggers in SBR mode.
    This patch adds the query_id parameter to the calls to mysql_bin_log.start_union_events().
    
    Note:
    The changes to sql_class.cc, sp_head.cc, and log.cc are designed to allow the proper 
    replication of access to user-defined variables under a special test case (the last case 
    shown in rpl_user_variables.test).

  sql/sql_class.h@1.314.4.1, 2007-02-23 12:57:20-05:00, Chuck@mysql_cab_desk. +1 -1
    BUG#20141 - User-defined variables are not replicated properly for SF/Triggers in SBR mode.
    This patch adds the query_id parameter to the calls to mysql_bin_log.start_union_events().

ChangeSet@1.2392.19.6, 2007-02-23 20:49:01+03:00, anozdrin@alik.opbmk +2 -0
  Fix test for views with national characters,
  which accidentally got broken during the merge
  on 16-Feb-2007.

  mysql-test/r/view.result@1.194, 2007-02-23 20:49:00+03:00, anozdrin@alik.opbmk +10 -8
    Updated result file.

  mysql-test/t/view.test@1.179, 2007-02-23 20:49:00+03:00, anozdrin@alik.opbmk +8 -6
    Fix test for views with national characters,
    which accidentally got broken during the merge
    on 16-Feb-2007.
    
    Now view.test is in UTF8 character set,
    so SET NAMES is required.

ChangeSet@1.2392.19.5, 2007-02-23 20:24:32+03:00, anozdrin@alik.opbmk +2 -0
  BUG#24415: im_daemon_life_cycle.imtest fails
  
  Fix timeouts. Only test suite is changed.

  mysql-test/mysql-test-run.pl@1.196.2.1, 2007-02-23 20:24:30+03:00, anozdrin@alik.opbmk +1 -0
    Decrease MySQL server shutdown delay.
    Trasactional storage engines are not used here,
    so it should be enough.

  mysql-test/t/im_daemon_life_cycle.imtest@1.12, 2007-02-23 20:24:30+03:00, anozdrin@alik.opbmk +12 -7
    Increase wait-timeout.

ChangeSet@1.2392.1.50, 2007-02-23 18:05:32+01:00, msvensson@pilot.blaudden +1 -0
  Convert "system cp" to portable mysqltest commands

  mysql-test/t/type_varchar.test@1.12, 2007-02-23 18:05:31+01:00, msvensson@pilot.blaudden +3 -2
    Convert "system cp" to portable mysqltest commands

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.188.1.5, 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.1.48, 2007-02-23 17:33:11+01:00, msvensson@pilot.blaudden +2 -0
  Bug#26536 func_time failure on vm-win2003-64-b, occurs every time
   - Avoid overflow in sec_since_epoch by shifting the time
     back 2 days for times close to the maximum range of my_time_t
   - Improve comment about why we need my_time_t
   - Patch will also fix timezone2.test

  include/my_time.h@1.16.1.3, 2007-02-23 17:33:11+01:00, msvensson@pilot.blaudden +7 -1
    Improve comment for my_time_t, especially that we require
    it to be at least a 32bit unsigned type

  sql/tztime.cc@1.36.1.2, 2007-02-23 17:33:11+01:00, msvensson@pilot.blaudden +20 -3
    - Add assert in sec_since_epoch to guard it against broken down time
    values that would cause overflow in my_time_t on systems with 32 bit
    my_time_t
    - Avoid overflow in sec_since_epoch by "shifting" the broken down
    time back 2 days for times that are near the max value.c

ChangeSet@1.2392.24.5, 2007-02-23 16:51:13+01:00, msvensson@pilot.blaudden +1 -0
  Link comp_err with zlib

  extra/CMakeLists.txt@1.4, 2007-02-23 16:51:11+01:00, msvensson@pilot.blaudden +1 -1
    Link comp_err with zlib

ChangeSet@1.2341.92.1, 2007-02-23 15:32:51+01:00, gbichot@dl145h.mysql.com +2 -0
  the fix for BUG#24432
    "INSERT... ON DUPLICATE KEY UPDATE skips auto_increment values"
  didn't make it into 5.0.36 and 5.1.16,
  so we need to adjust the bug-detection-based-on-version-number code.
  Because the rpl tree has a too old version, rpl_insert_id cannot pass,
  so I disable it (like is already the case in 5.1-rpl for the same reason),
  and the repl team will re-enable it when they merge 5.0 and 5.1 into
  their trees (thus getting the right version number).

  mysql-test/t/disabled.def@1.39.1.1, 2007-02-23 15:26:32+01:00, gbichot@dl145h.mysql.com +1 -0
        rpl_insert_id tests statement-based replication of INSERT ON
        DUPLICATE KEY UPDATE. This type of INSERT had BUG#24432, which is
        fixed in 5.0.38; we made the slave detect if it is connected to a
        <5.0.38 master and if so refuse to replicate.
        The problem is that this 5.0-rpl tree, even though it will produce
        the 5.0.38 release, still has a 5.0.36 version in configure.in.
        Thus rpl_insert_id fails. So I disable it. As soon as the 5.0-rpl
        tree gets the changesets from the main 5.0, its version will change
        to 5.0.38 and so the repl team will re-enable the test.

  sql/slave.cc@1.286.6.2, 2007-02-23 15:28:39+01:00, gbichot@dl145h.mysql.com +2 -2
    the fix for BUG#24432 didn't make it into 5.0.36 and 5.1.16,
    so we need to adjust the bug-detection-based-on-version-number code.

ChangeSet@1.2392.30.1, 2007-02-23 10:28:50+01:00, msvensson@pilot.blaudden +3 -0
  Bug#25197 repeat function returns null when using table field directly as count
   - Return empty string also if count is unsigned and value is 0

  mysql-test/r/func_str.result@1.127, 2007-02-23 10:28:49+01:00, msvensson@pilot.blaudden +14 -0
    Update test result

  mysql-test/t/func_str.test@1.100, 2007-02-23 10:28:49+01:00, msvensson@pilot.blaudden +22 -0
    Add test case for using an unsigned value as count parameter
    for REPEAT

  sql/item_strfunc.cc@1.292.4.1, 2007-02-23 10:28:49+01:00, msvensson@pilot.blaudden +3 -1
    The repeat function should return the emptystring if
    count is unsigned and equal to zero or
    count is signed and less than or equal to zero

ChangeSet@1.2392.28.2, 2007-02-22 20:20:49+02:00, monty@mysql.com +2 -0
  Portability fix
  Suppress compiler warnings from bdb and (for the moment) warnings from ndb

  client/mysqltest.c@1.277, 2007-02-22 20:20:47+02:00, monty@mysql.com +1 -1
    Portability fix for windows (windows doesn't have mode_t)

  support-files/compiler_warnings.supp@1.5, 2007-02-22 20:20:48+02:00, monty@mysql.com +14 -0
    Suppress warnings from bdb and (for the moment) warnings from ndb

ChangeSet@1.2392.29.2, 2007-02-22 17:53:41+01:00, msvensson@pilot.blaudden +1 -0
  Bug#24617  	Typo in Czech translation

  sql/share/errmsg.txt@1.75.2.2, 2007-02-22 17:53:39+01:00, msvensson@pilot.blaudden +1 -1
    Add the missing "d"

ChangeSet@1.2392.29.1, 2007-02-22 16:41:51+01:00, msvensson@pilot.blaudden +3 -0
  Bug #26571  	Different format specifiers in errmsg.txt
  - Add check of format specifiers in error message strings
  - Update error message text accordingly to be equal between all translations

  extra/Makefile.am@1.38, 2007-02-22 16:41:49+01:00, msvensson@pilot.blaudden +2 -1
    comp_err uses my_cheksum, link with zlib

  extra/comp_err.c@1.25.2.1, 2007-02-22 16:41:49+01:00, msvensson@pilot.blaudden +119 -0
    Add check of format specifiers in error message strings

  sql/share/errmsg.txt@1.75.2.1, 2007-02-22 16:41:49+01:00, msvensson@pilot.blaudden +540 -540
    Update error messages after checks
    ---
    Remove the newly added space in error message, should not be there

ChangeSet@1.2392.28.1, 2007-02-22 16:59:57+02:00, monty@mysql.com +43 -0
  Fixed compiler warnings (for linux and win32 and win64)
  Fixed a couple of usage of not initialized warnings (unlikely cases)

  client/mysqldump.c@1.257, 2007-02-22 16:59:54+02:00, monty@mysql.com +2 -2
    Fixed compiler warnings from 'max' build

  client/mysqltest.c@1.276, 2007-02-22 16:59:54+02:00, monty@mysql.com +9 -8
    Removed compiler warnings

  cmd-line-utils/readline/xmalloc.c@1.8, 2007-02-22 16:59:54+02:00, monty@mysql.com +2 -2
    Fixed compiler warnings from 'max' build

  extra/comp_err.c@1.25.1.1, 2007-02-22 16:59:54+02:00, monty@mysql.com +4 -0
    Fixed compiler warnings from 'max' build

  extra/yassl/include/openssl/ssl.h@1.21, 2007-02-22 16:59:54+02:00, monty@mysql.com +6 -2
    Changed prototype for SSL_set_fd() to fix compiler warnings (and possible errors) on windows 64 bit

  extra/yassl/include/socket_wrapper.hpp@1.11, 2007-02-22 16:59:54+02:00, monty@mysql.com +2 -4
    Moved socket_t to ssl.h, to be able to removed compiler warnings on windows 64 bit

  extra/yassl/src/ssl.cpp@1.26, 2007-02-22 16:59:54+02:00, monty@mysql.com +1 -1
    Changed prototype for SSL_set_fd() to fix compiler warnings (and possible errors) on windows 64 bit

  extra/yassl/taocrypt/src/integer.cpp@1.29, 2007-02-22 16:59:54+02:00, monty@mysql.com +1 -1
    Fixed compiler warnings

  include/my_global.h@1.136, 2007-02-22 16:59:54+02:00, monty@mysql.com +15 -0
    Added my_offsetof() macro from 5.1 to get rid of compiler warnings

  innobase/include/ut0byte.ic@1.5, 2007-02-22 16:59:54+02:00, monty@mysql.com +2 -2
    Fixed compiler warnings on win64

  innobase/include/ut0ut.ic@1.4, 2007-02-22 16:59:54+02:00, monty@mysql.com +1 -1
    Fixed compiler warnings on win64

  libmysql/libmysql.def@1.45, 2007-02-22 16:59:54+02:00, monty@mysql.com +0 -1
    Fixed compiler warnings on win64

  myisam/mi_packrec.c@1.42, 2007-02-22 16:59:54+02:00, monty@mysql.com +1 -1
    Fixed compiler warnings on win64

  myisam/myisamchk.c@1.125, 2007-02-22 16:59:54+02:00, monty@mysql.com +1 -0
    Fixed compiler warnings from 'max' build

  mysys/base64.c@1.15, 2007-02-22 16:59:54+02:00, monty@mysql.com +2 -2
    Fixed compiler warnings on win64

  mysys/mf_keycache.c@1.61, 2007-02-22 16:59:54+02:00, monty@mysql.com +4 -1
    Fixed compiler warnings from 'max' build

  mysys/my_getopt.c@1.62, 2007-02-22 16:59:54+02:00, monty@mysql.com +1 -0
    Fixed compiler warnings from 'max' build

  mysys/my_init.c@1.48, 2007-02-22 16:59:54+02:00, monty@mysql.com +2 -0
    Fixed compiler warnings from 'max' build

  mysys/my_thr_init.c@1.40.1.1, 2007-02-22 16:59:54+02:00, monty@mysql.com +3 -3
    Fixed compiler warnings

  mysys/ptr_cmp.c@1.8, 2007-02-22 16:59:54+02:00, monty@mysql.com +1 -1
    Fixed compiler warnings from 'max' build

  ndb/include/kernel/signaldata/DictTabInfo.hpp@1.24, 2007-02-22 16:59:54+02:00, monty@mysql.com +5 -5
    Fixed compiler warnings

  server-tools/instance-manager/mysql_connection.cc@1.19, 2007-02-22 16:59:54+02:00, monty@mysql.com +1 -1
    Fixed compiler warnings

  server-tools/instance-manager/mysqlmanager.cc@1.19.1.1, 2007-02-22 16:59:54+02:00, monty@mysql.com +1 -1
    Fixed compiler warnings

  sql/filesort.cc@1.116, 2007-02-22 16:59:55+02:00, monty@mysql.com +1 -1
    Initalize variable that was used unitialized in error conditions

  sql/ha_berkeley.cc@1.166, 2007-02-22 16:59:55+02:00, monty@mysql.com +10 -0
    Moved get_auto_primary_key() here as int5store() gives (wrong) compiler warnings in win64

  sql/ha_berkeley.h@1.81, 2007-02-22 16:59:55+02:00, monty@mysql.com +1 -7
    Moved get_auto_primary_key() to ha_berkeley.cc

  sql/ha_innodb.cc@1.308, 2007-02-22 16:59:55+02:00, monty@mysql.com +6 -3
    Fixed compiler warnings

  sql/item.cc@1.250, 2007-02-22 16:59:55+02:00, monty@mysql.com +2 -0
    Fixed compiler warnings from 'max' build

  sql/item_timefunc.cc@1.141, 2007-02-22 16:59:55+02:00, monty@mysql.com +1 -1
    Fixed compiler warnings

  sql/mysqld.cc@1.589, 2007-02-22 16:59:55+02:00, monty@mysql.com +2 -2
    Fixed compiler warnings

  sql/sql_acl.cc@1.217, 2007-02-22 16:59:55+02:00, monty@mysql.com +2 -0
    Fixed compiler warnings from 'max' build

  sql/sql_base.cc@1.360.5.1, 2007-02-22 16:59:55+02:00, monty@mysql.com +1 -0
    Fixed compiler warnings from 'max' build

  sql/sql_insert.cc@1.211.1.5, 2007-02-22 16:59:55+02:00, monty@mysql.com +1 -0
    Initialize variable that may be used unitialized on error conditions (not fatal)

  sql/sql_prepare.cc@1.194, 2007-02-22 16:59:55+02:00, monty@mysql.com +1 -0
    Fixed compiler warnings from 'max' build

  sql/sql_select.cc@1.493, 2007-02-22 16:59:55+02:00, monty@mysql.com +2 -2
    Fixed compiler warnings

  sql/sql_show.cc@1.341, 2007-02-22 16:59:55+02:00, monty@mysql.com +4 -3
    Fixed compiler warnings

  sql/udf_example.def@1.3, 2007-02-22 16:59:55+02:00, monty@mysql.com +0 -1
    Fixed compiler warnings on win64

  sql/unireg.cc@1.83, 2007-02-22 16:59:55+02:00, monty@mysql.com +3 -0
    Initialize variable that may be used unitialized on error conditions

  strings/ctype-ucs2.c@1.65, 2007-02-22 16:59:55+02:00, monty@mysql.com +4 -1
    Fixed compiler warnings

  strings/ctype-utf8.c@1.105, 2007-02-22 16:59:55+02:00, monty@mysql.com +2 -0
    Fixed compiler warnings

  strings/decimal.c@1.77, 2007-02-22 16:59:55+02:00, monty@mysql.com +3 -0
    Fixed compiler warnings

  support-files/compiler_warnings.supp@1.4, 2007-02-22 16:59:56+02:00, monty@mysql.com +8 -0
    Ignore warnings from sql_yacc.cc that are hard to remove
    Ignore some not important warnings from windows 64 bit build

  tools/mysqlmanager.c@1.50, 2007-02-22 16:59:56+02:00, monty@mysql.com +1 -1
    Fixed compiler warnings

ChangeSet@1.2216.71.50, 2007-02-22 15:31:21+01:00, jonas@perch.ndb.mysql.com +1 -0
  ndb - bug#26481 - fix of bug fix 5.0 version

  ndb/src/kernel/blocks/dblqh/DblqhMain.cpp@1.97.2.3, 2007-02-22 15:31:19+01:00, jonas@perch.ndb.mysql.com +7 -4
    ndb - bug#26481 - fix of bug fix 5.0 version

ChangeSet@1.2377.45.1, 2007-02-22 14:11:01+01:00, mhansson@linux-st28.site +2 -0
  Bug #24010: INSERT INTO ... SELECT fails on unique constraint with data 
  it doesn't select.
  
  This bug was fixed along with bug #16861: User defined variable can 
  have a wrong value if a tmp table was used.
  
  There the fix consisted of Item_func_set_user_var overloading the method
  Item::save_in_field. Consider the query from the test case:
  
  
  INSERT INTO foo( bar, baz )
  SELECT 
    bar,
    @newBaz := 1 + baz
  FROM 
    foo
  WHERE 
    quux <= 0.1;
  
  Here the assignment expression '@newBaz := 1 + baz' is represented by an 
  Item_func_set_user_var. Its member method save_in_field, which writes the 
  value of this assignment into the result field, writes the val_xxx() value, 
  which is not updated at this point. In the fix introduced by the patch,
  the save_in_field method reads the actual variable value instead.
  
  See also comment for 
  ChangeSet@1.2368.1.3, 2007-01-09 23:24:56+03:00, evgen@moonbone.local +4 -0
  and comment for
  Item_func_set_user_var::save_in_field (item_func.cc)

  mysql-test/r/update.result@1.32, 2007-02-22 14:11:00+01:00, mhansson@linux-st28.site +19 -0
    BUG#24010
    The correct, and expected, result

  mysql-test/t/update.test@1.30, 2007-02-22 14:11:00+01:00, mhansson@linux-st28.site +26 -0
    BUG#24010
    The test case for this bug. When the bug is active, the INSERT ... SELECT 
    statement will try to insert the values <1, 2> which gives an error

ChangeSet@1.2392.24.3, 2007-02-22 15:28:42+03:00, kaa@polly.local +1 -0
  Force the server restart before running mysqlbinlog-cp932.test to fix PB failures introduced by the patch for bug #18743.

  mysql-test/t/mysqlbinlog-cp932-master.opt@1.1, 2007-02-22 15:28:39+03:00, kaa@polly.local +1 -0
    New BitKeeper file ``mysql-test/t/mysqlbinlog-cp932-master.opt''

  mysql-test/t/mysqlbinlog-cp932-master.opt@1.0, 2007-02-22 15:28:39+03:00, kaa@polly.local +0 -0

ChangeSet@1.2377.44.1, 2007-02-21 23:00:32+03:00, evgen@moonbone.local +11 -0
  Bug#23800: Outer fields in correlated subqueries is used in a temporary table
  created for sorting.
  
  Any outer reference in a subquery was represented by an Item_field object.
  If the outer select employs a temporary table all such fields should be
  replaced with fields from that temporary table in order to point to the 
  actual data. This replacement wasn't done and that resulted in a wrong
  subquery evaluation and a wrong result of the whole query.
  
  Now any outer field is represented by two objects - Item_field placed in the
  outer select and Item_outer_ref in the subquery. Item_field object is
  processed as a normal field and the reference to it is saved in the
  ref_pointer_array. Thus the Item_outer_ref is always references the correct
  field. The original field is substituted for a reference in the
  Item_field::fix_outer_field() function.
  
  New function called fix_inner_refs() is added to fix fields referenced from
  inner selects and to fix references (Item_ref objects) to these fields.
  
  The new Item_outer_ref class is a descendant of the Item_direct_ref class.
  It additionally stores a reference to the original field and designed to
  behave more like a field.

  mysql-test/r/subselect.result@1.172.1.1, 2007-02-21 22:59:50+03:00, evgen@moonbone.local +51 -9
    Added a test case for bug#23800: Correlated sub query returning incorrect results when
    operated upon.

  mysql-test/r/subselect3.result@1.5, 2007-02-21 22:59:51+03:00, evgen@moonbone.local +11 -11
    Corrected test cases result after fix for bug#23800: Correlated sub query returning
    incorrect results when operated upon.

  mysql-test/t/subselect.test@1.139.1.1, 2007-02-21 22:59:51+03:00, evgen@moonbone.local +28 -1
    Added a test case for bug#23800: Correlated sub query returning incorrect results when
    operated upon.

  sql/item.cc@1.245.10.1, 2007-02-21 22:59:45+03:00, evgen@moonbone.local +71 -9
    Bug#23800: Correlated sub query returning incorrect results when operated upon.
    Now all outer fields are substituted with references to them (Item_outer_ref objects)
    in the Item_field::fix_outer_field() function.
    The original field is saved in the Item_outer_ref object.

  sql/item.h@1.213.5.1, 2007-02-21 22:59:48+03:00, evgen@moonbone.local +37 -3
    Bug#23800: Correlated sub query returning incorrect results when operated upon.
    Added the Item_outer_ref class.

  sql/mysql_priv.h@1.429.7.3, 2007-02-21 22:59:48+03:00, evgen@moonbone.local +2 -0
    Bug#23800: Correlated sub query returning incorrect results when operated upon.
    Added the fix_inner_refs() function prototype.

  sql/sql_delete.cc@1.188.1.4, 2007-02-21 22:59:49+03:00, evgen@moonbone.local +6 -0
    Bug#23800: Correlated sub query returning incorrect results when operated upon.
    Added call to the fix_inner_refs() function.

  sql/sql_lex.cc@1.209.3.1, 2007-02-21 23:00:04+03:00, evgen@moonbone.local +1 -0
    Bug#23800: Correlated sub query returning incorrect results when operated upon.
    Added cleanup of the inner_refs_list.

  sql/sql_lex.h@1.233.7.1, 2007-02-21 23:00:14+03:00, evgen@moonbone.local +2 -1
    Bug#23800: Correlated sub query returning incorrect results when operated upon.
    The inner_refs_list is added to the SELECT_LEX class.

  sql/sql_select.cc@1.488.2.2, 2007-02-21 22:59:49+03:00, evgen@moonbone.local +76 -7
    Bug#23800: Correlated sub query returning incorrect results when operated upon.
    The new function called fix_inner_refs() is added.

  sql/sql_update.cc@1.205.1.8, 2007-02-21 22:59:50+03:00, evgen@moonbone.local +5 -0
    Bug#23800: Correlated sub query returning incorrect results when operated upon.
    Added call to the fix_inner_refs() function.

ChangeSet@1.2392.26.2, 2007-02-21 19:38:40+02:00, monty@mysql.com +18 -0
  After merge fixes
  This also fixes a bug in counting number of rows that are updated when we have many simultanous queries

  extra/yassl/src/ssl.cpp@1.25, 2007-02-21 19:38:38+02:00, monty@mysql.com +1 -1
    Removed compiler warning

  extra/yassl/taocrypt/src/asn.cpp@1.14, 2007-02-21 19:38:38+02:00, monty@mysql.com +0 -2
    After merge fixes

  extra/yassl/testsuite/testsuite.cpp@1.7, 2007-02-21 19:38:38+02:00, monty@mysql.com +2 -2
    Removed compiler warning

  mysql-test/r/ndb_lock.result@1.14, 2007-02-21 19:38:38+02:00, monty@mysql.com +1 -1
    After merge fixes

  ndb/src/common/debugger/EventLogger.cpp@1.30.1.1, 2007-02-21 19:38:38+02:00, monty@mysql.com +3 -0
    Removed compiler warning

  ndb/src/common/util/ConfigValues.cpp@1.14, 2007-02-21 19:38:38+02:00, monty@mysql.com +0 -2
    Removed compiler warning

  ndb/src/common/util/NdbSqlUtil.cpp@1.35, 2007-02-21 19:38:38+02:00, monty@mysql.com +0 -2
    Removed compiler warning

  ndb/src/kernel/blocks/dbtc/DbtcMain.cpp@1.103.1.1, 2007-02-21 19:38:38+02:00, monty@mysql.com +0 -3
    Removed compiler warning

  ndb/src/kernel/blocks/dbtup/DbtupIndex.cpp@1.15, 2007-02-21 19:38:38+02:00, monty@mysql.com +0 -2
    Removed compiler warning

  ndb/src/kernel/blocks/dbtup/DbtupSystemRestart.cpp@1.8, 2007-02-21 19:38:38+02:00, monty@mysql.com +0 -2
    Removed compiler warning

  ndb/src/kernel/vm/ndbd_malloc.cpp@1.3, 2007-02-21 19:38:38+02:00, monty@mysql.com +2 -0
    Removed compiler warning

  ndb/src/mgmclient/main.cpp@1.25, 2007-02-21 19:38:38+02:00, monty@mysql.com +0 -2
    Removed compiler warning

  ndb/src/ndbapi/SignalSender.cpp@1.11, 2007-02-21 19:38:38+02:00, monty@mysql.com +0 -8
    Removed compiler warning

  sql/ha_ndbcluster.cc@1.297, 2007-02-21 19:38:38+02:00, monty@mysql.com +3 -0
    Some extra safety

  sql/item_cmpfunc.cc@1.236, 2007-02-21 19:38:39+02:00, monty@mysql.com +1 -1
    After merge fixes

  sql/item_subselect.cc@1.151.1.2, 2007-02-21 19:38:39+02:00, monty@mysql.com +4 -5
    After merge fixes

  sql/sql_insert.cc@1.211.1.4, 2007-02-21 19:38:39+02:00, monty@mysql.com +1 -1
    After merge fixes
    (This actually fixes a bug in old code when many connections are in use)

  support-files/compiler_warnings.supp@1.3, 2007-02-21 19:38:39+02:00, monty@mysql.com +2 -10
    Removed some suppressed warnings

ChangeSet@1.2216.71.49, 2007-02-21 18:01:04+01:00, jonas@perch.ndb.mysql.com +1 -0
  ndb -
    Make StartREDO come up as default in cluster log

  ndb/src/common/debugger/EventLogger.cpp@1.27.1.1, 2007-02-21 18:01:02+01:00, jonas@perch.ndb.mysql.com +1 -1
    Make StartREDO come up as default in cluster log

ChangeSet@1.2216.71.48, 2007-02-21 18:00:12+01:00, jonas@perch.ndb.mysql.com +1 -0
  ndb - bug#26515
    make sure logPartPtr is correctly initialized

  ndb/src/kernel/blocks/dblqh/DblqhMain.cpp@1.97.2.2, 2007-02-21 18:00:10+01:00, jonas@perch.ndb.mysql.com +4 -0
    fix bug#26515
      make sure logPartPtr is correctly initialized

ChangeSet@1.2377.5.5, 2007-02-21 13:02:57+02:00, monty@mysql.com +5 -0
  Fixed unsafe define of uint4korr()
  Fixed that --extern works with mysql-test-run.pl
  Small trivial cleanups

  include/my_global.h@1.134, 2007-02-21 13:02:55+02:00, monty@mysql.com +1 -1
    Fixed unsafe define of uint4korr()

  mysql-test/lib/mtr_report.pl@1.35, 2007-02-21 13:02:55+02:00, monty@mysql.com +4 -2
    Removed wrong messages when using --extern

  mysql-test/mysql-test-run.pl@1.190.2.1, 2007-02-21 13:02:55+02:00, monty@mysql.com +99 -80
    Fixed that --extern works
    Print help on stdout instead of stderr (make it easier to pipe it to less)

  mysql-test/t/ndb_lock.test@1.16, 2007-02-21 13:02:55+02:00, monty@mysql.com +1 -1
    Added other possible error code

  sql/sql_prepare.cc@1.192, 2007-02-21 13:02:55+02:00, monty@mysql.com +2 -2
    Removed not needed casts

ChangeSet@1.1616.2972.6, 2007-02-21 14:45:19+04:00, ramil@mysql.com +6 -0
  Fix for bug #26038: X() value of empty NOT NULL POINT is neither NULL nor NOT NULL
  
  Having maybe_null flag unset for geometry/spatial functions leads to
  wrong Item_func_isnull::val_int()'s results.
  Fix: set maybe_null flag and add is_null() methods.

  mysql-test/r/gis.result@1.15.1.9, 2007-02-21 14:45:18+04:00, ramil@mysql.com +43 -1
    Fix for bug #26038: X() value of empty NOT NULL POINT is neither NULL nor NOT NULL
      - test result.

  mysql-test/t/gis.test@1.17.1.5, 2007-02-21 14:45:18+04:00, ramil@mysql.com +35 -1
    Fix for bug #26038: X() value of empty NOT NULL POINT is neither NULL nor NOT NULL
      - test case.

  sql/item_geofunc.cc@1.18.1.7, 2007-02-21 14:45:18+04:00, ramil@mysql.com +17 -12
    Fix for bug #26038: X() value of empty NOT NULL POINT is neither NULL nor NOT NULL
      - set maybe_null flag for Item_geometry_func and Item_func_as_wkt.
      - moved length check to the beginnig of the 
        Item_func_spatial_collection::val_str() to affect geometry 
        collection objects at once.
      - changed Item_func_isempty::val_int() and Item_func_issimple::val_int()
        to properly handle null_value.

  sql/item_geofunc.h@1.8.1.3, 2007-02-21 14:45:18+04:00, ramil@mysql.com +32 -5
    Fix for bug #26038: X() value of empty NOT NULL POINT is neither NULL nor NOT NULL
      - set maybe_null flag for geometry/spatial functions.
      - added is_null() to Item_geometry_func and Item_func_spatial_rel
        classes.

  sql/spatial.cc@1.19.2.1, 2007-02-21 14:45:18+04:00, ramil@mysql.com +7 -6
    Fix for bug #26038: X() value of empty NOT NULL POINT is neither NULL nor NOT NULL
      - changed return type of Geometry::create_from_wkb() to be 
        consistent with Geometry::create_from_wkt(), now it returns
        Geometry object or NULL in case of error.

  sql/spatial.h@1.12.1.5, 2007-02-21 14:45:18+04:00, ramil@mysql.com +2 -2
    Fix for bug #26038: X() value of empty NOT NULL POINT is neither NULL nor NOT NULL
      - changed return type of Geometry::create_from_wkb() to be 
        consistent with Geometry::create_from_wkt(), now it returns
        Geometry object or NULL in case of error.

ChangeSet@1.2392.19.4, 2007-02-20 22:31:50+03:00, anozdrin@alik.opbmk +7 -0
  Fix for BUG#24415: Instance manager test im_daemon_life_cycle fails randomly.
  
  The cause of im_daemon_life_cycle.imtest random failures was the following
  behaviour of some implementations of LINUX threads: let's suppose that a
  process has several threads (in LINUX threads, there is a separate process for
  each thread). When the main process gets killed, the parent receives SIGCHLD
  before all threads (child processes) die. In other words, the parent receives
  SIGCHLD, when its child is not completely dead.
  
  In terms of IM, that means that IM-angel receives SIGCHLD when IM-main is not dead
  and still holds some resources. After receiving SIGCHLD, IM-angel restarts
  IM-main, but IM-main failed to initialize, because previous instance (copy) of
  IM-main still holds server socket (TCP-port).
  
  Another problem here was that IM-angel restarted IM-main only if it was killed
  by signal. If it exited with error, IM-angel thought it's intended / graceful
  shutdown and exited itself.
  
  So, when the second instance of IM-main failed to initialize, IM-angel thought
  it's intended shutdown and quit.
  
  The fix is
    1. to change IM-angel so that it restarts IM-main if it exited with error code;
    2. to change IM-main so that it returns proper exit code in case of failure.

  mysql-test/t/disabled.def@1.43, 2007-02-20 22:31:48+03:00, anozdrin@alik.opbmk +0 -1
    Enable im_daemon_life_cycle.

  server-tools/instance-manager/listener.cc@1.30, 2007-02-20 22:31:48+03:00, anozdrin@alik.opbmk +3 -0
    Set error status if Listener failed to initialize.

  server-tools/instance-manager/manager.cc@1.39, 2007-02-20 22:31:48+03:00, anozdrin@alik.opbmk +9 -5
    Return exit code from the manager.

  server-tools/instance-manager/manager.h@1.8, 2007-02-20 22:31:48+03:00, anozdrin@alik.opbmk +1 -1
    Return exit code from the manager.

  server-tools/instance-manager/mysqlmanager.cc@1.20, 2007-02-20 22:31:48+03:00, anozdrin@alik.opbmk +13 -15
    1. Restart IM-main if exit code is not EXIT_SUCCESS (0).
    2. Log IM-main exit code in case of failure.

  server-tools/instance-manager/thread_registry.cc@1.13, 2007-02-20 22:31:48+03:00, anozdrin@alik.opbmk +21 -0
    Add support for exit code.

  server-tools/instance-manager/thread_registry.h@1.9, 2007-02-20 22:31:48+03:00, anozdrin@alik.opbmk +4 -0
    Add support for exit code.

ChangeSet@1.2392.24.2, 2007-02-20 22:29:18+03:00, kaa@polly.local +1 -0
  Fixed the binlog numbering after changes introduced by patch for bug18743.

  mysql-test/t/mysqlbinlog.test@1.36.2.2, 2007-02-20 22:29:16+03:00, kaa@polly.local +3 -3
    Fixed the binlog numbering after changes introduced by patch for bug18743.

ChangeSet@1.2392.1.47, 2007-02-20 18:35:59+01:00, msvensson@pilot.blaudden +1 -0
  Use a temporary file to execute SQL commands with utf-8 chararcters

  mysql-test/t/rpl_temporary.test@1.23, 2007-02-20 18:35:58+01:00, msvensson@pilot.blaudden +8 -1
    Use a temporary file to execute SQL commands with utf-8 chararcters

ChangeSet@1.2392.1.46, 2007-02-20 18:22:33+01:00, msvensson@pilot.blaudden +1 -0
  Replace "exec diff" with diff_files

  mysql-test/t/mysql.test@1.24.1.4, 2007-02-20 18:22:32+01:00, msvensson@pilot.blaudden +1 -1
    Replace "exec diff" with diff_files

ChangeSet@1.1616.2969.15, 2007-02-20 18:20:58+01:00, msvensson@pilot.blaudden +2 -0
  Add "diff_files" command to mysqltest

  client/mysqltest.c@1.92.21.48, 2007-02-20 18:20:57+01:00, msvensson@pilot.blaudden +75 -1
    Add "diff_files" command to mysqltest

  mysql-test/t/mysqltest.test@1.3.1.25, 2007-02-20 18:20:57+01:00, msvensson@pilot.blaudden +35 -0
    Add "diff_files" command to mysqltest

ChangeSet@1.2392.23.1, 2007-02-20 16:50:54+01:00, bteam@mysql.com +1 -0
  Raise version number after cloning 5.0.36

  configure.in@1.416.1.11, 2007-02-20 16:50:44+01:00, bteam@mysql.com +2 -2
    Raise version number after cloning 5.0.36

ChangeSet@1.2392.22.2, 2007-02-20 16:24:38+01:00, msvensson@pilot.blaudden +5 -0
  Bug#20166 mysql-test-run.pl does not test system privilege tables creation
   - Part 2, add @@hostname system variable

  mysql-test/r/variables.result@1.91, 2007-02-20 16:24:37+01:00, msvensson@pilot.blaudden +8 -0
    Add testcase for @@hostname

  mysql-test/t/variables.test@1.66, 2007-02-20 16:24:37+01:00, msvensson@pilot.blaudden +11 -0
    Add testcase for @@hostname

  sql/log.cc@1.200.2.1, 2007-02-20 16:24:37+01:00, msvensson@pilot.blaudden +1 -1
    Use pidfile_name as base when generating the default log name

  sql/mysqld.cc@1.582.1.17, 2007-02-20 16:24:37+01:00, msvensson@pilot.blaudden +10 -4
    Init "glob_hostname" to that of hostname, fallback to "localhost"
    if 'gethostname' should fail.
    Init "pidfile_name" to hostname.pid and fallback to "mysql.pid" if
    'gethostname' should fail 

  sql/set_var.cc@1.176.1.4, 2007-02-20 16:24:37+01:00, msvensson@pilot.blaudden +6 -0
    Add new system variable "hostname"

ChangeSet@1.1616.2969.14, 2007-02-20 14:20:49+01:00, msvensson@pilot.blaudden +1 -0
  New version of 'do_cat_file' that will trim cr/lf to lf

  client/mysqltest.c@1.92.21.47, 2007-02-20 14:20:48+01:00, msvensson@pilot.blaudden +20 -3
    New version of 'do_cat_file' that will trim cr/lf to lf

ChangeSet@1.1616.2877.51, 2007-02-20 13:10:27+01:00, joerg@trift2. +1 -0
  After-merge fix:
  The declaration of "thr_client_alarm" had got lost, keep it in "mysys/thr_alarm.c".

  mysys/thr_alarm.c@1.44.2.6, 2007-02-20 13:10:25+01:00, joerg@trift2. +1 -0
    After-merge fix:
    In 4.1, the variable "thr_client_alarm" is declared in this module.

ChangeSet@1.2392.1.43, 2007-02-20 13:06:01+01:00, msvensson@pilot.blaudden +1 -0
  Change "exec echo" commands with different delimiters that are also
  escape chars to use "write_file" to avoid confusion about what's what.

  mysql-test/t/mysql.test@1.24.1.3, 2007-02-20 13:05:59+01:00, msvensson@pilot.blaudden +10 -4
    Change "exec echo" commands with different delimiters that are also
    escape chars to use "write_file" to avoid confusion about what's what.

ChangeSet@1.2392.22.1, 2007-02-20 12:48:15+01:00, msvensson@pilot.blaudden +4 -0
  Bug#20166 mysql-test-run.pl does not test system privilege tables creation
   - Add test of bootstrap mode
   - Make mysqld return error if bootstrap failed  

  mysql-test/mysql-test-run.pl@1.199, 2007-02-20 12:48:13+01:00, msvensson@pilot.blaudden +5 -2
    Remove options --skip-grant-tables as that is always
    turned on by --bootstrap
    Remove options --console as that does not affect --bootstrap mode
    at all
    Add environment variable MYSQLD_BOOTSTRAP_CMD containing path 
    to mysqld and the arguments used for bootstrap

  mysql-test/r/bootstrap.result@1.1, 2007-02-20 12:48:14+01:00, msvensson@pilot.blaudden +8 -0
    New BitKeeper file ``mysql-test/r/bootstrap.result''

  mysql-test/r/bootstrap.result@1.0, 2007-02-20 12:48:14+01:00, msvensson@pilot.blaudden +0 -0

  mysql-test/t/bootstrap.test@1.1, 2007-02-20 12:48:14+01:00, msvensson@pilot.blaudden +46 -0
    New BitKeeper file ``mysql-test/t/bootstrap.test''

  mysql-test/t/bootstrap.test@1.0, 2007-02-20 12:48:14+01:00, msvensson@pilot.blaudden +0 -0

  sql/sql_parse.cc@1.593.7.1, 2007-02-20 12:48:14+01:00, msvensson@pilot.blaudden +12 -1
    Abort bootstrap if execution fails
    Report error to stderr/log

ChangeSet@1.2392.1.42, 2007-02-20 12:06:04+01:00, msvensson@pilot.blaudden +1 -0
  Bug#25807 LOAD DATA INFILE does not work with Pipes
   - Additional fix for io_cache_init being called on a closed file

  mysys/mf_iocache.c@1.66, 2007-02-20 12:06:02+01:00, msvensson@pilot.blaudden +19 -15
    The file does not need to be open when init_io_cache is called
    so don't call my_tell in that case

ChangeSet@1.2392.17.2, 2007-02-20 10:01:54+01:00, istruewing@chilla.local +1 -0
  Fixed a bad merge. Got a duplicate symbol on OSX.

  mysys/my_thr_init.c@1.40, 2007-02-20 10:01:52+01:00, istruewing@chilla.local +0 -2
    Fixed a bad merge. Got a duplicate symbol on OSX.

ChangeSet@1.2216.71.47, 2007-02-20 00:55:33+01:00, jonas@perch.ndb.mysql.com +1 -0
  fix compile error in testBitfield

  ndb/test/ndbapi/testBitfield.cpp@1.11, 2007-02-20 00:55:32+01:00, jonas@perch.ndb.mysql.com +9 -0
    fix compile error in testBitfield

ChangeSet@1.2216.71.46, 2007-02-19 22:51:04+01:00, jonas@perch.ndb.mysql.com +1 -0
  ndb - fix correct argv/argc handling in testBitfield

  ndb/test/ndbapi/testBitfield.cpp@1.10, 2007-02-19 22:51:02+01:00, jonas@perch.ndb.mysql.com +4 -3
    fix correct argv/argc handling in testBitfield

ChangeSet@1.2216.71.45, 2007-02-19 22:30:54+01:00, jonas@perch.ndb.mysql.com +1 -0
  ndb -
    forgott to add testcase for bug#26481

  ndb/test/run-test/daily-basic-tests.txt@1.41.1.8, 2007-02-19 22:30:52+01:00, jonas@perch.ndb.mysql.com +4 -0
    forgott to add testcase for bug#26481

ChangeSet@1.1616.2969.13, 2007-02-19 20:34:12+01:00, msvensson@pilot.blaudden +1 -0
  Turn the "is_windows" flag _on_ when compiled on windows

  client/mysqltest.c@1.92.21.46, 2007-02-19 20:34:11+01:00, msvensson@pilot.blaudden +1 -1
    Turn the "is_windows" flag _on_ when compiled on windows

ChangeSet@1.2392.1.40, 2007-02-19 20:30:34+01:00, msvensson@pilot.blaudden +1 -0
  Remove extra ; at end of line

  mysql-test/t/mysqldump.test@1.110, 2007-02-19 20:30:33+01:00, msvensson@pilot.blaudden +4 -4
    Remove extra ; at end of line

ChangeSet@1.2216.71.44, 2007-02-19 20:13:08+01:00, jonas@perch.ndb.mysql.com +5 -0
  ndb - bug#26481
    fix for killed node during initial node restart

  ndb/src/kernel/blocks/dbdih/Dbdih.hpp@1.14.2.1, 2007-02-19 20:13:07+01:00, jonas@perch.ndb.mysql.com +1 -0
    add flag for initial node restart, to keep track on when to concider it to be "done"

  ndb/src/kernel/blocks/dbdih/DbdihInit.cpp@1.13.1.1, 2007-02-19 20:13:07+01:00, jonas@perch.ndb.mysql.com +1 -0
    add flag for initial node restart, to keep track on when to concider it to be "done"

  ndb/src/kernel/blocks/dbdih/DbdihMain.cpp@1.55.1.13, 2007-02-19 20:13:07+01:00, jonas@perch.ndb.mysql.com +22 -0
    add flag for initial node restart, to keep track on when to concider it to be "done"

  ndb/src/kernel/blocks/dblqh/DblqhMain.cpp@1.97.2.1, 2007-02-19 20:13:07+01:00, jonas@perch.ndb.mysql.com +2 -1
    Check cstartRecReq also when refusing GCP_SAVEREQ

  ndb/test/ndbapi/testNodeRestart.cpp@1.24.1.4, 2007-02-19 20:13:07+01:00, jonas@perch.ndb.mysql.com +43 -0
    add testcase

ChangeSet@1.2392.1.39, 2007-02-19 18:25:42+01:00, msvensson@pilot.blaudden +1 -0
  Remove unportable constructs in mysqldump.test

  mysql-test/t/mysqldump.test@1.109, 2007-02-19 18:25:41+01:00, msvensson@pilot.blaudden +14 -12
    Remove unportable constructs in mysqldump.test

ChangeSet@1.1616.2969.12, 2007-02-19 18:23:59+01:00, msvensson@pilot.blaudden +2 -0
  Commment out two test's thats just confusing for cmd.exe 

  mysql-test/r/mysqltest.result@1.3.1.19, 2007-02-19 18:23:58+01:00, msvensson@pilot.blaudden +0 -3
    Commment out two test's thats just confusing for cmd.exe 

  mysql-test/t/mysqltest.test@1.3.1.24, 2007-02-19 18:23:58+01:00, msvensson@pilot.blaudden +4 -4
    Commment out two test's thats just confusing for cmd.exe 

ChangeSet@1.1616.2969.11, 2007-02-19 18:19:47+01:00, msvensson@pilot.blaudden +3 -0
  Add cat_file command to mysqltest

  client/mysqltest.c@1.92.21.45, 2007-02-19 18:19:46+01:00, msvensson@pilot.blaudden +47 -1
    Add cat_file command to mysqltest

  mysql-test/r/mysqltest.result@1.3.1.18, 2007-02-19 18:19:46+01:00, msvensson@pilot.blaudden +4 -0
    Add cat_file command to mysqltest

  mysql-test/t/mysqltest.test@1.3.1.23, 2007-02-19 18:19:46+01:00, msvensson@pilot.blaudden +14 -0
    Add cat_file command to mysqltest

ChangeSet@1.2392.1.36, 2007-02-19 17:40:34+01:00, msvensson@pilot.blaudden +1 -0
  Use a temporary file to pass UTF8 chars to "mysql" in a portable
  way

  mysql-test/t/mysqlbinlog.test@1.36.1.1, 2007-02-19 17:40:33+01:00, msvensson@pilot.blaudden +9 -1
    Use a temporary file to pass UTF8 chars to "mysql" in a portable
    way

ChangeSet@1.1616.2969.10, 2007-02-19 16:39:50+01:00, msvensson@pilot.blaudden +2 -0
  Add "append_file" command to mysqltest

  client/mysqltest.c@1.92.21.44, 2007-02-19 16:39:49+01:00, msvensson@pilot.blaudden +90 -30
    Add "append_file" command to mysqltest

  mysql-test/t/mysqltest.test@1.3.1.22, 2007-02-19 16:39:49+01:00, msvensson@pilot.blaudden +19 -0
    Add "append_file" command to mysqltest

ChangeSet@1.2392.1.34, 2007-02-19 15:46:32+01:00, msvensson@pilot.blaudden +1 -0
  Replace "exec rm" with  remove_file and "exec touch" with "write_file"

  mysql-test/t/csv.test@1.10, 2007-02-19 15:46:30+01:00, msvensson@pilot.blaudden +4 -2
    Replace "exec rm" with  remove_file and "exec touch" with "write_file"

ChangeSet@1.2377.4.14, 2007-02-19 14:57:54+01:00, thek@kpdesk.mysql.com +4 -0
  Bug#23240 --init_file statements with NOW() reports '1970-01-01 11:00:00'as the date time
  
  - Starting time of a query sent by bootstrapping wasn't initialized
    and starting time defaulted to 0. This later used value by NOW-
    item and was translated to 1970-01-01 11:00:00.
  - Marketing the time with thd->set_time() before the call to
    mysql_parse resolves this issue.
  - set_time was refactored to be part of the thd->init_for_queries-
    process.

  mysql-test/r/init_file.result@1.3, 2007-02-19 14:57:52+01:00, thek@kpdesk.mysql.com +7 -0
    Manual merge from 4.1

  mysql-test/std_data/init_file.dat@1.8, 2007-02-19 14:57:52+01:00, thek@kpdesk.mysql.com +9 -0
    Manual merge from 4.1

  sql/sql_class.cc@1.256.4.1, 2007-02-19 14:57:52+01:00, thek@kpdesk.mysql.com +1 -0
    - Moved set_time into init_for_queries process.

  sql/sql_parse.cc@1.593.6.2, 2007-02-19 14:57:52+01:00, thek@kpdesk.mysql.com +1 -2
    Bug#23240 --init_file statements with NOW() reports '1970-01-01 11:00:00'as the date time
    
    - Starting time of a query sent by bootstrapping wasn't initialized
      and starting time defaulted to 0. This later used value by NOW-
      item and was translated to 1970-01-01 11:00:00.
    - Marketing the time with thd->set_time() before the call to
      mysql_parse resolves this issue.
    - set_time was refactored to be part of the thd->init_for_queries-
      process.

ChangeSet@1.2377.43.1, 2007-02-19 14:39:37+02:00, gkodinov@macbook.gmz +9 -0
  Bug #25831: Deficiencies in INSERT ... SELECT ... field name resolving.
   Several problems fixed: 
    1. There was a "catch-all" context initialization in setup_tables()
      that was causing the table that we insert into to be visible in the 
      SELECT part of an INSERT .. SELECT .. statement with no tables in
      its FROM clause. This was making sure all the under-initialized
      contexts in various parts of the code are not left uninitialized.
      Fixed by removing the "catch-all" statement and initializing the 
      context in the parser.
    2. Incomplete name resolution context when resolving the right-hand
      values in the ON DUPLICATE KEY UPDATE ... part of an INSERT ... SELECT ...
      caused columns from NATURAL JOIN/JOIN USING table references in the
      FROM clause of the select to be unavailable.
      Fixed by establishing a proper name resolution context.
    3. When setting up the special name resolution context for problem 2
      there was no check for cases where an aggregate function without a
      GROUP BY effectively takes the column from the SELECT part of an 
      INSERT ... SELECT unavailable for ON DUPLICATE KEY UPDATE.
      Fixed by checking for that condition when setting up the name 
      resolution context.

  mysql-test/r/insert_update.result@1.21, 2007-02-19 14:39:24+02:00, gkodinov@macbook.gmz +17 -0
    Bug #25831: Deficiencies in INSERT ... SELECT ... field name resolving.
     - test case

  mysql-test/t/insert_update.test@1.21, 2007-02-19 14:39:25+02:00, gkodinov@macbook.gmz +23 -0
    Bug #25831: Deficiencies in INSERT ... SELECT ... field name resolving.
     - test case

  sql/item.h@1.213.4.1, 2007-02-19 14:39:25+02:00, gkodinov@macbook.gmz +6 -1
    Bug #25831: Deficiencies in INSERT ... SELECT ... field name resolving.
     - save_next_local is not referenced any more outside class methods

  sql/sql_base.cc@1.360.4.1, 2007-02-19 14:39:26+02:00, gkodinov@macbook.gmz +2 -15
    Bug #25831: Deficiencies in INSERT ... SELECT ... field name resolving.
     - removed a "catch-all" code to cater for correct context initialization

  sql/sql_help.cc@1.54, 2007-02-19 14:39:27+02:00, gkodinov@macbook.gmz +2 -0
    Bug #25831: Deficiencies in INSERT ... SELECT ... field name resolving.
     - fixed the name resolution context initialization

  sql/sql_insert.cc@1.211.6.1, 2007-02-19 14:39:28+02:00, gkodinov@macbook.gmz +39 -38
    Bug #25831: Deficiencies in INSERT ... SELECT ... field name resolving.
     - Fixed the context of resolving the values in INSERT SELECT ON UPDATE

  sql/sql_prepare.cc@1.187.4.1, 2007-02-19 14:39:29+02:00, gkodinov@macbook.gmz +8 -13
    Bug #25831: Deficiencies in INSERT ... SELECT ... field name resolving.
     - Correct context for name resolution of prepared INSERT .. SELECT

  sql/sql_union.cc@1.134.1.3, 2007-02-19 14:39:30+02:00, gkodinov@macbook.gmz +2 -0
    Bug #25831: Deficiencies in INSERT ... SELECT ... field name resolving.
     - fixed the name resolution context initialization

  sql/sql_yacc.yy@1.498.6.1, 2007-02-19 14:39:30+02:00, gkodinov@macbook.gmz +6 -1
    Bug #25831: Deficiencies in INSERT ... SELECT ... field name resolving.
     - Set the context here instead of setup_tables()

ChangeSet@1.2392.1.33, 2007-02-19 13:21:06+01:00, msvensson@pilot.blaudden +1 -0
  Add echo.c as EXTRA_DIST file

  client/Makefile.am@1.64, 2007-02-19 13:21:04+01:00, msvensson@pilot.blaudden +1 -1
    Add echo.c as EXTRA_DIST file

ChangeSet@1.2392.1.30, 2007-02-19 12:03:42+01:00, msvensson@pilot.blaudden +2 -0
  Update for running with cmd.exe directly

  mysql-test/r/mysqltest.result@1.40.1.2, 2007-02-19 12:03:41+01:00, msvensson@pilot.blaudden +0 -2
    Update result file after removing one test

  mysql-test/t/mysqltest.test@1.49.1.3, 2007-02-19 12:03:41+01:00, msvensson@pilot.blaudden +35 -22
    Remove use of "ls" in system
    Rewrite "system echo" which introduces CR/LF problems
    with  "write_file"
    Remove test for end of line junk for "write_file" - it has mismatching number of "'s 

ChangeSet@1.1616.2969.9, 2007-02-19 12:00:17+01:00, msvensson@pilot.blaudden +1 -0
  Don't output escape char from 'do_eval' on windows. "It" won't 
  know it's an escape char.
  Replace /dev/null with NUL
  Replace "closed stdout" with "not open fd"

  client/mysqltest.c@1.92.21.43, 2007-02-19 12:00:16+01:00, msvensson@pilot.blaudden +20 -3
    Don't output escape char from 'do_eval' on windows. "It" won't 
    know it's an escape char.
    Replace /dev/null with NUL
    Replace "closed stdout" with "not open fd"

ChangeSet@1.2360.4.1, 2007-02-19 13:57:06+03:00, kaa@polly.local +19 -0
  Bug#18743: Several test cases fails if "classic" configuration in 5.0
  The problem happened because those tests were using "cp932" and "ucs2" without checking whether these character sets are available. This fix moves test parts to make character set specific parts be tested only if they are:
  - some parts were moved to "ctype_ucs.test" and "ctype_cp932.test"
  - some parts were moved to the newly added tests "innodb-ucs2.test", "mysqlbinglog-cp932.test" and "sp-ucs2.test"

  mysql-test/r/ctype_cp932.result@1.8.1.1, 2007-02-19 13:57:02+03:00, kaa@polly.local +10 -0
    Moved cp932-specific test case from mysql.test

  mysql-test/r/innodb-ucs2.result@1.1, 2007-02-19 13:57:03+03:00, kaa@polly.local +313 -0
    New BitKeeper file ``mysql-test/r/innodb-ucs2.result''

  mysql-test/r/innodb-ucs2.result@1.0, 2007-02-19 13:57:03+03:00, kaa@polly.local +0 -0

  mysql-test/r/innodb.result@1.163.1.1, 2007-02-19 13:57:02+03:00, kaa@polly.local +0 -312
    Moved ucs2-specific test cases to innodb-ucs2.test

  mysql-test/r/mysql.result@1.27, 2007-02-19 13:57:02+03:00, kaa@polly.local +0 -10
    Move cp932-specific test cases to ctype_cp932.test

  mysql-test/r/mysqlbinlog-cp932.result@1.1, 2007-02-19 13:57:03+03:00, kaa@polly.local +19 -0
    New BitKeeper file ``mysql-test/r/mysqlbinlog-cp932.result''

  mysql-test/r/mysqlbinlog-cp932.result@1.0, 2007-02-19 13:57:03+03:00, kaa@polly.local +0 -0

  mysql-test/r/mysqlbinlog.result@1.24.2.1, 2007-02-19 13:57:02+03:00, kaa@polly.local +2 -18
    Moved cp932-specific test case to mysqlbinlog-cp932.test

  mysql-test/r/sp-ucs2.result@1.1, 2007-02-19 13:57:03+03:00, kaa@polly.local +14 -0
    New BitKeeper file ``mysql-test/r/sp-ucs2.result''

  mysql-test/r/sp-ucs2.result@1.0, 2007-02-19 13:57:03+03:00, kaa@polly.local +0 -0

  mysql-test/r/sp.result@1.217.1.1, 2007-02-19 13:57:02+03:00, kaa@polly.local +0 -14
    Moved ucs2-specific test case to sp-ucs2.test

  mysql-test/t/ctype_cp932.test@1.10.1.1, 2007-02-19 13:57:02+03:00, kaa@polly.local +14 -0
    Moved cp932-specific test case from mysql.test

  mysql-test/t/ctype_ucs2_def-master.opt@1.4, 2007-02-19 13:57:02+03:00, kaa@polly.local +1 -1
    Use the comma-separated list of character sets to avoid mysql-test errors when ucs2 is not available in the server

  mysql-test/t/ctype_ucs2_def.test@1.4, 2007-02-19 13:57:02+03:00, kaa@polly.local +2 -0
    Added requirement for ucs2 in the server

  mysql-test/t/innodb-ucs2.test@1.1, 2007-02-19 13:57:03+03:00, kaa@polly.local +226 -0
    New BitKeeper file ``mysql-test/t/innodb-ucs2.test''

  mysql-test/t/innodb-ucs2.test@1.0, 2007-02-19 13:57:03+03:00, kaa@polly.local +0 -0

  mysql-test/t/innodb.test@1.134.1.2, 2007-02-19 13:57:02+03:00, kaa@polly.local +0 -222
    Moved ucs2-specific test cases to innodb-ucs2.test

  mysql-test/t/mysql.test@1.24.2.1, 2007-02-19 13:57:02+03:00, kaa@polly.local +0 -14
    Move cp932-specific test cases to ctype_cp932.test

  mysql-test/t/mysqlbinlog-cp932.test@1.1, 2007-02-19 13:57:03+03:00, kaa@polly.local +19 -0
    New BitKeeper file ``mysql-test/t/mysqlbinlog-cp932.test''

  mysql-test/t/mysqlbinlog-cp932.test@1.0, 2007-02-19 13:57:03+03:00, kaa@polly.local +0 -0

  mysql-test/t/mysqlbinlog.test@1.33.3.1, 2007-02-19 13:57:02+03:00, kaa@polly.local +3 -18
    Moved cp932-specific test case to mysqlbinlog-cp932.test

  mysql-test/t/sp-ucs2.test@1.1, 2007-02-19 13:57:03+03:00, kaa@polly.local +28 -0
    New BitKeeper file ``mysql-test/t/sp-ucs2.test''

  mysql-test/t/sp-ucs2.test@1.0, 2007-02-19 13:57:03+03:00, kaa@polly.local +0 -0

  mysql-test/t/sp.test@1.207.1.1, 2007-02-19 13:57:02+03:00, kaa@polly.local +2 -23
    Moved ucs2-specific test case to sp-ucs2.test

  sql/mysqld.cc@1.582.16.1, 2007-02-19 13:57:03+03:00, kaa@polly.local +27 -4
    Allow specifying several character sets for test purposes, to make "mysqld" start even if the character set being tested is not compiled:
    mysqld --default-character-set=ucs2,latin1
    The first available character set will be chosen.

ChangeSet@1.1616.2953.2, 2007-02-19 09:37:34+01:00, thek@kpdesk.mysql.com +4 -0
  Bug#23240 --init-file statements with NOW() reports '1970-01-01 11:00:00'as the date time
  
  - Starting time of a query sent by file bootstrapping wasn't initialized
    and starting time defaulted to 0. This later used value by the Now-
    item and is translated to 1970-01-01 11:00:00.
  - marking the time with thd->set_time() before the call to 
    mysql_parse resolves this issue.

  mysql-test/r/init_file.result@1.1.1.1, 2007-02-19 09:37:32+01:00, thek@kpdesk.mysql.com +7 -0
    Appended test case

  mysql-test/std_data/init_file.dat@1.3.2.1, 2007-02-19 09:37:32+01:00, thek@kpdesk.mysql.com +8 -0
    Appended test case

  mysql-test/t/init_file.test@1.6.1.2, 2007-02-19 09:37:32+01:00, thek@kpdesk.mysql.com +9 -0
    Appended test case

  sql/sql_parse.cc@1.271.132.1, 2007-02-19 09:37:32+01:00, thek@kpdesk.mysql.com +1 -0
    Bug#23240 --init-file statements with NOW() reports '1970-01-01 11:00:00'as the date time
    
    - Starting time of a query sent by file bootstrapping wasn't initialized
      and starting time defaulted to 0. This later used value by the Now-
      item and is translated to 1970-01-01 11:00:00.
    - marking the time with thd->set_time() before the call to 
      mysql_parse resolves this issue.

ChangeSet@1.2216.71.43, 2007-02-17 23:52:17+01:00, jonas@perch.ndb.mysql.com +6 -0
  ndb - bug#26457
    master failure during master take over

  ndb/src/kernel/blocks/ERROR_codes.txt@1.26, 2007-02-17 23:52:15+01:00, jonas@perch.ndb.mysql.com +3 -1
    new error code

  ndb/src/kernel/blocks/dbdih/DbdihMain.cpp@1.55.1.12, 2007-02-17 23:52:15+01:00, jonas@perch.ndb.mysql.com +26 -1
    Make sure to clear NF_XX_LCP if master fails during master take-over

  ndb/test/include/NdbRestarter.hpp@1.5.1.1, 2007-02-17 23:52:15+01:00, jonas@perch.ndb.mysql.com +2 -0
    Add support for querying next master and node group
      (for multi node failure testing)

  ndb/test/ndbapi/testNodeRestart.cpp@1.24.1.3, 2007-02-17 23:52:15+01:00, jonas@perch.ndb.mysql.com +42 -0
    testcase

  ndb/test/run-test/daily-basic-tests.txt@1.41.1.7, 2007-02-17 23:52:15+01:00, jonas@perch.ndb.mysql.com +4 -0
    testcase

  ndb/test/src/NdbRestarter.cpp@1.12.1.1, 2007-02-17 23:52:15+01:00, jonas@perch.ndb.mysql.com +62 -0
    Add support for querying next master and node group
      (for multi node failure testing)

ChangeSet@1.2392.15.4, 2007-02-16 15:43:50-08:00, igor@olga.mysql.com +1 -0
  Adjusted results after fix for bug 25971.

  mysql-test/r/bdb.result@1.55, 2007-02-16 15:43:49-08:00, igor@olga.mysql.com +1 -1
    Adjusted results after fix for bug 25971.

ChangeSet@1.2392.15.3, 2007-02-16 14:30:25-08:00, igor@olga.mysql.com +1 -0
  Adjusted results after fix for bug 25971.

  mysql-test/r/bdb.result@1.54, 2007-02-16 14:30:23-08:00, igor@olga.mysql.com +1 -1
    Adjusted results after fix for bug 25971.

ChangeSet@1.2392.19.2, 2007-02-16 13:42:52-07:00, malff@weblab.(none) +4 -0
  Manual merge

  mysql-test/r/subselect.result@1.174, 2007-02-16 13:42:51-07:00, malff@weblab.(none) +125 -18
    Manual merge

  mysql-test/r/view.result@1.193, 2007-02-16 13:42:51-07:00, malff@weblab.(none) +121 -9
    Manual merge

  mysql-test/t/subselect.test@1.141, 2007-02-16 13:42:51-07:00, malff@weblab.(none) +93 -0
    Manual merge

  mysql-test/t/view.test@1.178, 2007-02-16 13:42:51-07:00, malff@weblab.(none) +89 -7
    Manual merge

ChangeSet@1.2216.71.42, 2007-02-16 18:20:24+01:00, jonas@perch.ndb.mysql.com +1 -0
  ndb - bug in my.cnf handling on resize of vector
    backport fix from 5.1

  ndb/src/mgmsrv/InitConfigFileParser.cpp@1.26.2.1, 2007-02-16 18:20:23+01:00, jonas@perch.ndb.mysql.com +7 -6
    backport fix from 5.1

ChangeSet@1.2216.71.41, 2007-02-16 18:10:27+01:00, jonas@perch.ndb.mysql.com +1 -0
  ndb - bug#26454
    make lockpages=1 run a bit earlier in startup

  ndb/src/kernel/blocks/ndbcntr/NdbcntrMain.cpp@1.32.1.1, 2007-02-16 18:10:25+01:00, jonas@perch.ndb.mysql.com +1 -1
    change order

ChangeSet@1.2377.42.1, 2007-02-16 19:39:28+03:00, evgen@moonbone.local +6 -0
  Bug#16630: The update fields of the INSERT .. SELECT .. ON DUPLICATE KEY
  UPDATE contains wrong data if the SELECT employs a temporary table.
  
  If the UPDATE values of the INSERT .. SELECT .. ON DUPLICATE KEY UPDATE
  statement contains fields from the SELECT part and the select employs a
  temporary table then those fields will contain wrong values because they
  aren't corrected to get data from the temporary table.
  
  The solution is to add these fields to the selects all_fields list,
  to store pointers to those fields in the selects ref_pointer_array and
  to access them via Item_ref objects.
  
  The substitution for Item_ref objects is done in the new function called 
  Item_field::update_value_transformer(). It is called through the
  item->transform() mechanism at the end of the select_insert::prepare()
  function.

  mysql-test/r/insert_select.result@1.45, 2007-02-16 19:38:47+03:00, evgen@moonbone.local +13 -0
    Added a test case for bug#16630: The update fields of the INSERT .. SELECT ..
    ON DUPLICATE KEY UPDATE contains wrong data if the SELECT employs a 
    temporary table.

  mysql-test/t/insert_select.test@1.37, 2007-02-16 19:38:50+03:00, evgen@moonbone.local +15 -0
    Added a test case for bug#16630: The update fields of the INSERT .. SELECT ..
    ON DUPLICATE KEY UPDATE contains wrong data if the SELECT employs a 
    temporary table.

  sql/item.cc@1.245.8.1, 2007-02-16 19:38:21+03:00, evgen@moonbone.local +45 -0
    Bug#16630: The update fields of the INSERT .. SELECT .. ON DUPLICATE KEY
    UPDATE contains wrong data if the SELECT employs a temporary table.
    The new method Item_field::update_value_transformer() is added. It
    substitutes fields in the update values list for references 
    (Item_ref objects) to them.

  sql/item.h@1.213.1.7, 2007-02-16 19:38:36+03:00, evgen@moonbone.local +2 -0
    Bug#16630: The update fields of the INSERT .. SELECT .. ON DUPLICATE KEY
    UPDATE contains wrong data if the SELECT employs a temporary table.
    The update_value_transformer() method is added to the Item and to the
    Item_field classes.

  sql/sql_insert.cc@1.211.4.4, 2007-02-16 19:38:40+03:00, evgen@moonbone.local +16 -0
    Bug#16630: The update fields of the INSERT .. SELECT .. ON DUPLICATE KEY
    UPDATE contains wrong data if the SELECT employs a temporary table.
    Traverse update values and substitute fields from the select for
    references (Item_ref objects) to them.

  sql/sql_select.cc@1.488.3.1, 2007-02-16 19:38:45+03:00, evgen@moonbone.local +3 -3
    Bug#16630: The update fields of the INSERT .. SELECT .. ON DUPLICATE KEY
    UPDATE contains wrong data if the SELECT employs a temporary table.
    Traverse update values and substitute fields from the select for
    references (Item_ref objects) to them.

ChangeSet@1.1346.893.4, 2007-02-16 16:31:31+01:00, joerg@trift2. +1 -0
  include/config-win.h  :  
  Companion change to this one
     ChangeSet@1.2206, 2007-01-22 02:32:07+02:00, jani@a88-113-38-195.elisa-laajakaista.fi +8 -0
       include/my_pthread.h@1.67, 2007-01-22 02:32:06+02:00, jani@a88-113-38-195.elisa-laajakaista.fi +31 -10
  which renamed "sigset()" -> "my_sigset()" but forgot to do it for Windows ...
  TAG: mysql-4.0.30

  include/config-win.h@1.23.1.15, 2007-02-16 16:31:29+01:00, joerg@trift2. +1 -1
    Companion change to this one
       ChangeSet@1.2206, 2007-01-22 02:32:07+02:00, jani@a88-113-38-195.elisa-laajakaista.fi +8 -0
         include/my_pthread.h@1.67, 2007-01-22 02:32:06+02:00, jani@a88-113-38-195.elisa-laajakaista.fi +31 -10
    which renamed "sigset()" -> "my_sigset()" but forgot to do it for Windows ...

ChangeSet@1.2392.1.29, 2007-02-16 16:08:08+01:00, msvensson@pilot.blaudden +1 -0
  Use " instead of ' to avoid win problem with '

  mysql-test/t/mysql.test@1.24.1.2, 2007-02-16 16:08:06+01:00, msvensson@pilot.blaudden +2 -2
    Use " instead of ' to avoid win problem with '

ChangeSet@1.2392.1.28, 2007-02-16 15:25:49+01:00, msvensson@pilot.blaudden +1 -0
  Add echo.c to be built on Windows

  client/CMakeLists.txt@1.5, 2007-02-16 15:25:48+01:00, msvensson@pilot.blaudden +2 -0
    Add echo.c to be built on Windows

ChangeSet@1.1616.2977.1, 2007-02-16 15:19:38+01:00, msvensson@neptunus.(none) +4 -0
  Workaround for problem where cygwin's bash/sh randomly fails with error 128 which 
  mainly occurs on win2003 64bit.
   - Execute "exec" commands directly with cmd.exe and replace "--exec echo ..." with "--exec .\echo.exe ..." 

  client/echo.c@1.1, 2007-02-16 15:19:35+01:00, msvensson@neptunus.(none) +45 -0
    New BitKeeper file ``client/echo.c''

  client/echo.c@1.0, 2007-02-16 15:19:35+01:00, msvensson@neptunus.(none) +0 -0

  client/mysqltest.c@1.92.25.1, 2007-02-16 15:19:35+01:00, msvensson@neptunus.(none) +84 -9
    Workaround the problem with "echo" in windows not behaving like "echo" in Unix.
    - Replace "--exec echo ..." with "--exec <path to mysqltest>\echo.exe" thus forcing
      use of our own echo implementation which baheves like on Unix.
    - The above change makes it possible to remove the need to execute all --exec's
      inside cygwin. Add ifdefs to only use use cygwin's bash conditionally  

  mysql-test/lib/mtr_misc.pl@1.5.1.6, 2007-02-16 15:19:35+01:00, msvensson@neptunus.(none) +11 -0
    Add function for converting to the OS's native format

  mysql-test/mysql-test-run.pl@1.8.20.3, 2007-02-16 15:19:35+01:00, msvensson@neptunus.(none) +21 -13
    Convert path to executables to "windows native" (c:\<path>\) instead of "mixed"(c:/<path>) mode
    necessary for pipes and redirects to work properly in cmd.exe

ChangeSet@1.2341.90.2, 2007-02-15 15:50:56+01:00, guilhem@gbichot3.local +2 -0
  Backport from the Falcon tree.
  When opening/creating the transaction coordinator's log, if binlog is
  used, the tc log is the binlog so we use the binlog's name; otherwise
  we use the mmap-based log, named after the mandatory argument of the
  --log-tc option (meant for that).

  sql/log.cc@1.200.1.1, 2007-02-15 15:50:54+01:00, guilhem@gbichot3.local +1 -1
    fixing wrong order of arguments to my_create()
    (3rd param is the desired modes of the file; "0" lead to no rights
    for anybody on the file).

  sql/mysqld.cc@1.582.7.5, 2007-02-15 15:50:54+01:00, guilhem@gbichot3.local +1 -1
    When opening/creating the transaction coordinator's log, if binlog is
    used, the tc log is the binlog so we use the binlog's name; otherwise
    we use the mmap-based log, named after the mandatory argument of the
    --log-tc option (meant for that).

ChangeSet@1.2341.90.1, 2007-02-15 15:39:03+01:00, guilhem@gbichot3.local +5 -0
  Fix for BUG#25507 "multi-row insert delayed + auto increment causes
  duplicate key entries on slave" (two concurrrent connections doing
  multi-row INSERT DELAYED to insert into an auto_increment column,
  caused replication slave to stop with "duplicate key error" (and
  binlog was wrong)), and BUG#26116 "If multi-row INSERT
  DELAYED has errors, statement-based binlogging breaks" (the binlog
  was not accounting for all rows inserted, or slave could stop).
  The fix is that: if (statement-based) binlogging is on, a multi-row
  INSERT DELAYED is silently converted to a non-delayed INSERT.
  Note: it is not possible to test BUG#25507 in 5.0 (requires mysqlslap),
  so it is tested only in the changeset for 5.1. However, BUG#26116
  is tested here, and the fix for BUG#25507 is the same code change.

  mysql-test/r/innodb-replace.result@1.3, 2007-02-15 15:39:01+01:00, guilhem@gbichot3.local +2 -2
    result update

  mysql-test/r/rpl_insert_delayed.result@1.1, 2007-02-15 15:39:01+01:00, guilhem@gbichot3.local +31 -0
    result. Master and slave match.

  mysql-test/r/rpl_insert_delayed.result@1.0, 2007-02-15 15:39:01+01:00, guilhem@gbichot3.local +0 -0

  mysql-test/t/innodb-replace.test@1.4, 2007-02-15 15:39:01+01:00, guilhem@gbichot3.local +2 -2
    now that multi-row delayed inserts are converted to normal inserts
    if the statement-based binlog is enabled,
    no error is issued even if this engine does not support INSERT DELAYED,
    as the insert does not go through the INSERT DELAYED code.
    To preserve the goal of this test, we change the statements to single-
    row inserts.

  mysql-test/t/rpl_insert_delayed.test@1.1, 2007-02-15 15:39:01+01:00, guilhem@gbichot3.local +67 -0
    Test for BUG#26116 (see if one error at first row on master makes the
    slave's data incorrect, see if one error at second row on master
    makes slave stop).

  mysql-test/t/rpl_insert_delayed.test@1.0, 2007-02-15 15:39:01+01:00, guilhem@gbichot3.local +0 -0

  sql/sql_insert.cc@1.211.5.2, 2007-02-15 15:39:01+01:00, guilhem@gbichot3.local +21 -0
    A multi-row INSERT DELAYED cannot be recorded to a statement-based
    binlog in a way that describes the insertions actually done;
    in that case we fallback to a non-delayed INSERT.

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.2392.14.2, 2007-02-15 11:17:25+01:00, msvensson@pilot.mysql.com +1 -0
  Remove the newly added space in error message, should not be there

  sql/share/errmsg.txt@1.75.1.2, 2007-02-15 11:17:23+01:00, msvensson@pilot.mysql.com +1 -1
    Remove the newly added space in error message, should not be there

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.2392.15.1, 2007-02-14 22:06:41-08:00, igor@olga.mysql.com +7 -0
  Fixed bug #25971: indexes on text columns were ignored when ref accesses
  were evaluated.
  According to the new rules for string comparison partial indexes on text
  columns can be used in the same cases when partial indexes on varchar
  columns can be used.

  mysql-test/r/endspace.result@1.11, 2007-02-14 22:06:38-08:00, igor@olga.mysql.com +1 -1
    Adjusted results after the fix for bug #25971.

  mysql-test/r/innodb.result@1.164, 2007-02-14 22:06:39-08:00, igor@olga.mysql.com +1 -1
    Adjusted results after the fix for bug #25971.

  mysql-test/r/myisam.result@1.98, 2007-02-14 22:06:39-08:00, igor@olga.mysql.com +1 -1
    Adjusted results after the fix for bug #25971.

  mysql-test/r/select.result@1.151, 2007-02-14 22:06:39-08:00, igor@olga.mysql.com +148 -0
    Added a test case for bug #25971.

  mysql-test/r/type_blob.result@1.53.1.1, 2007-02-14 22:06:39-08:00, igor@olga.mysql.com +2 -2
    Adjusted results after the fix for bug #25971.

  mysql-test/t/select.test@1.125, 2007-02-14 22:06:39-08:00, igor@olga.mysql.com +46 -0
    Added a test case for bug #25971.

  sql/sql_select.cc@1.490.1.1, 2007-02-14 22:06:39-08:00, igor@olga.mysql.com +1 -7
    Fixed bug #25971: indexes on text columns were ignored when ref accesses
    were evaluated.
    According to the new rules for string comparison partial indexes on text
    columns can be used in the same cases when partial indexes on varchar
    columns can be used.

ChangeSet@1.2392.14.1, 2007-02-14 19:31:06+01:00, msvensson@pilot.mysql.com +2 -0
  Add check of format specifiers in error message strings
  Update error message text accordingly to be equal between all translations

  extra/comp_err.c@1.26, 2007-02-14 19:31:02+01:00, msvensson@pilot.mysql.com +120 -0
    Add check of format specifiers in error message strings

  sql/share/errmsg.txt@1.75.1.1, 2007-02-14 19:31:03+01:00, msvensson@pilot.mysql.com +541 -541
    Update error messages after checks

ChangeSet@1.2392.13.1, 2007-02-14 18:35:59+02:00, gkodinov@macbook.gmz +3 -0
  Bug#19717: The blackhole engine is returning an OK flag in 
  index_read(), whereas it must return HA_ERR_END_OF_FILE
  instead (as there are by definition no rows in a table of 
  that engine.

  mysql-test/r/blackhole.result@1.11, 2007-02-14 18:35:52+02:00, gkodinov@macbook.gmz +11 -0
    Bug#19717: test case

  mysql-test/t/blackhole.test@1.9, 2007-02-14 18:35:53+02:00, gkodinov@macbook.gmz +15 -0
    Bug#19717: test case

  sql/ha_blackhole.cc@1.26, 2007-02-14 18:35:54+02:00, gkodinov@macbook.gmz +1 -1
    Bug#19717: return no rows instead of success.

ChangeSet@1.1616.2972.5, 2007-02-14 16:49:41+01:00, msvensson@pilot.mysql.com +1 -0
  Use my_vsnprintf instead of vsnprintf

  client/mysqltest.c@1.92.21.41, 2007-02-14 16:49:40+01:00, msvensson@pilot.mysql.com +1 -1
    Use my_vsnprintf instead of vsnprintf

ChangeSet@1.2385.7.2, 2007-02-14 14:44:34+01:00, msvensson@pilot.mysql.com +17 -0
  Bug#18628 mysql-test-run: security problem(part1)
   - Implement --secure-file-priv=<dir> option that limits
    "load_file", "LOAD DATA" and "SELECT .. INTO OUTFILE" to work 
    with files in specified dir.
   - Use above option for mysqld in mysql-test-run.pl 

  mysql-test/mysql-test-run.pl@1.191.1.1, 2007-02-14 14:44:30+01:00, msvensson@pilot.mysql.com +6 -0
    Add usage of --secure-file-priv=vardir when starting mysqld

  mysql-test/r/loaddata.result@1.25, 2007-02-14 14:44:30+01:00, msvensson@pilot.mysql.com +16 -0
    Update test result after adding test to check that secure-file-priv
    works for "load data" and "load_file"

  mysql-test/r/outfile.result@1.7, 2007-02-14 14:44:30+01:00, msvensson@pilot.mysql.com +6 -1
    Update result

  mysql-test/r/query_cache.result@1.78, 2007-02-14 14:44:30+01:00, msvensson@pilot.mysql.com +1 -1
    Can't load from outside of vardir anymore

  mysql-test/r/type_blob.result@1.54, 2007-02-14 14:44:30+01:00, msvensson@pilot.mysql.com +12 -12
    Can't load from outside of vardir anymore

  mysql-test/t/loaddata.test@1.19, 2007-02-14 14:44:30+01:00, msvensson@pilot.mysql.com +23 -0
    Update test result after adding test to check that secure-file-priv 
    works for "load data" and "load_file"

  mysql-test/t/outfile.test@1.15, 2007-02-14 14:44:30+01:00, msvensson@pilot.mysql.com +12 -0
    Update test result after adding test to check that secure-file-priv
    works for "SELECT .. INTO OUTFILE"

  mysql-test/t/query_cache.test@1.57, 2007-02-14 14:44:30+01:00, msvensson@pilot.mysql.com +2 -2
    Can't load from outside of vardir anymore

  mysql-test/t/type_blob.test@1.34, 2007-02-14 14:44:31+01:00, msvensson@pilot.mysql.com +13 -14
    Can't load from outside of vardir anymore

  sql/item_strfunc.cc@1.292.3.1, 2007-02-14 14:44:31+01:00, msvensson@pilot.mysql.com +5 -0
    Check that the path "load_file" uses for the file is within 
    what's specified with --secure-file-priv

  sql/mysql_priv.h@1.429.9.1, 2007-02-14 14:44:31+01:00, msvensson@pilot.mysql.com +1 -0
    Add secure_file_priv

  sql/mysqld.cc@1.582.15.1, 2007-02-14 14:44:31+01:00, msvensson@pilot.mysql.com +19 -1
    Add "--secure_file_priv"

  sql/set_var.cc@1.176.2.1, 2007-02-14 14:44:31+01:00, msvensson@pilot.mysql.com +4 -0
    Add variable "secure_file_priv" to "show variables"

  sql/share/errmsg.txt@1.76, 2007-02-14 14:44:32+01:00, msvensson@pilot.mysql.com +1 -1
    Fix swedish error message for ER_OPTION_PREVENTS_STATMENT wich was hardcoded
    to --skip-grant-tables

  sql/sql_class.cc@1.256.3.1, 2007-02-14 14:44:31+01:00, msvensson@pilot.mysql.com +10 -2
    Check that the path "load_file" uses for the file is within 
    what's specified with --secure-file-priv

  sql/sql_class.h@1.314.3.1, 2007-02-14 14:44:31+01:00, msvensson@pilot.mysql.com +1 -1
    Fix spelling error

  sql/sql_load.cc@1.102.1.3, 2007-02-14 14:44:31+01:00, msvensson@pilot.mysql.com +9 -0
    Check that the path "load_file" uses for the file is within 
    what's specified with --secure-file-priv

ChangeSet@1.2392.11.3, 2007-02-14 15:33:48+07:00, tomas@poseidon.mysql.com +2 -0
  ndb_config_4_node.ini, ndb_config_1_node.ini:
    new file

  mysql-test/ndb/ndb_config_1_node.ini@1.1, 2007-02-14 15:27:30+07:00, tomas@poseidon.mysql.com +43 -0

  mysql-test/ndb/ndb_config_1_node.ini@1.0, 2007-02-14 15:27:30+07:00, tomas@poseidon.mysql.com +0 -0
    BitKeeper file /home/tomas/mysql-5.0-ndb/mysql-test/ndb/ndb_config_1_node.ini

  mysql-test/ndb/ndb_config_4_node.ini@1.1, 2007-02-14 15:27:33+07:00, tomas@poseidon.mysql.com +52 -0

  mysql-test/ndb/ndb_config_4_node.ini@1.0, 2007-02-14 15:27:33+07:00, tomas@poseidon.mysql.com +0 -0
    BitKeeper file /home/tomas/mysql-5.0-ndb/mysql-test/ndb/ndb_config_4_node.ini

ChangeSet@1.2392.11.2, 2007-02-14 15:26:06+07:00, tomas@poseidon.mysql.com +4 -0
      backport some mysql-test ndbcluster things from 5.1
      remove compiler warning EventLogger.cpp
      Bug#26176 NdbObjectIdMap::expand unable to expand!! mysqld got signal 11
       - partial fix
       - object map to handle failed realloc
  

  mysql-test/ndb/ndb_config_2_node.ini@1.16, 2007-02-14 15:25:51+07:00, tomas@poseidon.mysql.com +10 -0
    backport some mysql-test ndbcluster things from 5.1

  mysql-test/ndb/ndbcluster.sh@1.48, 2007-02-14 15:25:51+07:00, tomas@poseidon.mysql.com +65 -32
    backport some mysql-test ndbcluster things from 5.1

  ndb/src/common/debugger/EventLogger.cpp@1.32, 2007-02-14 15:25:51+07:00, tomas@poseidon.mysql.com +2 -2
    remove compiler warning

  ndb/src/ndbapi/ObjectMap.hpp@1.10, 2007-02-14 15:25:52+07:00, tomas@poseidon.mysql.com +7 -6
    Bug#26176 NdbObjectIdMap::expand unable to expand!! mysqld got signal 11
     - partial fix
     - object map to handle failed realloc

ChangeSet@1.2377.39.3, 2007-02-14 15:16:26+07:00, tomas@poseidon.mysql.com +1 -0
  Bug #21033 Error 0 in readAutoIncrementValue()
  - do not call function if table has no autoincrement

  sql/ha_ndbcluster.cc@1.291.5.1, 2007-02-14 15:16:01+07:00, tomas@poseidon.mysql.com +1 -1
    Bug #21033 Error 0 in readAutoIncrementValue()
    - do not call function if table has no autoincrement

ChangeSet@1.2377.40.7, 2007-02-14 16:03:25+11:00, stewart@willster.(none) +25 -0
  BUG#26358  	remove unused and non-working SET_VAR_REQ/CONF signals
  
  remove SET_VAR_REQ,REF,CONF - unused, #if 0 and confusing
  
  Remove the dead SET_VAR_REQ,REF,CONF signals.
  
  They:
  a) don't currently work
  b) will cause confusion with future mgmd updates for
     signal interface to configuration things (e.g. port numbers)

  ndb/include/kernel/GlobalSignalNumbers.h@1.20, 2007-02-14 16:03:22+11:00, stewart@willster.(none) +3 -3
    remove SET_VAR_REQ,REF,CONF - unused, #if 0 and confusing
    
    Remove the dead SET_VAR_REQ,REF,CONF signals.
    
    They:
    a) don't currently work
    b) will cause confusion with future mgmd updates for
       signal interface to configuration things (e.g. port numbers)

  ndb/src/common/debugger/signaldata/SignalNames.cpp@1.13, 2007-02-14 16:03:22+11:00, stewart@willster.(none) +0 -3
    remove SET_VAR_REQ,REF,CONF - unused, #if 0 and confusing
    
    Remove the dead SET_VAR_REQ,REF,CONF signals.
    
    They:
    a) don't currently work
    b) will cause confusion with future mgmd updates for
       signal interface to configuration things (e.g. port numbers)

  ndb/src/kernel/blocks/cmvmi/Cmvmi.cpp@1.28.2.3, 2007-02-14 16:03:22+11:00, stewart@willster.(none) +0 -157
    remove SET_VAR_REQ,REF,CONF - unused, #if 0 and confusing
    
    Remove the dead SET_VAR_REQ,REF,CONF signals.
    
    They:
    a) don't currently work
    b) will cause confusion with future mgmd updates for
       signal interface to configuration things (e.g. port numbers)

  ndb/src/kernel/blocks/cmvmi/Cmvmi.hpp@1.7, 2007-02-14 16:03:22+11:00, stewart@willster.(none) +0 -5
    remove SET_VAR_REQ,REF,CONF - unused, #if 0 and confusing
    
    Remove the dead SET_VAR_REQ,REF,CONF signals.
    
    They:
    a) don't currently work
    b) will cause confusion with future mgmd updates for
       signal interface to configuration things (e.g. port numbers)

  ndb/src/kernel/blocks/dbacc/Dbacc.hpp@1.25, 2007-02-14 16:03:22+11:00, stewart@willster.(none) +0 -1
    remove SET_VAR_REQ,REF,CONF - unused, #if 0 and confusing
    
    Remove the dead SET_VAR_REQ,REF,CONF signals.
    
    They:
    a) don't currently work
    b) will cause confusion with future mgmd updates for
       signal interface to configuration things (e.g. port numbers)

  ndb/src/kernel/blocks/dbacc/DbaccInit.cpp@1.18, 2007-02-14 16:03:22+11:00, stewart@willster.(none) +0 -1
    remove SET_VAR_REQ,REF,CONF - unused, #if 0 and confusing
    
    Remove the dead SET_VAR_REQ,REF,CONF signals.
    
    They:
    a) don't currently work
    b) will cause confusion with future mgmd updates for
       signal interface to configuration things (e.g. port numbers)

  ndb/src/kernel/blocks/dbacc/DbaccMain.cpp@1.62, 2007-02-14 16:03:22+11:00, stewart@willster.(none) +0 -27
    remove SET_VAR_REQ,REF,CONF - unused, #if 0 and confusing
    
    Remove the dead SET_VAR_REQ,REF,CONF signals.
    
    They:
    a) don't currently work
    b) will cause confusion with future mgmd updates for
       signal interface to configuration things (e.g. port numbers)

  ndb/src/kernel/blocks/dbdih/Dbdih.hpp@1.14.1.2, 2007-02-14 16:03:22+11:00, stewart@willster.(none) +0 -1
    remove SET_VAR_REQ,REF,CONF - unused, #if 0 and confusing
    
    Remove the dead SET_VAR_REQ,REF,CONF signals.
    
    They:
    a) don't currently work
    b) will cause confusion with future mgmd updates for
       signal interface to configuration things (e.g. port numbers)

  ndb/src/kernel/blocks/dbdih/DbdihInit.cpp@1.15, 2007-02-14 16:03:22+11:00, stewart@willster.(none) +0 -1
    remove SET_VAR_REQ,REF,CONF - unused, #if 0 and confusing
    
    Remove the dead SET_VAR_REQ,REF,CONF signals.
    
    They:
    a) don't currently work
    b) will cause confusion with future mgmd updates for
       signal interface to configuration things (e.g. port numbers)

  ndb/src/kernel/blocks/dbdih/DbdihMain.cpp@1.65.1.1, 2007-02-14 16:03:22+11:00, stewart@willster.(none) +0 -24
    remove SET_VAR_REQ,REF,CONF - unused, #if 0 and confusing
    
    Remove the dead SET_VAR_REQ,REF,CONF signals.
    
    They:
    a) don't currently work
    b) will cause confusion with future mgmd updates for
       signal interface to configuration things (e.g. port numbers)

  ndb/src/kernel/blocks/dblqh/Dblqh.hpp@1.41.1.2, 2007-02-14 16:03:23+11:00, stewart@willster.(none) +0 -1
    remove SET_VAR_REQ,REF,CONF - unused, #if 0 and confusing
    
    Remove the dead SET_VAR_REQ,REF,CONF signals.
    
    They:
    a) don't currently work
    b) will cause confusion with future mgmd updates for
       signal interface to configuration things (e.g. port numbers)

  ndb/src/kernel/blocks/dblqh/DblqhInit.cpp@1.18, 2007-02-14 16:03:23+11:00, stewart@willster.(none) +0 -1
    remove SET_VAR_REQ,REF,CONF - unused, #if 0 and confusing
    
    Remove the dead SET_VAR_REQ,REF,CONF signals.
    
    They:
    a) don't currently work
    b) will cause confusion with future mgmd updates for
       signal interface to configuration things (e.g. port numbers)

  ndb/src/kernel/blocks/dblqh/DblqhMain.cpp@1.97.1.2, 2007-02-14 16:03:23+11:00, stewart@willster.(none) +0 -24
    remove SET_VAR_REQ,REF,CONF - unused, #if 0 and confusing
    
    Remove the dead SET_VAR_REQ,REF,CONF signals.
    
    They:
    a) don't currently work
    b) will cause confusion with future mgmd updates for
       signal interface to configuration things (e.g. port numbers)

  ndb/src/kernel/blocks/dbtc/Dbtc.hpp@1.36.1.3, 2007-02-14 16:03:23+11:00, stewart@willster.(none) +0 -1
    remove SET_VAR_REQ,REF,CONF - unused, #if 0 and confusing
    
    Remove the dead SET_VAR_REQ,REF,CONF signals.
    
    They:
    a) don't currently work
    b) will cause confusion with future mgmd updates for
       signal interface to configuration things (e.g. port numbers)

  ndb/src/kernel/blocks/dbtc/DbtcInit.cpp@1.15, 2007-02-14 16:03:23+11:00, stewart@willster.(none) +0 -1
    remove SET_VAR_REQ,REF,CONF - unused, #if 0 and confusing
    
    Remove the dead SET_VAR_REQ,REF,CONF signals.
    
    They:
    a) don't currently work
    b) will cause confusion with future mgmd updates for
       signal interface to configuration things (e.g. port numbers)

  ndb/src/kernel/blocks/dbtc/DbtcMain.cpp@1.104, 2007-02-14 16:03:23+11:00, stewart@willster.(none) +0 -30
    remove SET_VAR_REQ,REF,CONF - unused, #if 0 and confusing
    
    Remove the dead SET_VAR_REQ,REF,CONF signals.
    
    They:
    a) don't currently work
    b) will cause confusion with future mgmd updates for
       signal interface to configuration things (e.g. port numbers)

  ndb/src/kernel/blocks/dbtup/Dbtup.hpp@1.28.1.2, 2007-02-14 16:03:23+11:00, stewart@willster.(none) +0 -1
    remove SET_VAR_REQ,REF,CONF - unused, #if 0 and confusing
    
    Remove the dead SET_VAR_REQ,REF,CONF signals.
    
    They:
    a) don't currently work
    b) will cause confusion with future mgmd updates for
       signal interface to configuration things (e.g. port numbers)

  ndb/src/kernel/blocks/dbtup/DbtupGen.cpp@1.22, 2007-02-14 16:03:23+11:00, stewart@willster.(none) +0 -28
    remove SET_VAR_REQ,REF,CONF - unused, #if 0 and confusing
    
    Remove the dead SET_VAR_REQ,REF,CONF signals.
    
    They:
    a) don't currently work
    b) will cause confusion with future mgmd updates for
       signal interface to configuration things (e.g. port numbers)

  ndb/src/kernel/blocks/ndbcntr/Ndbcntr.hpp@1.6.1.2, 2007-02-14 16:03:23+11:00, stewart@willster.(none) +0 -1
    remove SET_VAR_REQ,REF,CONF - unused, #if 0 and confusing
    
    Remove the dead SET_VAR_REQ,REF,CONF signals.
    
    They:
    a) don't currently work
    b) will cause confusion with future mgmd updates for
       signal interface to configuration things (e.g. port numbers)

  ndb/src/kernel/blocks/ndbcntr/NdbcntrInit.cpp@1.11, 2007-02-14 16:03:23+11:00, stewart@willster.(none) +0 -1
    remove SET_VAR_REQ,REF,CONF - unused, #if 0 and confusing
    
    Remove the dead SET_VAR_REQ,REF,CONF signals.
    
    They:
    a) don't currently work
    b) will cause confusion with future mgmd updates for
       signal interface to configuration things (e.g. port numbers)

  ndb/src/kernel/blocks/ndbcntr/NdbcntrMain.cpp@1.34.1.2, 2007-02-14 16:03:23+11:00, stewart@willster.(none) +0 -17
    remove SET_VAR_REQ,REF,CONF - unused, #if 0 and confusing
    
    Remove the dead SET_VAR_REQ,REF,CONF signals.
    
    They:
    a) don't currently work
    b) will cause confusion with future mgmd updates for
       signal interface to configuration things (e.g. port numbers)

  ndb/src/kernel/blocks/qmgr/Qmgr.hpp@1.11.1.3, 2007-02-14 16:03:23+11:00, stewart@willster.(none) +0 -1
    remove SET_VAR_REQ,REF,CONF - unused, #if 0 and confusing
    
    Remove the dead SET_VAR_REQ,REF,CONF signals.
    
    They:
    a) don't currently work
    b) will cause confusion with future mgmd updates for
       signal interface to configuration things (e.g. port numbers)

  ndb/src/kernel/blocks/qmgr/QmgrInit.cpp@1.10, 2007-02-14 16:03:23+11:00, stewart@willster.(none) +0 -1
    remove SET_VAR_REQ,REF,CONF - unused, #if 0 and confusing
    
    Remove the dead SET_VAR_REQ,REF,CONF signals.
    
    They:
    a) don't currently work
    b) will cause confusion with future mgmd updates for
       signal interface to configuration things (e.g. port numbers)

  ndb/src/kernel/blocks/qmgr/QmgrMain.cpp@1.36.1.3, 2007-02-14 16:03:23+11:00, stewart@willster.(none) +0 -28
    remove SET_VAR_REQ,REF,CONF - unused, #if 0 and confusing
    
    Remove the dead SET_VAR_REQ,REF,CONF signals.
    
    They:
    a) don't currently work
    b) will cause confusion with future mgmd updates for
       signal interface to configuration things (e.g. port numbers)

  ndb/src/mgmsrv/MgmtSrvr.hpp@1.48.1.2, 2007-02-14 16:03:23+11:00, stewart@willster.(none) +0 -1
    remove SET_VAR_REQ,REF,CONF - unused, #if 0 and confusing
    
    Remove the dead SET_VAR_REQ,REF,CONF signals.
    
    They:
    a) don't currently work
    b) will cause confusion with future mgmd updates for
       signal interface to configuration things (e.g. port numbers)

ChangeSet@1.2377.40.6, 2007-02-14 15:55:08+11:00, stewart@willster.(none) +4 -0
  BUG#26357  	remove unused GSN_STATISTICS_REQ and CONF
  
  remove GSN_STATISTICS_REQ and CONF
  
  These are unused and have been since BK import. not needed.

  ndb/include/kernel/GlobalSignalNumbers.h@1.19, 2007-02-14 15:55:06+11:00, stewart@willster.(none) +2 -2
    remove STATISTICS_REQ and CONF

  ndb/src/common/debugger/signaldata/SignalNames.cpp@1.12, 2007-02-14 15:55:06+11:00, stewart@willster.(none) +1 -3
    remove signal names for STATISTICS_REQ and CONF (unused)

  ndb/src/kernel/blocks/cmvmi/Cmvmi.cpp@1.28.2.2, 2007-02-14 15:55:06+11:00, stewart@willster.(none) +0 -19
    remove unused STATISTICS signals

  ndb/src/kernel/blocks/cmvmi/Cmvmi.hpp@1.6, 2007-02-14 15:55:06+11:00, stewart@willster.(none) +0 -1
    remove unused STATISTICS signals

ChangeSet@1.2377.40.5, 2007-02-14 15:51:16+11:00, stewart@willster.(none) +1 -0
  BUG#26356  	uninitialised data sent from TAMPER_ORD to DIHNDBTAMPER
  
  Don't send uninit data in TAMPER_ORD to DIHNDBTAMPER
  
  Even though this data is unused from the CMVMI (mgmd) signal,
  we shouldn't be doing stuff with uninited data.

  ndb/src/kernel/blocks/cmvmi/Cmvmi.cpp@1.28.2.1, 2007-02-14 15:51:14+11:00, stewart@willster.(none) +1 -1
    init the 3rd word of DIHNDBTAMPER before sending to DIH.

ChangeSet@1.2377.40.4, 2007-02-14 15:47:34+11:00, stewart@willster.(none) +2 -0
  BUG#26355  	FIXME: use constant for max loglevel in ndb_mgmd

  ndb/include/mgmapi/mgmapi.h@1.55, 2007-02-14 15:47:33+11:00, stewart@willster.(none) +2 -0
    use constant for max log level in ndb_mgmd.
    
    (more useful in 5.1 due to other defines and refinements of mgmapi)

  ndb/src/mgmsrv/Services.cpp@1.72.1.3, 2007-02-14 15:47:33+11:00, stewart@willster.(none) +3 -5
    fix the XXX fixme of constant for max log level

ChangeSet@1.2377.40.3, 2007-02-14 15:35:29+11:00, stewart@willster.(none) +2 -0
  BUG#26353 remove GET_CONFIG_BACKWARDS_COMPAT from ndb_mgmd
  
  there is backwards compatibility for GET CONFIG style configuration requests in
  ndb_mgmd. None of the ndbd versions that use this couldn't possibly connect to a
  5.0 or 5.1 cluster. remove the backwards compat
  
  remove it

  ndb/src/mgmsrv/Services.cpp@1.72.1.2, 2007-02-14 15:35:27+11:00, stewart@willster.(none) +3 -83
    remove MGM_GET_CONFIG_BACKWARDS_COMPAT code.
    
    any client using GET CONFIG will just not work with modern NDB.

  ndb/src/mgmsrv/Services.hpp@1.23, 2007-02-14 15:35:27+11:00, stewart@willster.(none) +0 -9
    remove GET CONFIG support

ChangeSet@1.2377.40.2, 2007-02-14 15:28:04+11:00, stewart@willster.(none) +1 -0
  BUG#26352  	unused ndb_mgm_rep_command in mgmapi.cpp

  ndb/src/mgmapi/mgmapi.cpp@1.66.1.3, 2007-02-14 15:28:02+11:00, stewart@willster.(none) +0 -37
    remove ndb_mgm_rep_command function

ChangeSet@1.2377.40.1, 2007-02-14 15:22:03+11:00, stewart@willster.(none) +2 -0
  WL#3704 mgmapi timeouts (and cleanups)
  
  indicate units in SocketOutputStream timeout
  
  rename timeout in SocketOutputStream to reflect units (ms)
  
  In 5.0 as well as is safe cleanup patch that will help with merging.

  ndb/include/util/OutputStream.hpp@1.4.1.2, 2007-02-14 15:22:00+11:00, stewart@willster.(none) +3 -3
    rename timeout in SocketOutputStream to reflect units (ms)

  ndb/src/common/util/OutputStream.cpp@1.6, 2007-02-14 15:22:00+11:00, stewart@willster.(none) +4 -4
    rename timeout in SocketOutputStream to reflect units (ms)

ChangeSet@1.2377.39.2, 2007-02-14 11:16:10+07:00, tomas@poseidon.mysql.com +2 -0
  make sure some printouts in ndbd out file is done with g_eventLogger

  ndb/src/kernel/blocks/dbdih/DbdihMain.cpp@1.66, 2007-02-14 11:16:04+07:00, tomas@poseidon.mysql.com +66 -64
    make sure some printouts in ndbd out file is done with g_eventLogger

  ndb/src/kernel/vm/WatchDog.cpp@1.6, 2007-02-14 11:16:04+07:00, tomas@poseidon.mysql.com +5 -2
    make sure some printouts in ndbd out file is done with g_eventLogger

ChangeSet@1.2377.39.1, 2007-02-14 11:05:38+07:00, tomas@poseidon.mysql.com +7 -0
  Bug#26293 cluster mgmt node sometimes doesn't receive events from all nodes on restart
  - signals where sometimes sent too early when setting up subscriptions

  ndb/include/kernel/signaldata/DumpStateOrd.hpp@1.11, 2007-02-14 11:05:31+07:00, tomas@poseidon.mysql.com +4 -0
    added dump for active subscriptions in cmvmi

  ndb/src/kernel/blocks/cmvmi/Cmvmi.cpp@1.28.1.3, 2007-02-14 11:05:31+07:00, tomas@poseidon.mysql.com +19 -1
    added dump for active subscriptions in cmvmi

  ndb/src/mgmsrv/MgmtSrvr.cpp@1.110.2.2, 2007-02-14 11:05:31+07:00, tomas@poseidon.mysql.com +74 -20
    bug in that signals where sent prior to api reg conf arrived, causing thrown away signals and subsequent hangs in mgmtserver
    also add retry if node connected but not yet received api reg conf

  ndb/src/ndbapi/ClusterMgr.cpp@1.32, 2007-02-14 11:05:31+07:00, tomas@poseidon.mysql.com +4 -1
    added status variable m_api_reg_conf in cluster manager to correctly be able to determine if a node is sendable

  ndb/src/ndbapi/ClusterMgr.hpp@1.11.1.3, 2007-02-14 11:05:31+07:00, tomas@poseidon.mysql.com +1 -0
    added status variable m_api_reg_conf in cluster manager to correctly be able to determine if a node is sendable

  ndb/src/ndbapi/SignalSender.cpp@1.6.1.3, 2007-02-14 11:05:31+07:00, tomas@poseidon.mysql.com +2 -0
    assert to see that node is sendable when signal is sent

  ndb/src/ndbapi/SignalSender.hpp@1.3, 2007-02-14 11:05:31+07:00, tomas@poseidon.mysql.com +1 -1
    manke metchd const

ChangeSet@1.1616.2972.4, 2007-02-13 18:59:46+01:00, msvensson@pilot.mysql.com +1 -0
  Write some debug info to result log file before dying in 'do_exec'

  client/mysqltest.c@1.92.21.40, 2007-02-13 18:59:45+01:00, msvensson@pilot.mysql.com +27 -0
    Write some debug info to result log file before dying in 'do_exec'

ChangeSet@1.1616.2972.3, 2007-02-13 16:59:58+01:00, msvensson@pilot.mysql.com +1 -0
  Reset value of variable "escaped" in "default" label causing $variables not
  to be expanded in same cases 

  client/mysqltest.c@1.92.21.39, 2007-02-13 16:59:57+01:00, msvensson@pilot.mysql.com +1 -0
    Reset value of variable "escaped" in "default" label 

ChangeSet@1.2377.4.12, 2007-02-12 13:59:29-07:00, malff@weblab.(none) +7 -0
  Bug#24532 (The return data type of IS TRUE is different from similar
    operations)
  
  Before this change, the boolean predicates:
  - X IS TRUE,
  - X IS NOT TRUE,
  - X IS FALSE,
  - X IS NOT FALSE
  were implemented by expanding the Item tree in the parser, by using a
  construct like:
  Item_func_if(Item_func_ifnull(X, <value>), <value>, <value>)
  
  Each <value> was a constant integer, either 0 or 1.
  
  A bug in the implementation of the function IF(a, b, c), in
  Item_func_if::fix_length_and_dec(), would cause the following :
  
  When the arguments b and c are both unsigned, the result type of the
  function was signed, instead of unsigned.
  
  When the result of the if function is signed, space for the sign could be
  counted twice (in the max() expression for a signed argument, and in the
  total), causing the member max_length to be too high.
  
  An effect of this is that the final type of IF(x, int(1), int(1)) would be
  int(2) instead of int(1).
  
  With this fix, the problems found in Item_func_if::fix_length_and_dec()
  have been fixed.
  
  While it's semantically correct to represent 'X IS TRUE' with
  Item_func_if(Item_func_ifnull(X, <value>), <value>, <value>),
  there are however more problems with this construct.
  
  a)
  Building the parse tree involves :
  - creating 5 Item instances (3 ints, 1 ifnull, 1 if),
  - creating each Item calls my_pthread_getspecific_ptr() once in the operator
    new(size), and a second time in the Item::Item() constructor, resulting
    in a total of 10 calls to get the current thread.
  Evaluating the expression involves evaluating up to 4 nodes at runtime.
  This representation could be greatly simplified and improved.
  
  b)
  Transforming the parse tree internally with if(ifnull(...)) is fine as long
  as this transformation is internal to the server implementation.
  With views however, the result of the parse tree is later exposed by the
  ::print() functions, and stored as part of the view definition.
  Doing this has long term consequences:
  
  1)
  The original semantic 'X IS TRUE' is lost, and replaced by the
  if(ifnull(...)) expression. As a result, SHOW CREATE VIEW does not restore
  the original code.
  
  2)
  Should a future version of MySQL implement the SQL BOOLEAN data type for
  example, views created today using 'X IS NULL' can be exported using
  mysqldump, and imported again. Such views would be converted correctly and
  automatically to use a BOOLEAN column in the future version.
  With 'X IS TRUE' and the current implementations, views using these
  "boolean" predicates would not be converted during the export/import, and
  would use integer columns instead.
  The difference traces back to how SHOW CREATE VIEW preserves 'X IS NULL' but
  does not preserve the 'X IS TRUE' semantic.
  
  With this fix, internal representation of 'X IS TRUE' booleans predicates
  has changed, so that:
  - dedicated Item classes are created for each predicate,
  - only 1 Item is created to represent 1 predicate
  - my_pthread_getspecific_ptr() is invoked 1 time instead of 10
  - SHOW CREATE VIEW preserves the original semantic, and prints 'X IS TRUE'.
  
  Note that, because of the fix in Item_func_if, views created before this fix
  will:
  - correctly use a int(1) type instead of int(2) for boolean predicates,
  - incorrectly print the if(ifnull(...), ...) expression in SHOW CREATE VIEW,
  since the original semantic (X IS TRUE) has been lost.
  - except for the syntax used in SHOW CREATE VIEW, these views will operate
  properly, no action is needed.
  
  Views created after this fix will operate correctly, and will preserve the
  original code semantic in SHOW CREATE VIEW.

  mysql-test/r/func_if.result@1.24, 2007-02-12 13:59:26-07:00, malff@weblab.(none) +3 -0
    IF(x, unsigned, unsigned) should be unsigned.

  mysql-test/r/view.result@1.186.1.2, 2007-02-12 13:59:26-07:00, malff@weblab.(none) +125 -0
    Preserve the semantic of 'X IS [NOT] (TRUE|FALSE)' boolean predicates.

  mysql-test/t/func_if.test@1.22, 2007-02-12 13:59:26-07:00, malff@weblab.(none) +11 -0
    IF(x, unsigned, unsigned) should be unsigned.

  mysql-test/t/view.test@1.171.1.2, 2007-02-12 13:59:26-07:00, malff@weblab.(none) +86 -0
    Preserve the semantic of 'X IS [NOT] (TRUE|FALSE)' boolean predicates.

  sql/item_cmpfunc.cc@1.228.5.1, 2007-02-12 13:59:26-07:00, malff@weblab.(none) +68 -6
    Preserve the semantic of 'X IS [NOT] (TRUE|FALSE)' boolean predicates.
    IF(x, unsigned, unsigned) should be unsigned.

  sql/item_cmpfunc.h@1.136.4.1, 2007-02-12 13:59:26-07:00, malff@weblab.(none) +86 -0
    Preserve the semantic of 'X IS [NOT] (TRUE|FALSE)' boolean predicates.

  sql/sql_yacc.yy@1.498.3.6, 2007-02-12 13:59:26-07:00, malff@weblab.(none) +12 -16
    Preserve the semantic of 'X IS [NOT] (TRUE|FALSE)' boolean predicates.

ChangeSet@1.1346.893.3, 2007-02-12 20:13:34+01:00, joerg@trift2. +2 -0
  Fix a linkage problem with the previous patch for "thr_client_alarm".

  mysys/my_pthread.c@1.35.1.9, 2007-02-12 20:13:34+01:00, joerg@trift2. +1 -0
    Linkage problem with previous patch: "thr_client_alarm" must be declared in here.

  mysys/thr_alarm.c@1.41.1.4, 2007-02-12 20:13:34+01:00, joerg@trift2. +0 -1
    Linkage problem: Declare "thr_client_alarm" over in "mysys/my_pthread.c".

ChangeSet@1.1346.893.2, 2007-02-12 19:55:33+01:00, joerg@trift2. +1 -0
  Break a double declare of "uint thr_client_alarm" between "mysys/thr_alarm.c" and "mysys/my_pthread.c".

  mysys/my_pthread.c@1.35.1.8, 2007-02-12 19:55:31+01:00, joerg@trift2. +0 -1
    Break a double declare: "uint thr_client_alarm" is also declared in "mysys/thr_alarm.c", take it from there.

ChangeSet@1.1346.893.1, 2007-02-12 15:03:11+01:00, joerg@trift2. +1 -0
  Compile error on Windows: Signal names are undefined. Fix by hiding the whole section.

  mysys/my_thr_init.c@1.21.1.7, 2007-02-12 15:03:10+01:00, joerg@trift2. +3 -0
    Compile error on Windows: Both "SIGALRM" and "SIGUSR1" are undefined.
    Fix by hiding the whole section, according to Jani it is not needed on Windows.

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.1346.891.5, 2007-02-09 17:08:37+01:00, mysqldev@mysql.com +1 -0
  Raise version number after cloning 4.0.30

  configure.in@1.191.1.151, 2007-02-09 17:08:25+01:00, mysqldev@mysql.com +1 -1
    Raise version number after cloning 4.0.30

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.2377.33.1, 2007-02-09 13:31:51+00:00, lzhou@dev3-63.(none) +1 -0
  BUG#22025 Return correct error message when transporter error occur.

  ndb/src/common/debugger/EventLogger.cpp@1.31, 2007-02-09 13:31:46+00:00, lzhou@dev3-63.(none) +95 -4
    Add correct error string when transporter error occur.

ChangeSet@1.1346.891.4, 2007-02-09 13:03:37+02:00, jani@a88-113-38-195.elisa-laajakaista.fi +1 -0
  Fixes a compilation problem on Windows. Backport of the
  same fix from 4.0.
  TAG: clone-4.0.30-build

  sql/mysqld.cc@1.297.52.12, 2007-02-09 13:03:36+02:00, jani@a88-113-38-195.elisa-laajakaista.fi +4 -0
    Fixes a compilation problem on Windows. Backport of the
    same fix from 4.0.

ChangeSet@1.1616.2973.1, 2007-02-09 11:05:36+01:00, cmiller@calliope.local.cmiller +3 -0
  Bug#25126: Reference to non-existant column in UPDATE...ORDER BY... crashes server
  
  "update existingtable set anycolumn=nonexisting order by nonexisting" would crash
  the server.
  
  Though we would find the reference to a field, that doesn't mean we can then use
  it to set some values.  It could be a reference to another field.  If it is NULL, 
  don't try to use it to set values in the Item_field and instead return an error.
  
  Over the previous patch, this signals an error at the location of the error, rather
  than letting the subsequent deref signal it.

  mysql-test/r/order_by.result@1.40.2.1, 2007-02-09 11:05:29+01:00, cmiller@calliope.local.cmiller +24 -0
    Verify that all permutations work.

  mysql-test/t/order_by.test@1.29.2.1, 2007-02-09 11:05:30+01:00, cmiller@calliope.local.cmiller +30 -0
    Verify that all permutations work.

  sql/item.cc@1.58.79.1, 2007-02-09 11:05:30+01:00, cmiller@calliope.local.cmiller +12 -1
    When the field is NULL, don't dereference it when we set_field().  
    Instead, raise an error.

ChangeSet@1.2341.78.4, 2007-02-04 18:46:48+01:00, rafal@quant.(none) +1 -0
  BUG#25463 (Memory allocation problems in replication slave thread):
  The problem is (most probably) caused by whole server shutting down before a 
  slave thread terminates correctly. Fixing this requires fixing server shutdown
  code which has been done in 5.1 tree. Thus we ignore the issue in 5.0 assuming 
  that it is fixed in 5.1.  

  mysql-test/valgrind.supp@1.8, 2007-02-04 18:46:45+01:00, rafal@quant.(none) +17 -0
    Added a suppresion rule.

ChangeSet@1.2341.88.1, 2007-02-08 15:53:14+01:00, guilhem@gbichot3.local +10 -0
  Fix for BUG#24432
  "INSERT... ON DUPLICATE KEY UPDATE skips auto_increment values".
  When in an INSERT ON DUPLICATE KEY UPDATE, using
  an autoincrement column, we inserted some autogenerated values and
  also updated some rows, some autogenerated values were not used
  (for example, even if 10 was the largest autoinc value in the table
  at the start of the statement, 12 could be the first autogenerated
  value inserted by the statement, instead of 11). One autogenerated
  value was lost per updated row. Led to exhausting the range of the
  autoincrement column faster.
  Bug introduced by fix of BUG#20188; present since 5.0.24 and 5.1.12.
  This bug breaks replication from a pre-5.0.24 master.
  But the present bugfix, as it makes INSERT ON DUP KEY UPDATE
  behave like pre-5.0.24, breaks replication from a [5.0.24,5.0.34]
  master to a fixed (5.0.36) slave! To warn users against this when
  they upgrade their slave, as agreed with the support team, we add
  code for a fixed slave to detect that it is connected to a buggy
  master in a situation (INSERT ON DUP KEY UPDATE into autoinc column)
  likely to break replication, in which case it cannot replicate so
  stops and prints a message to the slave's error log and to SHOW SLAVE
  STATUS.
  For 5.0.36->[5.0.24,5.0.34] replication we cannot warn as master
  does not know the slave's version (but we always recommended to users
  to have slave at least as new as master).
  As agreed with support, I'll also ask for an alert to be put into
  the MySQL Network Monitoring and Advisory Service.

  mysql-test/r/rpl_insert_id.result@1.22, 2007-02-08 15:53:11+01:00, guilhem@gbichot3.local +58 -0
    results to check the bugfix; without the bugfix, you would see, in
    master and slave:
    "3,2" instead of "2,2" for the INSERT VALUES testcase,
    "11,6,..." instead of "6,6,..." for the INSERT SELECT testcase.

  mysql-test/r/rpl_known_bugs_detection.result@1.1, 2007-02-08 15:53:12+01:00, guilhem@gbichot3.local +133 -0
    see that SHOW SLAVE STATUS prints information that slave found a bug
    in master, and does not execute the dangerous event (table stays
    empty).

  mysql-test/r/rpl_known_bugs_detection.result@1.0, 2007-02-08 15:53:12+01:00, guilhem@gbichot3.local +0 -0

  mysql-test/t/rpl_insert_id.test@1.23, 2007-02-08 15:53:11+01:00, guilhem@gbichot3.local +53 -0
    testing that BUG#24432 is fixed

  mysql-test/t/rpl_known_bugs_detection-master.opt@1.1, 2007-02-08 15:53:12+01:00, guilhem@gbichot3.local +1 -0
    pass debug symbol to make the master pretend it has BUG#24432

  mysql-test/t/rpl_known_bugs_detection-master.opt@1.0, 2007-02-08 15:53:12+01:00, guilhem@gbichot3.local +0 -0

  mysql-test/t/rpl_known_bugs_detection.test@1.1, 2007-02-08 15:53:12+01:00, guilhem@gbichot3.local +90 -0
    new test to see if bug detection by slave works

  mysql-test/t/rpl_known_bugs_detection.test@1.0, 2007-02-08 15:53:12+01:00, guilhem@gbichot3.local +0 -0

  sql/log_event.cc@1.223.1.1, 2007-02-08 15:53:11+01:00, guilhem@gbichot3.local +37 -0
    A trick to force the master to pretend it is old and features BUG#24432.
    To do fast lookups in the list of known bugs by version, we compute
    the 3 X.Y.Z numbers from the master's version string and cache that
    into a new member Format_description_log_event::server_version_split.
    We do this computation in the event's two constructors.
    A simple prevention against buffer overrun when reading the master's
    version from a binlog event (assume the event is corrupted on disk,
    and so the version string on disk is longer than ST_SERVER_VER_LEN
    (50), then we would not get a closing 0 at the end of the class member.

  sql/log_event.h@1.130.1.1, 2007-02-08 15:53:12+01:00, guilhem@gbichot3.local +2 -0
    new member to hold the "split server version" (3 numbers X.Y.Z),
    and a method to compute this from the version string.

  sql/slave.cc@1.286.6.1, 2007-02-08 15:53:12+01:00, guilhem@gbichot3.local +64 -0
    a function which tells, based on master's version (as found
    in the Format_description event in the relay log being executed),
    if master can have a certain bug. This function uses a list of
    bug_id / first_version_with_bug / first_version_with_fix.
    If the test is positive, a short error message is put into SHOW SLAVE
    STATUS, and a verbose message is put into the slave's error log.
    The caller is expected to stop the slave in this case.

  sql/slave.h@1.100, 2007-02-08 15:53:12+01:00, guilhem@gbichot3.local +1 -0
    new function to test if the replication master has a bug

  sql/sql_insert.cc@1.211.5.1, 2007-02-08 15:53:12+01:00, guilhem@gbichot3.local +19 -1
    Fix for BUG#24432:t he reason was a misplaced restore_auto_increment() 
    (misplaced when fixing BUG#20188). Indeed, when updating the row,
    it is clear that the autogenerated auto_increment value will not be
    used for this row (and if by "chance" the autoinc value present
    in the updated row is >= to the not used autogenerated value,
    adjust_next_insert_id_after_explicit_value() will fix next_insert_id).
    We also add code for a fixed slave to detect that it is connected to
    a buggy master (in which case it cannot replicate so stops).

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.2377.13.17, 2007-02-07 14:22:19-08:00, antony@ppcg5.local +3 -0
  Bug#12204
    "CONNECTION is a reserved keyword"
    Allow connection to be used as an ordinary identifier
    Tests included.

  mysql-test/r/keywords.result@1.8, 2007-02-07 14:22:16-08:00, antony@ppcg5.local +13 -0
    test that CONNECTION may be used as ordinary identifier
    test that CONNECTION may be used in stored procedure.

  mysql-test/t/keywords.test@1.8, 2007-02-07 14:22:16-08:00, antony@ppcg5.local +22 -0
    test that CONNECTION may be used as ordinary identifier
    test that CONNECTION may be used in stored procedure.

  sql/sql_yacc.yy@1.498.5.2, 2007-02-07 14:22:17-08:00, antony@ppcg5.local +1 -0
    Set CONNECTION as an unreserved keyword

ChangeSet@1.1616.2968.1, 2007-02-07 09:46:20+01:00, msvensson@neptunus.(none) +1 -0
  Bug#10777 ERROR File = sql_lex.cc, Line = 93 The identifier "symbols" is undefined.
   - Protect againt empty/corrupt lex_hash-h by writing output from gen_lex_hash to 
     a temporary file first.

  sql/Makefile.am@1.77.1.41, 2007-02-07 09:46:18+01:00, msvensson@neptunus.(none) +2 -1
    Protect against empty lex_hash.h due to failed execution of
    gen_lex_hash by writing outpout to a tmp file first

ChangeSet@1.2377.13.16, 2007-02-06 15:19:01-08:00, antony@ppcg5.local +2 -0
  thd_lib_detected moved so that it is correctly declared as a data
  section symbol and not a common symbol on gcc 4.0.1 on darwin 8.8.0
  PowerPC MacOS X 10.4.8

  mysys/my_pthread.c@1.48, 2007-02-06 15:18:57-08:00, antony@ppcg5.local +0 -1
    thd_lib_detected moved to my_thr_init.c

  mysys/my_thr_init.c@1.39, 2007-02-06 15:18:57-08:00, antony@ppcg5.local +2 -0
    thd_lib_detected moved here so that it is correctly declared as a
    data section symbol and not a common symbol on gcc 4.0.1 on darwin 8.8.0
    PowerPC MacOS X 10.4.8

ChangeSet@1.2377.4.11, 2007-02-06 16:01:22-07:00, malff@weblab.(none) +3 -0
  Bug#12976 (stored procedures local variables of type bit)
  
  Before this change, a local variables in stored procedures / stored functions
  or triggers, when declared with a type of bit(N), would not evaluate their
  value properly.
  
  The problem was that the data was incorrectly typed as a string,
  causing for example bit b'1', implemented as a byte 0x01, to be interpreted
  as a string starting with the character 0x01. This later would cause
  implicit conversions to integers or booleans to fail.
  
  The root cause of this problem was an incorrect translation between field
  types, like bit(N), and internal types used when representing values in Item
  objects.
  
  Also, before this change, the function HEX() would sometime print extra "0"
  characters when invoked with bit(N) values.
  
  With this fix, the type translation (sp_map_result_type, sp_map_item_type)
  has been changed so that bit(N) fields are represented with integer values.
  
  A consequence is that, for the function HEX(), when called with a stored
  procedure local variable of type bit(N) as argument, HEX() is provided with an
  integer instead of a string, and therefore does not print "0" padding.
  
  A test case for Bug 12976 was present in the test suite, and has been updated.

  mysql-test/r/sp-vars.result@1.6, 2007-02-06 16:01:20-07:00, malff@weblab.(none) +55 -7
    Local stored procedure variables of type bit(N) are integer values.

  mysql-test/t/sp-vars.test@1.5, 2007-02-06 16:01:20-07:00, malff@weblab.(none) +58 -7
    Local stored procedure variables of type bit(N) are integer values.

  sql/sp_head.cc@1.230.1.1, 2007-02-06 16:01:20-07:00, malff@weblab.(none) +2 -0
    Local stored procedure variables of type bit(N) are integer values.

ChangeSet@1.2377.4.10, 2007-02-04 16:49:24+03:00, kroki@moonlight.home +4 -0
  BUG#25897: Some queries are no longer possible after a CREATE VIEW
             fails
  
  The bug was introduced with the push of the fix for bug#20953: after
  the error on view creation we never reset the error state, so some
  valid statements would give the same error after that.
  
  The solution is to properly reset the error state.

  mysql-test/r/view.result@1.186.1.1, 2007-02-04 16:49:19+03:00, kroki@moonlight.home +10 -0
    Add result for bug#25897: Some queries are no longer possible after
    a CREATE VIEW fails.

  mysql-test/t/view.test@1.171.1.1, 2007-02-04 16:49:19+03:00, kroki@moonlight.home +18 -0
    Add test case for bug#25897: Some queries are no longer possible after
    a CREATE VIEW fails.

  sql/sql_lex.cc@1.209.2.1, 2007-02-04 16:49:19+03:00, kroki@moonlight.home +11 -0
    Add st_parsing_options::reset() method, call it from lex_start().

  sql/sql_lex.h@1.233.6.1, 2007-02-04 16:49:20+03:00, kroki@moonlight.home +2 -4
    Add st_parsing_options::reset() method, call it from constructor.

ChangeSet@1.2341.87.1, 2007-02-03 20:14:16+01:00, rafal@quant.(none) +2 -0
  BUG#25306 (Race conditions during replication slave shutdown (valgrind stacks)):
  The possibility of the race is removed by changing sequence of calls
  
    pthread_mutex_unlock(&mi->run_lock);
    pthread_cond_broadcast(&mi->stop_cond);  
  
  into
  
    pthread_cond_broadcast(&mi->stop_cond);
    pthread_mutex_unlock(&mi->run_lock);
  
  at the end of I/O thread (similar change at the end of SQL thread). This ensures 
  that no thread waiting on the condition executes between the broadcast and the 
  unlock and thus can't delete the mi structure which caused the bug.

  sql/slave.cc@1.286.4.1, 2007-02-03 20:14:12+01:00, rafal@quant.(none) +14 -5
    Change order of condition broadcast and mutex unlock at the end of slave's 
    I/O thread and SQL thread.

  sql/sql_repl.cc@1.155.2.1, 2007-02-03 20:14:13+01:00, rafal@quant.(none) +5 -3
    Add DBUG_ENTER() call

ChangeSet@1.2377.4.9, 2007-02-01 09:36:17-07:00, malff@weblab.(none) +1 -0
  Improved comments

  sql/item_subselect.h@1.85.2.2, 2007-02-01 09:36:15-07:00, malff@weblab.(none) +5 -1
    Improved comments

ChangeSet@1.1616.2954.2, 2007-01-30 22:40:30+01:00, kent@mysql.com +1 -0
  mysql.spec.sh:
    Added man page mysql_install_db.1

  support-files/mysql.spec.sh@1.83.1.46, 2007-01-30 22:37:12+01:00, kent@mysql.com +1 -0
    Added man page mysql_install_db.1

ChangeSet@1.2294.64.1, 2007-01-29 17:32:52-07:00, malff@weblab.(none) +5 -0
  Bug#21904 (parser problem when using IN with a double "(())")
  
  Before this fix, a IN predicate of the form: "IN (( subselect ))", with two
  parenthesis, would be evaluated as a single row subselect: if the subselect
  returns more that 1 row, the statement would fail.
  
  The SQL:2003 standard defines a special exception in the specification,
  and mandates that this particular form of IN predicate shall be equivalent
  to "IN ( subselect )", which involves a table subquery and works with more
  than 1 row.
  
  This fix implements "IN (( subselect ))", "IN ((( subselect )))" etc
  as per the SQL:2003 requirement.
  
  All the details related to the implementation of this change have been
  commented in the code, and the relevant sections of the SQL:2003 spec
  are given for reference, so they are not repeated here.
  
  Having access to the spec is a requirement to review in depth this patch.

  mysql-test/r/subselect.result@1.166.1.1, 2007-01-29 17:32:49-07:00, malff@weblab.(none) +113 -0
    Implement IN predicate special exceptions with subselects.

  mysql-test/t/subselect.test@1.134.2.1, 2007-01-29 17:32:49-07:00, malff@weblab.(none) +100 -0
    Implement IN predicate special exceptions with subselects.

  sql/item_subselect.cc@1.142.4.1, 2007-01-29 17:32:49-07:00, malff@weblab.(none) +30 -0
    Implement IN predicate special exceptions with subselects.

  sql/item_subselect.h@1.82.2.1, 2007-01-29 17:32:49-07:00, malff@weblab.(none) +16 -0
    Implement IN predicate special exceptions with subselects.

  sql/sql_yacc.yy@1.497.2.2, 2007-01-29 17:32:49-07:00, malff@weblab.(none) +98 -17
    Implement IN predicate special exceptions with subselects, cleanup.

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.2294.63.1, 2007-01-25 20:00:12+03:00, kroki@moonlight.home +1 -0
  BUG#23527: set global query_cache_size can crash the server under
             high load
  
  MySQL server could crash if two or more threads would initiate query
  cache resize at the moments very close in time.
  
  The problem was introduced with the fix of bug 21051 in 5.0 and 5.1:
  simultaneous query cache resizes would wait for the first one in
  progress, but then each thread would try to finish the operation,
  accessing the data that was already reset (attempt to dereference
  'bins' pointer, which may be NULL already).
  
  The solution is to check after synchronization if another thread has
  done the reset already (test 'query_cache_size > 0' again).
  
  No test case is provided because the bug is a subject to a race.

  sql/sql_cache.cc@1.95.1.1, 2007-01-25 20:00:10+03:00, kroki@moonlight.home +17 -1
    We release 'structure_guard_mutex' in flush_cache(), so after the
    call we check if another thread had reset the cache before us.

ChangeSet@1.2377.12.1, 2007-01-25 19:58:04+03:00, kaa@polly.local +2 -0
  Added a test case for bug #20293 "group by cuts off value from time_format"

  mysql-test/r/func_time.result@1.80, 2007-01-25 19:57:29+03:00, kaa@polly.local +4 -0
    Added a test case for bug #20293 "group by cuts off value from time_format"

  mysql-test/t/func_time.test@1.67, 2007-01-25 19:58:02+03:00, kaa@polly.local +8 -0
    Added a test case for bug #20293 "group by cuts off value from time_format"

ChangeSet@1.2341.78.2, 2007-01-24 16:37:38+04:00, bar@mysql.com +3 -0
  Bug#25815 Data truncated for column TEXT
  Problem: "Data truncated" warning was incorrectly generated
  when storing a Japanese character encoded in utf8
  into a cp932 column.
  Reason: Incorrect wrong warning condition
  compared the original length of the character in bytes
  (which is 3 in utf8) to the converted length of the
  character in bytes (which is 2 in cp932).
  Fix: use "how many bytes were scanned from input" instead
  of "how many bytes were put to the column" in the condition.

  mysql-test/r/ctype_cp932.result@1.9, 2007-01-24 16:37:34+04:00, bar@mysql.com +12 -0
    Adding test case

  mysql-test/t/ctype_cp932.test@1.11, 2007-01-24 16:37:34+04:00, bar@mysql.com +11 -0
    Adding test case

  sql/field.cc@1.335.2.3, 2007-01-24 16:37:34+04:00, bar@mysql.com +1 -1
    Change warning condition from:
    "if number of bytes written to destination is less than full source length"
    to
    "if number of bytes read from source is less than full source length"
     

ChangeSet@1.2377.5.4, 2007-01-23 16:42:03+02:00, monty@mysql.com +4 -0
  Avoid compiler warnings on powermacg5
  Fixed compilation error when trying to compile libmysqld on powermac

  configure.in@1.416.4.1, 2007-01-23 16:41:58+02:00, monty@mysql.com +1 -1
    Added flag if __cxa_pure_virtual() should be defined.
    Without this flag, we get a warning from my_global.h for every compiled file on powermacg5

  extra/yassl/taocrypt/include/type_traits.hpp@1.4, 2007-01-23 16:41:58+02:00, monty@mysql.com +5 -1
    Avoid compiler warning

  include/my_global.h@1.133, 2007-01-23 16:41:59+02:00, monty@mysql.com +1 -1
    Avoid compiler warning on powermacg5

  sql/mysqld.cc@1.587, 2007-01-23 16:42:00+02:00, monty@mysql.com +1 -1
    Fix compiler error when compiling embedded on powermac

ChangeSet@1.2377.5.3, 2007-01-22 15:52:15+02:00, monty@mysql.com +8 -0
  Fixed compiler warnings
  Fixed wrong merge that disabled 'make test'
  Renamed all suppress files to end in '.supp'
  Don't give "skipped %d bytes from file" warnings in 5.0

  Makefile.am@1.96, 2007-01-22 15:52:14+02:00, monty@mysql.com +1 -0
    Added back missing cd from wrong merge

  heap/hp_write.c@1.29, 2007-01-22 15:52:14+02:00, monty@mysql.com +1 -1
    Fixed compiler warning

  mysql-test/purify.supp@1.2, 2007-01-22 15:50:29+02:00, monty@mysql.com +0 -0
    Rename: mysql-test/suppress.purify -> mysql-test/purify.supp

  mysql-test/r/mysqlbinlog.result@1.27, 2007-01-22 15:52:14+02:00, monty@mysql.com +7 -5
    Fixed test case to drop all used tables at start and used tables after each test group

  mysql-test/t/mysqlbinlog.test@1.38, 2007-01-22 15:52:14+02:00, monty@mysql.com +10 -5
    Fixed test case to drop all used tables at start and used tables after each test group

  sql/net_serv.cc@1.98, 2007-01-22 15:52:14+02:00, monty@mysql.com +1 -1
    Don't give "skipped %d bytes from file" warnings in 5.0
    (The proper fix for this is in 5.1)

  sql/table.cc@1.243, 2007-01-22 15:52:14+02:00, monty@mysql.com +2 -1
    Fixed compiler warning

  support-files/compiler_warnings.supp@1.2, 2007-01-22 15:50:29+02:00, monty@mysql.com +0 -0
    Rename: support-files/disabled_compiler_warnings.txt -> support-files/compiler_warnings.supp

ChangeSet@1.2341.58.2, 2007-01-18 13:35:49-05:00, cbell@mysql_cab_desk. +2 -0
  BUG#21490 - No warning issued for deprecated replication parameters
  This patch deprecates the replication startup options in the configuration
  file and on the command line. The options deprecated include:
  
  MASTER_HOST, MASTER_USER, MASTER_PASSWORD, MASTER_PORT, MASTER_CONNECT_RETRY,
  MASTER_SSL, MASTER_SSL_CA, MASTER_SSL_CAPATH, MASTER_SSL_CERT, MASTER_SSL_KEY,
  and MASTER_SSL_CIPHER
  
  The code is designed to print the warning message once.

  sql/mysql_priv.h@1.427.1.1, 2007-01-18 13:35:46-05:00, cbell@mysql_cab_desk. +12 -0
    BUG#21490 - No warning issued for deprecated replication parameters
    This patch modifies the WARN_DEPRECATED macro to permit displaying a deprecated 
    warning to the user at startup when the replication startup options are detected.
    It displays the same messae as the original version of the macro but allows the 
    macro to be called before a thread is created and the ER() macro is defined.

  sql/mysqld.cc@1.582.10.1, 2007-01-18 13:35:47-05:00, cbell@mysql_cab_desk. +25 -0
    BUG#21490 - No warning issued for deprecated replication parameters
    This patch deprecates the replication startup options in the configuration
    file and on the command line. The options deprecated include:
    
    MASTER_HOST, MASTER_USER, MASTER_PASSWORD, MASTER_PORT, MASTER_CONNECT_RETRY,
    MASTER_SSL, MASTER_SSL_CA, MASTER_SSL_CAPATH, MASTER_SSL_CERT, MASTER_SSL_KEY,
    and MASTER_SSL_CIPHER
    
    The code is designed to print the warning message once.

ChangeSet@1.2341.45.3, 2007-01-10 19:05:13+02:00, jani@ua141d10.elisa.omakaista.fi +1 -0
  New file for autopush. To disable (known) compiler warnings.

  support-files/disabled_compiler_warnings.txt@1.1, 2007-01-10 19:04:39+02:00, jani@ua141d10.elisa.omakaista.fi +12 -0
    BitKeeper file /home/my/bk/mysql-5.0/support-files/disabled_compiler_warnings.txt

  support-files/disabled_compiler_warnings.txt@1.0, 2007-01-10 19:04:39+02:00, jani@ua141d10.elisa.omakaista.fi +0 -0

ChangeSet@1.2294.60.1, 2007-01-10 16:55:53+02:00, jani@ua141d10.elisa.omakaista.fi +2 -0
  Added two possible error cases for a test.

  mysql-test/r/wait_timeout.result@1.4, 2007-01-10 16:55:49+02:00, jani@ua141d10.elisa.omakaista.fi +2 -2
    Added two possible error cases for a test. Depending
    on a platform, either errno can occur and is correct.
    
    Possible errors are CR_SERVER_GONE_ERROR and
    CR_SERVER_LOST

  mysql-test/t/wait_timeout.test@1.9, 2007-01-10 16:55:50+02:00, jani@ua141d10.elisa.omakaista.fi +4 -2
    Added two possible error cases for a test. Depending
    on a platform, either errno can occur and is correct.
    
    Possible errors are CR_SERVER_GONE_ERROR and
    CR_SERVER_LOST

ChangeSet@1.1616.2897.16, 2006-12-26 15:08:41+04:00, ramil@mysql.com +4 -0
  Fix for bug #23616: Week() changed behaviour between 5.0.22 and 5.0.24
  
  Consider double values as legal date{time} function's arguments
  (i.e. allow dates in internal format YYYYMMDDHHMMSS.XXXXXX).

  mysql-test/r/func_sapdb.result@1.2.1.10, 2006-12-26 15:08:39+04:00, ramil@mysql.com +1 -3
    Fix for bug #23616: Week() changed behaviour between 5.0.22 and 5.0.24
      - result adjusted.

  mysql-test/r/func_time.result@1.23.6.7, 2006-12-26 15:08:39+04:00, ramil@mysql.com +4 -0
    Fix for bug #23616: Week() changed behaviour between 5.0.22 and 5.0.24
      - test result.

  mysql-test/t/func_time.test@1.21.5.7, 2006-12-26 15:08:39+04:00, ramil@mysql.com +7 -0
    Fix for bug #23616: Week() changed behaviour between 5.0.22 and 5.0.24
      - test case.

  sql-common/my_time.c@1.6.1.13, 2006-12-26 15:08:39+04:00, ramil@mysql.com +1 -1
    Fix for bug #23616: Week() changed behaviour between 5.0.22 and 5.0.24
      - consider '.' as an acceptable separator for dates like YYYYYMMDDHHMMSS.XXXXXX

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.2341.15.2, 2006-12-15 06:21:15+02:00, monty@mysql.com +5 -0
  After merge fixes:
  - Remove compiler warnings
  - Fix merge errors
  - Indentation fixes

  sql/ha_ndbcluster.cc@1.293, 2006-12-15 06:21:13+02:00, monty@mysql.com +9 -9
    After merge fixes

  sql/slave.cc@1.288, 2006-12-15 06:21:13+02:00, monty@mysql.com +3 -1
    After merge fixes

  sql/sp.cc@1.125, 2006-12-15 06:21:13+02:00, monty@mysql.com +0 -5
    After merge fixes

  sql/sql_table.cc@1.330, 2006-12-15 06:21:13+02:00, monty@mysql.com +8 -6
    After merge fixes

  sql/sql_view.cc@1.102, 2006-12-15 06:21:13+02:00, monty@mysql.com +6 -4
    After merge fixes

ChangeSet@1.2294.31.13, 2006-12-15 00:51:37+02:00, monty@mysql.com +227 -0
  Fixed compiler warnings detected by option -Wshadow and -Wunused:
  - Removed not used variables and functions
  - Added #ifdef around code that is not used
  - Renamed variables and functions to avoid conflicts
  - Removed some not used arguments
  
  Fixed some class/struct warnings in ndb
  Added define IS_LONGDATA() to simplify code in libmysql.c
  
  I did run gcov on the changes and added 'purecov' comments on almost all lines that was not just variable name changes

  BUILD/SETUP.sh@1.62, 2006-12-15 00:51:28+02:00, monty@mysql.com +6 -3
    Added printing of unused functions and variables.
    Made it easy to test compiling with -Wshadow

  BUILD/compile-pentium-gcov@1.15, 2006-12-15 00:51:28+02:00, monty@mysql.com +3 -1
    Added warnings
    Mark binary with -gcov

  client/mysql.cc@1.227.1.2, 2006-12-15 00:51:28+02:00, monty@mysql.com +34 -33
    Fixed warnings found with gcc -Wshadow

  client/mysql_upgrade.c@1.10.2.1, 2006-12-15 00:51:28+02:00, monty@mysql.com +2 -2
    Fixed warnings found with gcc -Wshadow

  client/mysqlbinlog.cc@1.130.2.1, 2006-12-15 00:51:28+02:00, monty@mysql.com +33 -29
    Fixed warnings found with gcc -Wshadow

  client/mysqldump.c@1.252.1.1, 2006-12-15 00:51:28+02:00, monty@mysql.com +11 -9
    Fixed warnings found with gcc -Wshadow

  client/mysqltest.c@1.259.2.2, 2006-12-15 00:51:28+02:00, monty@mysql.com +62 -72
    Fixed warnings found with gcc -Wshadow

  client/sql_string.cc@1.26, 2006-12-15 00:51:28+02:00, monty@mysql.com +32 -18
    Fixed warnings found with gcc -Wshadow
    Merged with sql/sql_string.cc

  client/sql_string.h@1.16, 2006-12-15 00:51:28+02:00, monty@mysql.com +5 -1
    Fixed warnings found with gcc -Wshadow
    Merged with sql/sql_string.h

  cmd-line-utils/readline/display.c@1.16, 2006-12-15 00:51:28+02:00, monty@mysql.com +1 -1
    Fixed compiler warning

  cmd-line-utils/readline/histexpand.c@1.13, 2006-12-15 00:51:28+02:00, monty@mysql.com +4 -4
    Fixed warnings found with gcc -Wshadow
    

  cmd-line-utils/readline/input.c@1.14, 2006-12-15 00:51:28+02:00, monty@mysql.com +4 -4
    Fixed warnings found with gcc -Wshadow
    

  cmd-line-utils/readline/text.c@1.8, 2006-12-15 00:51:28+02:00, monty@mysql.com +3 -3
    Fixed warnings found with gcc -Wshadow
    

  cmd-line-utils/readline/vi_mode.c@1.14, 2006-12-15 00:51:28+02:00, monty@mysql.com +4 -4
    Fixed warnings found with gcc -Wshadow
    

  dbug/dbug_analyze.c@1.7, 2006-12-15 00:51:28+02:00, monty@mysql.com +27 -27
    Fixed warnings found with gcc -Wshadow
    

  extra/my_print_defaults.c@1.24, 2006-12-15 00:51:28+02:00, monty@mysql.com +5 -4
    Prefixed defaults_extra_file and defaults_group_suffix with 'my' to avoid conflicts with similar named local variables

  extra/yassl/include/buffer.hpp@1.7, 2006-12-15 00:51:28+02:00, monty@mysql.com +3 -0
    Fixed compiler warnings

  extra/yassl/include/crypto_wrapper.hpp@1.6, 2006-12-15 00:51:28+02:00, monty@mysql.com +6 -0
    Fixed compiler warnings

  extra/yassl/include/yassl_imp.hpp@1.6.1.1, 2006-12-15 00:51:28+02:00, monty@mysql.com +16 -1
    Fixed compiler warnings

  extra/yassl/include/yassl_int.hpp@1.14.1.1, 2006-12-15 00:51:28+02:00, monty@mysql.com +1 -0
    Fixed compiler warnings

  extra/yassl/src/crypto_wrapper.cpp@1.10, 2006-12-15 00:51:28+02:00, monty@mysql.com +2 -0
    Fixed compiler warnings

  extra/yassl/taocrypt/benchmark/benchmark.cpp@1.3, 2006-12-15 00:51:28+02:00, monty@mysql.com +16 -16
    Fixed warnings found with gcc -Wshadow
    

  extra/yassl/taocrypt/include/algebra.hpp@1.4.1.2, 2006-12-15 00:51:28+02:00, monty@mysql.com +3 -0
    Fixed compiler warnings

  extra/yassl/taocrypt/include/des.hpp@1.4.1.1, 2006-12-15 00:51:28+02:00, monty@mysql.com +1 -0
    Fixed compiler warnings

  extra/yassl/taocrypt/include/hash.hpp@1.7, 2006-12-15 00:51:28+02:00, monty@mysql.com +1 -0
    Fixed compiler warnings

  extra/yassl/taocrypt/include/hmac.hpp@1.7, 2006-12-15 00:51:28+02:00, monty@mysql.com +2 -2
    Fixed compiler warnings

  extra/yassl/taocrypt/include/modarith.hpp@1.4, 2006-12-15 00:51:28+02:00, monty@mysql.com +2 -2
    Fixed compiler warnings

  extra/yassl/taocrypt/include/modes.hpp@1.7.1.1, 2006-12-15 00:51:28+02:00, monty@mysql.com +2 -2
    Fixed compiler warnings

  extra/yassl/taocrypt/include/rsa.hpp@1.3.1.1, 2006-12-15 00:51:29+02:00, monty@mysql.com +19 -15
    Fixed compiler warnings

  extra/yassl/taocrypt/mySTL/list.hpp@1.2, 2006-12-15 00:51:29+02:00, monty@mysql.com +8 -8
    Fixed compiler warnings

  extra/yassl/taocrypt/src/aes.cpp@1.4.1.1, 2006-12-15 00:51:29+02:00, monty@mysql.com +9 -2
    Fixed compiler warnings

  extra/yassl/taocrypt/src/algebra.cpp@1.11.1.1, 2006-12-15 00:51:29+02:00, monty@mysql.com +3 -3
    Fixed compiler warnings

  extra/yassl/taocrypt/src/asn.cpp@1.12, 2006-12-15 00:51:29+02:00, monty@mysql.com +2 -2
    Fixed compiler warnings

  extra/yassl/taocrypt/test/test.cpp@1.3.1.1, 2006-12-15 00:51:29+02:00, monty@mysql.com +46 -46
    Fixed compiler warnings

  extra/yassl/testsuite/testsuite.cpp@1.5, 2006-12-15 00:51:29+02:00, monty@mysql.com +7 -6
    Fixed compiler warnings

  include/m_ctype.h@1.124, 2006-12-15 00:51:29+02:00, monty@mysql.com +1 -1
    Fixed warnings found with gcc -Wshadow

  include/my_pthread.h@1.92.2.1, 2006-12-15 00:51:29+02:00, monty@mysql.com +8 -8
    Fixed warnings found with gcc -Wshadow

  include/my_sys.h@1.189.1.1, 2006-12-15 00:51:29+02:00, monty@mysql.com +4 -3
    Fixed warnings found with gcc -Wshadow

  include/my_time.h@1.17, 2006-12-15 00:51:29+02:00, monty@mysql.com +5 -5
    Fixed warnings found with gcc -Wshadow

  include/mysql.h@1.166.1.1, 2006-12-15 00:51:29+02:00, monty@mysql.com +2 -1
    Fixed warnings found with gcc -Wshadow
    Added define IS_LONGDATA() to simplify code in libmysql.c

  libmysql/libmysql.c@1.249.2.2, 2006-12-15 00:51:29+02:00, monty@mysql.com +129 -121
    Fixed warnings found with gcc -Wshadow
    (Mostly replaced bind -> my_bind and time -> my_time)

  libmysqld/lib_sql.cc@1.117.1.1, 2006-12-15 00:51:29+02:00, monty@mysql.com +1 -2
    Removed not used variables and labels

  myisam/ft_boolean_search.c@1.94, 2006-12-15 00:51:29+02:00, monty@mysql.com +8 -8
    Fixed warnings found with gcc -Wshadow

  myisam/mi_open.c@1.98.2.1, 2006-12-15 00:51:29+02:00, monty@mysql.com +3 -3
    Fixed warnings found with gcc -Wshadow

  myisam/mi_search.c@1.62, 2006-12-15 00:51:29+02:00, monty@mysql.com +7 -7
    Fixed warnings found with gcc -Wshadow

  myisam/mi_unique.c@1.27, 2006-12-15 00:51:29+02:00, monty@mysql.com +1 -1
    Fixed compiler warning

  myisam/myisampack.c@1.55.1.1, 2006-12-15 00:51:29+02:00, monty@mysql.com +5 -4
    Fixed warnings found with gcc -Wshadow

  myisam/rt_index.c@1.18, 2006-12-15 00:51:29+02:00, monty@mysql.com +0 -3
    Remove not used variables

  myisam/sort.c@1.58, 2006-12-15 00:51:29+02:00, monty@mysql.com +3 -3
    Fixed warnings found with gcc -Wshadow

  mysql-test/r/mysqlcheck.result@1.3, 2006-12-15 00:51:29+02:00, monty@mysql.com +3 -0
    Remove databases and tables possible left by previous test

  mysql-test/r/mysqltest.result@1.38.1.1, 2006-12-15 00:51:29+02:00, monty@mysql.com +2 -0
    New test results

  mysql-test/t/mysql.test@1.22.1.1, 2006-12-15 00:51:29+02:00, monty@mysql.com +11 -1
    Coverage tests

  mysql-test/t/mysqlbinlog.test@1.33.2.1, 2006-12-15 00:51:29+02:00, monty@mysql.com +8 -0
    Coverage tests

  mysql-test/t/mysqlcheck.test@1.3, 2006-12-15 00:51:29+02:00, monty@mysql.com +9 -0
    Remove databases and tables possible left by previous test

  mysql-test/t/mysqltest.test@1.47.1.1, 2006-12-15 00:51:29+02:00, monty@mysql.com +20 -0
    Coverage tests

  mysys/default.c@1.84, 2006-12-15 00:51:29+02:00, monty@mysql.com +19 -19
    Prefixed defaults_file, defaults_group_suffix and defaults_extra_file with 'my' to avoid conflicts with local variables in some functions

  mysys/mf_iocache2.c@1.28, 2006-12-15 00:51:29+02:00, monty@mysql.com +13 -13
    Fixed warnings found with gcc -Wshadow

  mysys/mf_keycache.c@1.58, 2006-12-15 00:51:29+02:00, monty@mysql.com +3 -2
    Fixed warnings found with gcc -Wshadow

  mysys/my_bitmap.c@1.35, 2006-12-15 00:51:29+02:00, monty@mysql.com +3 -3
    Fixed warnings found with gcc -Wshadow

  mysys/sha1.c@1.7, 2006-12-15 00:51:29+02:00, monty@mysql.com +6 -6
    Fixed warnings found with gcc -Wshadow

  ndb/include/kernel/signaldata/ArbitSignalData.hpp@1.4, 2006-12-15 00:51:29+02:00, monty@mysql.com +2 -0
    Fixed compiler warning

  ndb/include/kernel/signaldata/DictTabInfo.hpp@1.21, 2006-12-15 00:51:29+02:00, monty@mysql.com +2 -0
    Fixed compiler warnings

  ndb/include/ndbapi/NdbReceiver.hpp@1.16, 2006-12-15 00:51:29+02:00, monty@mysql.com +1 -1
    Fixed warnings found with gcc -Wshadow

  ndb/include/transporter/TransporterDefinitions.hpp@1.13, 2006-12-15 00:51:29+02:00, monty@mysql.com +5 -0
    Fixed compiler warning

  ndb/include/util/InputStream.hpp@1.6, 2006-12-15 00:51:29+02:00, monty@mysql.com +1 -0
    Fixed compiler warning

  ndb/include/util/OutputStream.hpp@1.5, 2006-12-15 00:51:29+02:00, monty@mysql.com +2 -0
    Fixed compiler warning

  ndb/include/util/SimpleProperties.hpp@1.7, 2006-12-15 00:51:29+02:00, monty@mysql.com +1 -0
    Fixed compiler warning

  ndb/include/util/SocketAuthenticator.hpp@1.3, 2006-12-15 00:51:29+02:00, monty@mysql.com +1 -0
    Fixed compiler warning

  ndb/include/util/SocketServer.hpp@1.10, 2006-12-15 00:51:29+02:00, monty@mysql.com +1 -0
    Fixed compiler warning

  ndb/src/common/mgmcommon/ConfigRetriever.cpp@1.36, 2006-12-15 00:51:30+02:00, monty@mysql.com +4 -3
    Fixed warnings found with gcc -Wshadow

  ndb/src/common/portlib/NdbTick.c@1.6, 2006-12-15 00:51:30+02:00, monty@mysql.com +2 -2
    Fixed warnings found with gcc -Wshadow

  ndb/src/common/transporter/SHM_Transporter.cpp@1.17, 2006-12-15 00:51:30+02:00, monty@mysql.com +2 -2
    Fixed warnings found with gcc -Wshadow

  ndb/src/common/transporter/TCP_Transporter.cpp@1.11, 2006-12-15 00:51:30+02:00, monty@mysql.com +2 -2
    Fixed warnings found with gcc -Wshadow

  ndb/src/common/transporter/TCP_Transporter.hpp@1.6, 2006-12-15 00:51:30+02:00, monty@mysql.com +1 -0
    Fixed compiler warning

  ndb/src/common/transporter/Transporter.cpp@1.23, 2006-12-15 00:51:30+02:00, monty@mysql.com +2 -2
    Removed not used variable

  ndb/src/common/transporter/TransporterRegistry.cpp@1.62, 2006-12-15 00:51:30+02:00, monty@mysql.com +0 -2
    Removed not used variable

  ndb/src/common/util/Bitmask.cpp@1.9, 2006-12-15 00:51:30+02:00, monty@mysql.com +15 -15
    Moved function to avoid warnings of not used function

  ndb/src/common/util/ConfigValues.cpp@1.10, 2006-12-15 00:51:30+02:00, monty@mysql.com +3 -3
    Fixed warnings found with gcc -Wshadow

  ndb/src/common/util/File.cpp@1.12.2.1, 2006-12-15 00:51:30+02:00, monty@mysql.com +2 -2
    Fixed warnings found with gcc -Wshadow

  ndb/src/common/util/Properties.cpp@1.11, 2006-12-15 00:51:30+02:00, monty@mysql.com +2 -2
    Fixed warnings found with gcc -Wshadow

  ndb/src/common/util/SocketClient.cpp@1.9, 2006-12-15 00:51:30+02:00, monty@mysql.com +1 -1
    Fixed wrong return value

  ndb/src/common/util/random.c@1.5, 2006-12-15 00:51:30+02:00, monty@mysql.com +4 -4
    Fixed warnings found with gcc -Wshadow

  ndb/src/common/util/socket_io.cpp@1.9.1.1, 2006-12-15 00:51:30+02:00, monty@mysql.com +2 -2
    Fixed warnings found with gcc -Wshadow

  ndb/src/cw/cpcd/APIService.cpp@1.9, 2006-12-15 00:51:30+02:00, monty@mysql.com +0 -1
    Removed not used variable

  ndb/src/cw/cpcd/main.cpp@1.11, 2006-12-15 00:51:30+02:00, monty@mysql.com +0 -2
    Removed not used variables

  ndb/src/kernel/blocks/cmvmi/Cmvmi.cpp@1.25.1.2, 2006-12-15 00:51:30+02:00, monty@mysql.com +4 -4
    Fixed compiler warnings

  ndb/src/kernel/blocks/dbdict/Dbdict.cpp@1.70.1.1, 2006-12-15 00:51:30+02:00, monty@mysql.com +0 -5
    Removed not used variables

  ndb/src/kernel/blocks/dbdict/Dbdict.hpp@1.25, 2006-12-15 00:51:30+02:00, monty@mysql.com +6 -0
    Fixed compiler warnings

  ndb/src/kernel/blocks/dbdih/Dbdih.hpp@1.13.1.1, 2006-12-15 00:51:30+02:00, monty@mysql.com +3 -0
    Fixed compiler warnings

  ndb/src/kernel/blocks/dblqh/Dblqh.hpp@1.40.1.1, 2006-12-15 00:51:30+02:00, monty@mysql.com +3 -0
    Fixed compiler warnings

  ndb/src/kernel/blocks/dblqh/DblqhMain.cpp@1.96.1.1, 2006-12-15 00:51:30+02:00, monty@mysql.com +0 -9
    Removed not used variables

  ndb/src/kernel/blocks/dbtc/Dbtc.hpp@1.35.1.1, 2006-12-15 00:51:30+02:00, monty@mysql.com +4 -0
    Fixed compiler warnings

  ndb/src/kernel/blocks/dbtup/Dbtup.hpp@1.27.1.1, 2006-12-15 00:51:30+02:00, monty@mysql.com +1 -0
    Fixed compiler warnings

  ndb/src/kernel/blocks/dbtup/DbtupScan.cpp@1.4, 2006-12-15 00:51:30+02:00, monty@mysql.com +0 -1
    Removed not used variable

  ndb/src/kernel/blocks/dbtux/DbtuxNode.cpp@1.17, 2006-12-15 00:51:30+02:00, monty@mysql.com +0 -2
    Removed not used variables

  ndb/src/kernel/blocks/dbtux/DbtuxScan.cpp@1.31, 2006-12-15 00:51:30+02:00, monty@mysql.com +0 -2
    Removed not used variables

  ndb/src/kernel/blocks/dbtux/DbtuxTree.cpp@1.15, 2006-12-15 00:51:30+02:00, monty@mysql.com +0 -1
    Removed not used variables

  ndb/src/kernel/blocks/ndbcntr/Ndbcntr.hpp@1.7, 2006-12-15 00:51:30+02:00, monty@mysql.com +1 -0
    Fixed compiler warnings

  ndb/src/kernel/blocks/ndbcntr/NdbcntrMain.cpp@1.35, 2006-12-15 00:51:30+02:00, monty@mysql.com +0 -4
    Removed not used variables

  ndb/src/kernel/blocks/ndbfs/AsyncFile.hpp@1.5, 2006-12-15 00:51:30+02:00, monty@mysql.com +2 -0
    Fixed compiler warnings

  ndb/src/kernel/blocks/qmgr/Qmgr.hpp@1.12, 2006-12-15 00:51:30+02:00, monty@mysql.com +2 -0
    Fixed compiler warnings

  ndb/src/kernel/blocks/qmgr/QmgrMain.cpp@1.37, 2006-12-15 00:51:30+02:00, monty@mysql.com +0 -2
    Removed not used variables

  ndb/src/kernel/blocks/suma/Suma.cpp@1.23, 2006-12-15 00:51:30+02:00, monty@mysql.com +0 -6
    Removed not used variables

  ndb/src/kernel/blocks/suma/Suma.hpp@1.7, 2006-12-15 00:51:30+02:00, monty@mysql.com +1 -0
    Fixed compiler warnings

  ndb/src/kernel/vm/MetaData.hpp@1.5, 2006-12-15 00:51:30+02:00, monty@mysql.com +1 -0
    Fixed compiler warnings

  ndb/src/mgmapi/LocalConfig.cpp@1.23, 2006-12-15 00:51:30+02:00, monty@mysql.com +9 -9
    Fixed warnings found with gcc -Wshadow

  ndb/src/mgmapi/mgmapi.cpp@1.67, 2006-12-15 00:51:30+02:00, monty@mysql.com +6 -7
    Fixed warnings found with gcc -Wshadow

  ndb/src/mgmclient/CommandInterpreter.cpp@1.71.1.1, 2006-12-15 00:51:30+02:00, monty@mysql.com +0 -3
    Removed not used variables

  ndb/src/mgmsrv/ConfigInfo.cpp@1.81, 2006-12-15 00:51:30+02:00, monty@mysql.com +2 -4
    Fixed warnings found with gcc -Wshadow
    Removed not used variables

  ndb/src/mgmsrv/ConfigInfo.hpp@1.12, 2006-12-15 00:51:30+02:00, monty@mysql.com +5 -2
    Fixed warnings found with gcc -Wshadow

  ndb/src/mgmsrv/InitConfigFileParser.cpp@1.27, 2006-12-15 00:51:30+02:00, monty@mysql.com +13 -12
    Prefixed defaults_file, defaults_group_suffix and defaults_extra_file with 'my' to avoid conflicts with local variables in some functions

  ndb/src/mgmsrv/MgmtSrvr.cpp@1.108.1.1, 2006-12-15 00:51:31+02:00, monty@mysql.com +4 -4
    Removed not used variables and functions

  ndb/src/mgmsrv/MgmtSrvr.hpp@1.49, 2006-12-15 00:51:31+02:00, monty@mysql.com +1 -0
    Fixed compiler warnings

  ndb/src/mgmsrv/Services.cpp@1.70.1.3, 2006-12-15 00:51:31+02:00, monty@mysql.com +4 -5
    Removed not used variables and functions

  ndb/src/mgmsrv/main.cpp@1.49, 2006-12-15 00:51:31+02:00, monty@mysql.com +0 -1
    Removed not used variable

  ndb/src/ndbapi/ClusterMgr.hpp@1.12, 2006-12-15 00:51:31+02:00, monty@mysql.com +1 -0
    Fixed compiler warnings

  ndb/src/ndbapi/Ndb.cpp@1.63, 2006-12-15 00:51:31+02:00, monty@mysql.com +0 -2
    Removed not used variables

  ndb/src/ndbapi/NdbBlob.cpp@1.30, 2006-12-15 00:51:31+02:00, monty@mysql.com +0 -2
    Removed not used variables

  ndb/src/ndbapi/NdbDictionaryImpl.cpp@1.96, 2006-12-15 00:51:31+02:00, monty@mysql.com +0 -5
    Removed not used variables

  ndb/src/ndbapi/NdbIndexOperation.cpp@1.26, 2006-12-15 00:51:31+02:00, monty@mysql.com +0 -2
    Removed not used variables

  ndb/src/ndbapi/NdbOperationDefine.cpp@1.21, 2006-12-15 00:51:31+02:00, monty@mysql.com +1 -2
    Removed not used variables

  ndb/src/ndbapi/NdbOperationExec.cpp@1.22, 2006-12-15 00:51:31+02:00, monty@mysql.com +0 -2
    Removed not used variables

  ndb/src/ndbapi/NdbOperationSearch.cpp@1.27, 2006-12-15 00:51:31+02:00, monty@mysql.com +0 -3
    Removed not used variables

  ndb/src/ndbapi/NdbScanFilter.cpp@1.9, 2006-12-15 00:51:31+02:00, monty@mysql.com +1 -0
    Fixed compiler warning

  ndb/src/ndbapi/NdbScanOperation.cpp@1.81, 2006-12-15 00:51:31+02:00, monty@mysql.com +0 -3
    Removed not used variables

  ndb/src/ndbapi/SignalSender.cpp@1.7, 2006-12-15 00:51:31+02:00, monty@mysql.com +2 -0
    Removed not used variables

  ndb/src/ndbapi/ndb_cluster_connection.cpp@1.38, 2006-12-15 00:51:31+02:00, monty@mysql.com +0 -1
    Removed not used variable

  ndb/tools/delete_all.cpp@1.20, 2006-12-15 00:51:31+02:00, monty@mysql.com +2 -0
    Removed not used variable

  ndb/tools/desc.cpp@1.22, 2006-12-15 00:51:31+02:00, monty@mysql.com +2 -0
    Removed not used variable

  ndb/tools/drop_index.cpp@1.17, 2006-12-15 00:51:31+02:00, monty@mysql.com +2 -0
    Removed not used variable

  ndb/tools/drop_tab.cpp@1.17, 2006-12-15 00:51:31+02:00, monty@mysql.com +2 -0
    Removed not used variable

  ndb/tools/listTables.cpp@1.23, 2006-12-15 00:51:31+02:00, monty@mysql.com +2 -0
    Removed not used variable

  ndb/tools/ndb_config.cpp@1.18.1.2, 2006-12-15 00:51:31+02:00, monty@mysql.com +9 -4
    Fixed warnings found with gcc -Wshadow
    Added missing puts(desc)

  ndb/tools/restore/Restore.hpp@1.21, 2006-12-15 00:51:31+02:00, monty@mysql.com +2 -1
    Changed delimiter to define instead of static variable, as the static variable caused a LOT of compiler warnings
    Fixed compiler warning

  ndb/tools/restore/consumer.hpp@1.7, 2006-12-15 00:51:31+02:00, monty@mysql.com +1 -0
    Fixed compiler warning

  ndb/tools/restore/restore_main.cpp@1.37, 2006-12-15 00:51:31+02:00, monty@mysql.com +6 -6
    Fixed compiler warnings

  ndb/tools/select_all.cpp@1.24, 2006-12-15 00:51:31+02:00, monty@mysql.com +3 -1
    Removed not used variables

  ndb/tools/select_count.cpp@1.21, 2006-12-15 00:51:31+02:00, monty@mysql.com +2 -0
    Removed not used variable

  server-tools/instance-manager/commands.h@1.10, 2006-12-15 00:51:31+02:00, monty@mysql.com +1 -0
    Fixed compiler warnings

  server-tools/instance-manager/guardian.cc@1.25.1.1, 2006-12-15 00:51:31+02:00, monty@mysql.com +3 -3
    Fixed compiler warnings

  server-tools/instance-manager/instance_options.cc@1.33, 2006-12-15 00:51:31+02:00, monty@mysql.com +0 -2
    Removed not used variables

  server-tools/instance-manager/mysql_connection.cc@1.16, 2006-12-15 00:51:31+02:00, monty@mysql.com +3 -3
    Fixed compiler warnings

  server-tools/instance-manager/options.cc@1.34, 2006-12-15 00:51:31+02:00, monty@mysql.com +8 -8
    Fixed compiler warnings

  server-tools/instance-manager/options.h@1.17, 2006-12-15 00:51:31+02:00, monty@mysql.com +1 -0
    Fixed compiler warnings

  server-tools/instance-manager/parse.cc@1.14, 2006-12-15 00:51:31+02:00, monty@mysql.com +0 -1
    Removed not used variable

  server-tools/instance-manager/user_map.cc@1.16, 2006-12-15 00:51:31+02:00, monty@mysql.com +1 -0
    Fixed compiler warnings

  server-tools/instance-manager/user_map.h@1.6, 2006-12-15 00:51:31+02:00, monty@mysql.com +1 -0
    Fixed compiler warnings

  sql-common/client.c@1.104.1.3, 2006-12-15 00:51:34+02:00, monty@mysql.com +2 -2
    Removed not used variable

  sql-common/my_time.c@1.25.2.2, 2006-12-15 00:51:34+02:00, monty@mysql.com +29 -28
    Removed not used variable
    time -> my_time

  sql/field.cc@1.331.1.2, 2006-12-15 00:51:31+02:00, monty@mysql.com +95 -102
    Fixed compiler warnings

  sql/field.h@1.191.2.1, 2006-12-15 00:51:31+02:00, monty@mysql.com +27 -27
    Fixed compiler warnings

  sql/filesort.cc@1.109.1.2, 2006-12-15 00:51:31+02:00, monty@mysql.com +3 -1
    Fixed compiler warnings

  sql/ha_archive.cc@1.79, 2006-12-15 00:51:31+02:00, monty@mysql.com +11 -9
    Removed table and share arguments from get_share() / free_share() to get rid of compiler warnings

  sql/ha_archive.h@1.36, 2006-12-15 00:51:31+02:00, monty@mysql.com +2 -2
    Removed table and share arguments from get_share() / free_share() to get rid of compiler warnings

  sql/ha_federated.cc@1.71.1.1, 2006-12-15 00:51:31+02:00, monty@mysql.com +4 -4
    Fixed compiler warnings

  sql/ha_heap.cc@1.81, 2006-12-15 00:51:31+02:00, monty@mysql.com +14 -14
    Fixed compiler warnings

  sql/ha_myisam.cc@1.171, 2006-12-15 00:51:31+02:00, monty@mysql.com +45 -43
    Fixed compiler warnings

  sql/ha_myisammrg.cc@1.86, 2006-12-15 00:51:32+02:00, monty@mysql.com +14 -14
    Fixed compiler warnings

  sql/ha_ndbcluster.cc@1.286.1.3, 2006-12-15 00:51:32+02:00, monty@mysql.com +43 -48
    Fixed compiler warnings

  sql/handler.cc@1.222.2.2, 2006-12-15 00:51:32+02:00, monty@mysql.com +2 -7
    Fixed compiler warnings

  sql/item.cc@1.242.2.2, 2006-12-15 00:51:32+02:00, monty@mysql.com +32 -31
    Fixed compiler warnings

  sql/item.h@1.212.1.1, 2006-12-15 00:51:32+02:00, monty@mysql.com +19 -18
    Fixed compiler warnings
    new_item() -> clone_item(), to avoid a lot of warnings with variable 'new_item'
    el() -> element_index()

  sql/item_cmpfunc.cc@1.224.2.1, 2006-12-15 00:51:32+02:00, monty@mysql.com +40 -37
    Fixed compiler warnings

  sql/item_cmpfunc.h@1.134.1.1, 2006-12-15 00:51:32+02:00, monty@mysql.com +14 -14
    Fixed compiler warnings

  sql/item_func.cc@1.312.2.3, 2006-12-15 00:51:32+02:00, monty@mysql.com +11 -9
    Fixed compiler warnings

  sql/item_geofunc.cc@1.28, 2006-12-15 00:51:32+02:00, monty@mysql.com +3 -2
    Fixed compiler warnings

  sql/item_row.h@1.22, 2006-12-15 00:51:32+02:00, monty@mysql.com +1 -1
    Fixed compiler warnings

  sql/item_strfunc.cc@1.288.1.2, 2006-12-15 00:51:32+02:00, monty@mysql.com +4 -11
    Fixed compiler warnings

  sql/item_subselect.cc@1.142.2.1, 2006-12-15 00:51:32+02:00, monty@mysql.com +20 -21
    Fixed compiler warnings

  sql/item_subselect.h@1.82.1.1, 2006-12-15 00:51:32+02:00, monty@mysql.com +3 -3
    Fixed compiler warnings

  sql/item_sum.cc@1.189.2.2, 2006-12-15 00:51:32+02:00, monty@mysql.com +11 -14
    Fixed compiler warnings

  sql/item_timefunc.cc@1.133.2.2, 2006-12-15 00:51:32+02:00, monty@mysql.com +5 -5
    Fixed compiler warnings

  sql/log.cc@1.198.1.1, 2006-12-15 00:51:32+02:00, monty@mysql.com +35 -20
    Fixed compiler warnings
    More comments
    Added #ifdef HAVE_REPLICATION

  sql/log_event.cc@1.214.1.3, 2006-12-15 00:51:32+02:00, monty@mysql.com +7 -3
    Fixed compiler warnings

  sql/log_event.h@1.126.2.1, 2006-12-15 00:51:32+02:00, monty@mysql.com +2 -0
    Fixed compiler warnings

  sql/mysql_priv.h@1.423.1.2, 2006-12-15 00:51:32+02:00, monty@mysql.com +4 -4
    query_id -> global_query_id, to avoid a lot of clashes with function and class variables
    start_time -> server_start_time

  sql/mysqld.cc@1.577.5.1, 2006-12-15 00:51:32+02:00, monty@mysql.com +65 -35
    Fixed compiler warnings:
    - Removed not used variables
    - Added #ifndef EMBEDDED_LIBRARY
    - Fixed shadow warnings

  sql/net_serv.cc@1.93.1.1, 2006-12-15 00:51:32+02:00, monty@mysql.com +7 -1
    Fixed compiler warnings

  sql/opt_range.cc@1.232.1.2, 2006-12-15 00:51:32+02:00, monty@mysql.com +70 -86
    range -> last_range to avoid shadow warnings
    Removed not used function print_rowid()

  sql/opt_range.h@1.66, 2006-12-15 00:51:32+02:00, monty@mysql.com +1 -1
    range -> last_range to avoid shadow warnings
    

  sql/password.c@1.41, 2006-12-15 00:51:32+02:00, monty@mysql.com +4 -3
    Fixed compiler warnings

  sql/protocol.cc@1.119, 2006-12-15 00:51:33+02:00, monty@mysql.com +3 -1
    Fixed compiler warnings

  sql/repl_failsafe.cc@1.62, 2006-12-15 00:51:33+02:00, monty@mysql.com +6 -6
    Fixed compiler warnings

  sql/set_var.cc@1.171.1.3, 2006-12-15 00:51:33+02:00, monty@mysql.com +3 -6
    Fixed compiler warnings

  sql/set_var.h@1.78.1.1, 2006-12-15 00:51:33+02:00, monty@mysql.com +42 -40
    type() -> show_type()
    Fixed compiler warnings

  sql/slave.cc@1.287, 2006-12-15 00:51:33+02:00, monty@mysql.com +14 -12
    Fixed compiler warnings

  sql/sp_head.cc@1.225.1.2, 2006-12-15 00:51:33+02:00, monty@mysql.com +4 -6
    Fixed compiler warnings

  sql/sp_head.h@1.88.1.1, 2006-12-15 00:51:33+02:00, monty@mysql.com +5 -4
    Fixed compiler warnings

  sql/spatial.cc@1.28, 2006-12-15 00:51:33+02:00, monty@mysql.com +12 -13
    Fixed compiler warnings

  sql/spatial.h@1.21, 2006-12-15 00:51:33+02:00, monty@mysql.com +6 -6
    length() -> geom_length() to avoid compiler warnings
    wkb_end -> wkb_last to avoid compiler warnings with local variables named 'wkb_end'

  sql/sql_cache.h@1.34, 2006-12-15 00:51:33+02:00, monty@mysql.com +3 -3
    Fixed compiler warnings

  sql/sql_class.cc@1.254.2.1, 2006-12-15 00:51:33+02:00, monty@mysql.com +8 -6
    Fixed compiler warnings

  sql/sql_class.h@1.310.6.1, 2006-12-15 00:51:33+02:00, monty@mysql.com +19 -15
    log -> log_xid() to avoid compiler warnings
    Fixed shadow compiler warnings

  sql/sql_derived.cc@1.79, 2006-12-15 00:51:33+02:00, monty@mysql.com +0 -2
    Removed not used variable

  sql/sql_insert.cc@1.206.2.1, 2006-12-15 00:51:33+02:00, monty@mysql.com +5 -7
    Fixed compiler warnings

  sql/sql_lex.cc@1.206.3.1, 2006-12-15 00:51:33+02:00, monty@mysql.com +20 -17
    Fixed compiler warnings

  sql/sql_lex.h@1.234, 2006-12-15 00:51:33+02:00, monty@mysql.com +2 -1
    res -> saved_error to make the meaning of the variable clear and avoid shadow warnings

  sql/sql_load.cc@1.100.1.1, 2006-12-15 00:51:33+02:00, monty@mysql.com +5 -1
    Fixed compiler warnings

  sql/sql_parse.cc@1.590.7.1, 2006-12-15 00:51:33+02:00, monty@mysql.com +97 -99
    Fixed compiler warnings

  sql/sql_prepare.cc@1.188, 2006-12-15 00:51:33+02:00, monty@mysql.com +7 -6
    Fixed compiler warnings

  sql/sql_select.cc@1.475.1.4, 2006-12-15 00:51:33+02:00, monty@mysql.com +55 -50
    Fixed compiler warnings

  sql/sql_show.cc@1.333.1.1, 2006-12-15 00:51:33+02:00, monty@mysql.com +21 -13
    Fixed compiler warnings

  sql/sql_string.cc@1.95, 2006-12-15 00:51:33+02:00, monty@mysql.com +9 -10
    Fixed compiler warnings

  sql/sql_string.h@1.62.1.1, 2006-12-15 00:51:33+02:00, monty@mysql.com +2 -1
    Fixed compiler warnings

  sql/sql_table.cc@1.325.2.1, 2006-12-15 00:51:33+02:00, monty@mysql.com +29 -26
    Fixed compiler warnings

  sql/sql_trigger.cc@1.58.1.2, 2006-12-15 00:51:33+02:00, monty@mysql.com +9 -8
    Fixed compiler warnings

  sql/sql_trigger.h@1.23, 2006-12-15 00:51:33+02:00, monty@mysql.com +3 -2
    table -> trigger_table to avoid warnings from local variables

  sql/sql_union.cc@1.135, 2006-12-15 00:51:33+02:00, monty@mysql.com +45 -44
    Fixed compiler warnings
    (mainly res -> saved_error)

  sql/sql_update.cc@1.206, 2006-12-15 00:51:34+02:00, monty@mysql.com +0 -1
    Removed not used variable

  sql/sql_view.cc@1.101, 2006-12-15 00:51:34+02:00, monty@mysql.com +0 -1
    Removed not used variable

  sql/sql_yacc.yy@1.494.1.3, 2006-12-15 00:51:34+02:00, monty@mysql.com +1 -6
    Removed not used variable

  sql/table.cc@1.237.2.3, 2006-12-15 00:51:34+02:00, monty@mysql.com +31 -31
    Removed not used variable

  sql/tztime.cc@1.37, 2006-12-15 00:51:34+02:00, monty@mysql.com +2 -2
    Removed not used variable

  sql/unireg.cc@1.79, 2006-12-15 00:51:34+02:00, monty@mysql.com +7 -7
    Removed not used variable

  strings/ctype-bin.c@1.72, 2006-12-15 00:51:34+02:00, monty@mysql.com +3 -3
    mblen -> mb_len to avoid compiler warnings with local variable mblen

  strings/ctype-cp932.c@1.14, 2006-12-15 00:51:34+02:00, monty@mysql.com +2 -2
    Fixed compiler warnings

  strings/ctype-eucjpms.c@1.15, 2006-12-15 00:51:34+02:00, monty@mysql.com +2 -2
    Fixed compiler warnings

  strings/ctype-mb.c@1.53, 2006-12-15 00:51:34+02:00, monty@mysql.com +32 -32
    mblen -> mb_len to avoid compiler warnings with local variable mblen

  strings/ctype-simple.c@1.80, 2006-12-15 00:51:34+02:00, monty@mysql.com +7 -7
    mblen -> mb_len to avoid compiler warnings with local variable mblen
    exp -> exponent

  strings/ctype-sjis.c@1.91, 2006-12-15 00:51:34+02:00, monty@mysql.com +2 -2
    Fixed compiler warnings

  strings/ctype-uca.c@1.41, 2006-12-15 00:51:34+02:00, monty@mysql.com +13 -13
    mblen -> mb_len to avoid compiler warnings with local variable mblen

  strings/ctype-ujis.c@1.72, 2006-12-15 00:51:34+02:00, monty@mysql.com +2 -2
    Fixed compiler warnings

  strings/ctype-utf8.c@1.102, 2006-12-15 00:51:34+02:00, monty@mysql.com +2 -2
    Fixed compiler warnings

  strings/decimal.c@1.71.1.2, 2006-12-15 00:51:34+02:00, monty@mysql.com +14 -13
    Fixed compiler warnings

  strings/my_vsnprintf.c@1.36, 2006-12-15 00:51:34+02:00, monty@mysql.com +7 -0
    Added comment

  strings/strtod.c@1.23.1.1, 2006-12-15 00:51:34+02:00, monty@mysql.com +14 -13
    Fixed compiler warnings

  tests/mysql_client_test.c@1.212.1.2, 2006-12-15 00:51:34+02:00, monty@mysql.com +1237 -1237
    Fixed compiler warnings
    (Biggest part of patch is to not get a conflict with global function 'bind')

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.

ChangeSet@1.2196.1.38, 2006-07-23 22:13:12+02:00, msvensson@neptunus.(none) +1 -0
  Remove strange comment

  client/mysql.cc@1.208.1.2, 2006-07-23 22:13:10+02:00, msvensson@neptunus.(none) +0 -4
    Remove strange comment

