ChangeSet@1.2608.8.1, 2008-05-12 21:01:13+05:00, gshchepa@host.loc +7 -0
  Fixed bug #36055: mysql_upgrade doesn't really 'upgrade' tables
  
  The REPAIR TABLE ... USE_FRM query silently corrupts data of tables
  with old .FRM file version.
  The mysql_upgrade client program or the REPAIR TABLE query (without
  the USE_FRM clause) can't prevent this trouble, because in the
  common case they don't upgrade .FRM file to compatible structure.
  
  1. Evaluation of the REPAIR TABLE ... USE_FRM query has been
     modified to reject such tables with the message:
     "Failed repairing incompatible .FRM file".
  
  2. REPAIR TABLE query (without USE_FRM clause) evaluation has been
     modified to upgrade .FRM files to current version.
  
  3. CHECK TABLE ... FOR UPGRADE query evaluation has been modified
     to return error status when .FRM file has incompatible version.
  
  4. mysql_upgrade and mysqlcheck client programs call CHECK TABLE
     FOR UPGRADE and REPAIR TABLE queries, so their behaviors have
     been changed too to upgrade .FRM files with incompatible
     version numbers.

  mysql-test/r/repair.result@1.28, 2008-05-12 20:59:09+05:00, gshchepa@host.loc +36 -0
    Added test case for bug# 36055.

  mysql-test/std_data/bug36055.MYD@1.1, 2008-05-12 20:04:32+05:00, gshchepa@host.loc +2 -0
    Added test data for bug #36055.

  mysql-test/std_data/bug36055.MYD@1.0, 2008-05-12 20:04:32+05:00, gshchepa@host.loc +0 -0

  mysql-test/std_data/bug36055.MYI@1.1, 2008-05-12 20:04:32+05:00, gshchepa@host.loc +24 -0
    Added test data for bug #36055.

  mysql-test/std_data/bug36055.MYI@1.0, 2008-05-12 20:04:32+05:00, gshchepa@host.loc +0 -0

  mysql-test/std_data/bug36055.frm@1.1, 2008-05-12 20:04:32+05:00, gshchepa@host.loc +192 -0
    Added test data for bug #36055.

  mysql-test/std_data/bug36055.frm@1.0, 2008-05-12 20:04:32+05:00, gshchepa@host.loc +0 -0

  mysql-test/t/repair.test@1.20, 2008-05-12 20:59:13+05:00, gshchepa@host.loc +30 -0
    Added test case for bug# 36055.

  sql/handler.cc@1.242, 2008-05-12 20:59:15+05:00, gshchepa@host.loc +2 -0
    Fixed bug #36055: mysql_upgrade doesn't really 'upgrade' tables
    
    The handler::ha_check_for_upgrade method has been modified to
    return error if .FRM file has incompatible version number.

  sql/sql_table.cc@1.360, 2008-05-12 20:59:16+05:00, gshchepa@host.loc +7 -0
    Fixed bug #36055: mysql_upgrade doesn't really 'upgrade' tables
    
    The prepare_for_repair function has been modified to reject
    REPAIR TABLE ... USE_FRM queries on incompatible .FRM files
    with the message: "Failed repairing incompatible .FRM file".

ChangeSet@1.2610.1.6, 2008-05-08 09:41:22+02:00, mattiasj@client-10-129-10-147.upp.off.mysql.com +4 -0
  Bug#32575 - Parse error of stmt with extended comments on slave side
  
  Problem was that mysql_create_view did not remove all comments characters
  when writing to binlog, resulting in parse error of stmt on slave side.
  
  Solution was to use the recreated select clause
  and add a generated CHECK OPTION clause if needed.

  mysql-test/r/rpl_sp.result@1.23, 2008-05-08 09:41:20+02:00, mattiasj@client-10-129-10-147.upp.off.mysql.com +1 -1
    Bug#32575 - Parse error of stmt with extended comments on slave side
    
    Updated test result

  mysql-test/r/rpl_view.result@1.10, 2008-05-08 09:41:20+02:00, mattiasj@client-10-129-10-147.upp.off.mysql.com +16 -2
    Bug#32575 - Parse error of stmt with extended comments on slave side
    
    Updated test result

  mysql-test/t/rpl_view.test@1.8, 2008-05-08 09:41:20+02:00, mattiasj@client-10-129-10-147.upp.off.mysql.com +18 -0
    Bug#32575 - Parse error of stmt with extended comments on slave side
    
    Added test case

  sql/sql_view.cc@1.123, 2008-05-08 09:41:20+02:00, mattiasj@client-10-129-10-147.upp.off.mysql.com +5 -3
    Bug#32575 - Parse error of stmt with extended comments on slave side
    
    Problem was that mysql_create_view did not remove all comments characters
    when writing to binlog, resulting in parse error of stmt on slave side.
    
    Solution was to use the recreated select clause and generate
    'WITH {LOCAL|CASCADED} CHECK OPTION'.

ChangeSet@1.2623, 2008-05-06 21:43:46+05:00, gshchepa@host.loc +9 -0
  Partial rollback of fix for bug #30059: End-space truncation is inconsistent
  or incorrect.
  
  For better conformance with standard, truncation procedure of CHAR columns
  has been changed to ignore truncation of trailing whitespace characters
  (note has been removed).
  
  Finally, for columns with non-binary charsets:
  
  1. CHAR(N) columns silently ignore trailing whitespace truncation;
  2. VARCHAR and TEXT columns issue Note about truncation.
  
  BLOBs and other columns with BINARY charset are unaffected.
  
  
  

  mysql-test/r/bdb.result@1.58, 2008-05-06 21:01:56+05:00, gshchepa@host.loc +0 -1
    Rollback of bug #30059 fix.

  mysql-test/r/heap.result@1.52, 2008-05-06 21:01:58+05:00, gshchepa@host.loc +0 -1
    Rollback of bug #30059 fix.

  mysql-test/r/innodb.result@1.174, 2008-05-06 21:01:58+05:00, gshchepa@host.loc +0 -1
    Rollback of bug #30059 fix.

  mysql-test/r/myisam.result@1.108, 2008-05-06 21:01:59+05:00, gshchepa@host.loc +0 -1
    Rollback of bug #30059 fix.

  mysql-test/r/strict.result@1.38, 2008-05-06 21:01:59+05:00, gshchepa@host.loc +0 -2
    Rollback of bug #30059 fix.

  mysql-test/r/type_binary.result@1.6, 2008-05-06 21:01:59+05:00, gshchepa@host.loc +0 -1
    Rollback of bug #30059 fix.

  mysql-test/r/warnings.result@1.43, 2008-05-06 21:02:01+05:00, gshchepa@host.loc +0 -2
    Updated test case for bug #30059.

  sql/field.cc@1.377, 2008-05-06 21:02:01+05:00, gshchepa@host.loc +12 -6
    Post-commit fix for bug #30059.
    
    The Field_longstr::report_if_important_data method
    has been changed to notify about trailing spaces only if
    the new count_spaces parameter is TRUE.
    
    The Field_string::store method has been changed to
    ignore trailing whitespace truncation (CHAR column
    type).

  sql/field.h@1.217, 2008-05-06 21:02:02+05:00, gshchepa@host.loc +2 -1
    Post-commit fix for bug #30059.
    
    The Field_longstr::report_if_important_data method declaration
    has been changed to accept extra parameter: bool count_spaces.

ChangeSet@1.2622, 2008-05-06 11:57:19+03:00, gkodinov@magare.gmz +2 -0
  revert the push of bug 35616.

  mysys/my_static.c@1.21, 2008-05-06 11:57:18+03:00, gkodinov@magare.gmz +2 -2
    revert the push of bug 35616.

  mysys/my_static.h@1.22, 2008-05-06 11:57:18+03:00, gkodinov@magare.gmz +1 -1
    revert the push of bug 35616.

ChangeSet@1.2621, 2008-05-06 02:55:35+02:00, tnurnberg@noir.wlan.koehntopp.de +2 -0
  Bug#35616: memory overrun on 64-bit linux on setting large values for keybuffer-size
  
  We could allocate chunks larger than 4GB, but did our size-accounting in 32-bit
  values. This could lead to spurious warnings, inaccurate accounting, and, in
  theory, data loss.
  
  Affected: 64-bit platforms. Debug-build (with safemalloc). At least one buffer
  larger than 4GB. For potential data loss, a re-alloc on such a buffer would be
  necessary.

  mysys/my_static.c@1.20, 2008-05-06 02:55:34+02:00, tnurnberg@noir.wlan.koehntopp.de +2 -2
    Make memory-accounting 64-bit safe.

  mysys/my_static.h@1.21, 2008-05-06 02:55:34+02:00, tnurnberg@noir.wlan.koehntopp.de +1 -1
    Make memory-accounting 64-bit safe.
    Move in struct for better alignment when 64-bit.

ChangeSet@1.2610.4.4, 2008-05-02 14:41:19+02:00, msvensson@pilot.mysql.com +2 -0
  Bug#36469 mysql_upgrade does not use --tmpdir

  client/mysql_upgrade.c@1.29, 2008-05-02 14:41:18+02:00, msvensson@pilot.mysql.com +10 -1
    Add --tmpdir option to mysql_upgrade and use it when creating temporary files.

  mysql-test/mysql-test-run.pl@1.255.2.2, 2008-05-02 14:41:18+02:00, msvensson@pilot.mysql.com +1 -0
    Pass --tmpdir to mysql_upgrade

ChangeSet@1.2610.4.3, 2008-05-02 12:49:31+02:00, msvensson@pilot.mysql.com +1 -0
  Bug#35986 valgrind warning in DbugParse for empty string in SET GLOBAL DEBUG=""
   - Code in DbugParse was reading from beyond end of the control string

  dbug/dbug.c@1.26, 2008-05-02 12:49:29+02:00, msvensson@pilot.mysql.com +1 -1
    Don't try to parse control strings that hasn't got any tokens
    or is zero size

ChangeSet@1.2610.4.2, 2008-05-02 11:22:10+02:00, msvensson@pilot.mysql.com +1 -0
  Bug#36465 mysqltest should always use the --tmpdir

  client/mysqltest.c@1.314.1.1, 2008-05-02 11:22:09+02:00, msvensson@pilot.mysql.com +1 -1
    Use the --tmpdir location to create temporary files

ChangeSet@1.2610.4.1, 2008-05-02 09:13:43+02:00, msvensson@pilot.mysql.com +1 -0
  Bug#36463 mysql-test-run.pl should always use the --tmpdi

  mysql-test/mysql-test-run.pl@1.255.2.1, 2008-05-02 09:13:42+02:00, msvensson@pilot.mysql.com +10 -2
    Use the requested tmpdir in 'collect_mysqld_features', create
    it if it does not already exists

ChangeSet@1.2610.3.1, 2008-05-01 11:36:03-04:00, pcrews@pcrews-mac-local.local +1 -0
  Bug#36026 - Test funcs_1.<engine>_trig_03 failing on Windows
  Bug#36028 - Test funcs_1.<engine>_trig_03e failing on Windows
  Bug#36029 - Test funcs_1.<engine>_trig_0407 failing on Windows
  Bug#36030 - Test funcs_1.<engine>_trig_08 failing on Windows
  
  Adding $MASTER_MYSOCK to init_win_path()
  When path names are short, master.sock ends up in MYSQL_TMP_DIR, but with longer path names,
  master.sock ends up in /tmp/<random_string>/ and these tests will fail due to path delimiter difference.
  
  New changeset to start with 5.0 -- Not all of these tests are present in 5.0, but want to keep mysqltest the same

  client/mysqltest.c@1.315, 2008-05-01 11:36:01-04:00, pcrews@pcrews-mac-local.local +1 -0
    Bug#36026 - Test funcs_1.<engine>_trig_03 failing on Windows
    Bug#36028 - Test funcs_1.<engine>_trig_03e failing on Windows
    Bug#36029 - Test funcs_1.<engine>_trig_0407 failing on Windows
    Bug#36030 - Test funcs_1.<engine>_trig_08 failing on Windows
    
    Adding $MASTER_MYSOCK to init_win_path()
    When path names are short, master.sock ends up in MYSQL_TMP_DIR, but with longer path names,
    master.sock ends up in /tmp/<random_string>/ and these tests will fail due to path delimiter difference.
    
    New changeset to start with 5.0 -- Not all of these tests are present in 5.0, but want to keep mysqltest the same

ChangeSet@1.2610.1.3, 2008-05-01 13:49:26+03:00, gkodinov@magare.gmz +3 -0
  Fix for bug #35298: GROUP_CONCAT with DISTINCT can crash the server
  
  The bug is a regression introduced by the patch for bug32798.
  
  The code in Item_func_group_concat::clear() relied on the 'distinct'
  variable to check if 'unique_filter' was initialized. That, however,
  is not always valid because Item_func_group_concat::setup() can do
  shortcuts in some cases w/o initializing 'unique_filter'.
  
  Fixed by checking the value of 'unique_filter' instead of 'distinct'
  before dereferencing.

  mysql-test/r/func_gconcat.result@1.76, 2008-05-01 13:49:22+03:00, gkodinov@magare.gmz +26 -0
    Added test cases for bugs #35298 and #36024.

  mysql-test/t/func_gconcat.test@1.63, 2008-05-01 13:49:23+03:00, gkodinov@magare.gmz +36 -0
    Added test cases for bugs #35298 and #36024.

  sql/item_sum.cc@1.223, 2008-05-01 13:49:23+03:00, gkodinov@magare.gmz +1 -1
    Check if unique_filter != NULL before dereferencing it. Non-zero value
    of distinct does not always mean that unique_filter is initialized
    because Item_func_group_concat::setup() can do shortcuts is some cases

ChangeSet@1.2608.4.5, 2008-04-25 00:39:37+04:00, evgen@moonbone.local +3 -0
  Bug#36023: Incorrect handling of zero length caused an assertion to fail.
  
  When a zero length is provided to the my_decimal_length_to_precision
  function along with unsigned_flag set to false it returns a negative value.
  For queries that employs temporary tables may cause failed assertion or
  excessive memory consumption while temporary table creation.
  
  Now the my_decimal_length_to_precision and the my_decimal_precision_to_length
  functions take unsigned_flag into account only if the length/precision
  argument is non-zero.

  mysql-test/r/type_decimal.result@1.51, 2008-04-25 00:38:56+04:00, evgen@moonbone.local +7 -0
    Added a test case for the bug#36023: Incorrect handling of zero length caused
     an assertion to fail.

  mysql-test/t/type_decimal.test@1.40, 2008-04-25 00:38:54+04:00, evgen@moonbone.local +8 -0
    Added a test case for the bug#36023: Incorrect handling of zero length caused
     an assertion to fail.

  sql/my_decimal.h@1.19, 2008-04-25 00:38:57+04:00, evgen@moonbone.local +11 -2
    Bug#36023: Incorrect handling of zero length caused an assertion to fail.
    Now the my_decimal_length_to_precision and the my_decimal_precision_to_length
    functions take unsigned_flag into account only if the length/precision
    argument is non-zero.

ChangeSet@1.2610.1.1, 2008-04-23 20:54:53+02:00, kent@mysql.com +1 -0
  Raise version number after cloning 5.0.60

  configure.in@1.477, 2008-04-23 20:54:41+02:00, kent@mysql.com +2 -2
    Raise version number after cloning 5.0.60

ChangeSet@1.2608.4.4, 2008-04-23 14:22:49+05:00, gshchepa@host.loc +2 -0
  subselect.test, subselect.result:
    Post-commit minor cleanup of testcase (bug#36139).

  mysql-test/r/subselect.result@1.208, 2008-04-23 14:20:50+05:00, gshchepa@host.loc +1 -1
    Post-commit minor cleanup of testcase (bug#36139).

  mysql-test/t/subselect.test@1.166, 2008-04-23 14:22:04+05:00, gshchepa@host.loc +1 -1
    Post-commit minor cleanup of testcase (bug#36139).

ChangeSet@1.2608.5.1, 2008-04-23 02:27:23+05:00, gshchepa@host.loc +3 -0
  Fixed bug#36005: server crashes inside NOT IN clause subquery with
                   impossible WHERE/HAVING clause
                   (subselect_single_select_engine::exec).
  
  Allocation and initialization of joined table list t1, t2... of
  subqueries like:
  
      NOT IN (SELECT ... FROM t1,t2,... WHERE 0)
  
  is optimized out, however server tries to traverse this list.

  mysql-test/r/subselect3.result@1.14, 2008-04-23 02:23:53+05:00, gshchepa@host.loc +9 -0
    Added test case for bug#36005.

  mysql-test/t/subselect3.test@1.14, 2008-04-23 02:23:54+05:00, gshchepa@host.loc +13 -0
    Added test case for bug#36005.

  sql/sql_select.cc@1.562, 2008-04-23 02:23:55+05:00, gshchepa@host.loc +1 -0
    Fixed bug#36005.
    
    1. JOIN::prepare initializes JOIN::table counter (actually a size
       of the JOIN::join_tab array) and sets it to a number of joined tables.
    
    2. The make_join_statistics function (when called from JOIN::optimize)
       allocates and fills the JOIN::join_tab array.
       However, when optimizing subselect has impossible (definite false)
       WHERE or HAVING clause, optimizer skips call to make_join_statistics
       and leaves JOIN::join_tab == NULL.
    
    3. subselect_single_select_engine::exec does traversal of the JOIN::join_tab
       array and the server dies because array is not allocated but array
       counter is greater than 0.
    
    The JOIN::optimize method has been modified to reset the JOIN::table
    counter to 0 in cause of impossible WHERE/HAVING clause.

ChangeSet@1.2608.4.2, 2008-04-23 02:14:58+05:00, gshchepa@host.loc +4 -0
  Fixed bug #35993: memory corruption and crash with multibyte conversion.
  
  Grouping or ordering of long values in not indexed BLOB/TEXT columns
  with GBK or BIG5 charsets crashes the server.
  
  MySQL server uses sorting (the filesort procedure) in the temporary
  table to evaluate the GROUP BY clause in case of lack of suitable index.
  That procedure takes into account only first @max_sort_length bytes
  (system variable, usually 1024) of TEXT/BLOB sorting key string.
  The my_strnxfrm_gbk and my_strnxfrm_big5 fill temporary keys
  with data of whole blob length instead of @max_sort_length bytes
  length. That buffer overrun has been fixed.

  mysql-test/r/ctype_gbk.result@1.10, 2008-04-23 02:08:07+05:00, gshchepa@host.loc +7 -0
    Added test case for bug #35993.

  mysql-test/t/ctype_gbk.test@1.7, 2008-04-23 02:08:09+05:00, gshchepa@host.loc +14 -0
    Added test case for bug #35993.

  strings/ctype-big5.c@1.94, 2008-04-23 02:08:10+05:00, gshchepa@host.loc +4 -2
    Fixed bug #35993: memory corruption and crash with multibyte conversion.
    
    Buffer overrun has been fixed in the my_strnxfrm_big5 function.

  strings/ctype-gbk.c@1.83, 2008-04-23 02:08:12+05:00, gshchepa@host.loc +4 -2
    Fixed bug #35993: memory corruption and crash with multibyte conversion.
    
    Buffer overrun has been fixed in the my_strnxfrm_gbk function.

ChangeSet@1.2608.4.1, 2008-04-22 02:53:12+04:00, sergefp@mysql.com +3 -0
  BUG#36139 "float, zerofill, crash with subquery"
  - Make convert_zerofill_number_to_string() take into account that the 
    constant it is converting may evaluate to NULL.

  mysql-test/r/subselect.result@1.207, 2008-04-22 02:53:07+04:00, sergefp@mysql.com +7 -0
    BUG#36139 "float, zerofill, crash with subquery"
    - Testcase

  mysql-test/t/subselect.test@1.165, 2008-04-22 02:53:07+04:00, sergefp@mysql.com +12 -0
    BUG#36139 "float, zerofill, crash with subquery"
    - Testcase

  sql/item.cc@1.308, 2008-04-22 02:53:07+04:00, sergefp@mysql.com +8 -3
    BUG#36139 "float, zerofill, crash with subquery"
    - Make convert_zerofill_number_to_string() take into account that the 
      constant it is converting may evaluate to NULL.

ChangeSet@1.2608.3.1, 2008-04-17 18:41:23+02:00, joerg@trift2. +1 -0
  Fix for   Bug #34291  compile-amd64-debug-max-no-ndb missing
      
  Include several "BUILD/compile-*" files in a source tarball ("make dist" target)
  which might be useful to community users who want to build from source.
  
  When merging this up, the "BUILD/compile-*" file list needs to be checked.

  BUILD/Makefile.am@1.14, 2008-04-17 18:41:17+02:00, joerg@trift2. +8 -0
    Fix for   Bug #34291  compile-amd64-debug-max-no-ndb missing
    
    Include several "BUILD/compile-*" files in a source tarball ("make dist" target)
    which might be useful to community users who want to build from source.

ChangeSet@1.2617, 2008-04-10 15:55:37-04:00, cmiller@zippy.cornsilk.net +2 -0
  Fix mismerge.

  sql/field.cc@1.376, 2008-04-10 15:55:35-04:00, cmiller@zippy.cornsilk.net +1 -1
    Fix indentation of new line.

  sql/item_create.cc@1.71, 2008-04-10 15:55:35-04:00, cmiller@zippy.cornsilk.net +1 -1
    Fix mismerge.

ChangeSet@1.2485.36.4, 2008-04-09 12:27:30-04:00, cmiller@zippy.cornsilk.net +4 -0
  Follow-up to B-g#15776, test failures on 64-bit linux.
  
  Make maximum blob size to be 2**32-1, regardless of word size.
  
  Fix failure of timestamp with size of 2**31-1.  The method of
  rounding up to the nearest even number would overflow.

  mysql-test/r/type_blob.result@1.57.1.1, 2008-04-09 12:27:28-04:00, cmiller@zippy.cornsilk.net +5 -1
    2**32-1 is not a special case for timestamp.
    
    Test 2**32-1 and 2**64 as the reliable test points for both 32-
    and 64-bit machines.  I'd like to test 2**32, but that would make 
    tests that vary between architectures.
    
    I'd like to generalize the tests by pulling the max blob size from
    the server, and then "eval"ing N-1, N, and N+1 instead of all these
    literal numbers, but I have not found a way to get UINT_MAX.

  mysql-test/t/type_blob.test@1.36.1.1, 2008-04-09 12:27:28-04:00, cmiller@zippy.cornsilk.net +3 -1
    2**32-1 is not a special case for timestamp.
    
    Test 2**32-1 and 2**64 as the reliable test points for both 32-
    and 64-bit machines.  I'd like to test 2**32, but that would make 
    tests that vary between architectures.
    
    I'd like to generalize the tests by pulling the max blob size from
    the server, and then "eval"ing N-1, N, and N+1 instead of all these
    literal numbers, but I have not found a way to get UINT_MAX.

  sql/field.cc@1.359.1.2, 2008-04-09 12:27:28-04:00, cmiller@zippy.cornsilk.net +17 -7
    Fix a bug where the round-to-even code for TIMESTAMP fields
    failed where the size would overflow the size to zero and then
    fail.
    
    Also, since we silently truncate the size of TIMESTAMP fields, set
    the maximum size we report is allowable to be the largest parsable
    number.

  sql/unireg.h@1.49.1.2, 2008-04-09 12:27:28-04:00, cmiller@zippy.cornsilk.net +1 -1
    Make BLOB size the maximum that the packed value in 
    field_blob::get_length() allows.

ChangeSet@1.2597.2.4, 2008-04-04 17:41:14+02:00, mleich@five.local.lan +1 -0
  Backport of fix made in 5.1 to 5.0
  mysql-test/Makefile.am   :    Fix a copy-paste error ...

  mysql-test/Makefile.am@1.99, 2008-04-04 17:41:13+02:00, mleich@five.local.lan +1 -1
    Correct the variables used for target directory
    of copy action.

ChangeSet@1.2572.27.1, 2008-04-03 11:32:00-04:00, cmiller@zippy.cornsilk.net +5 -0
  Bug#26294: library name conflict between MySQL 4.x, 5.0 and Qt 3.3
  
  When linking with some external programs, "multiple definition 
  of `init_time'"
  
  Rename init_time() to my_init_time() to avoid collision with other
  libraries (particularly libmng).

  client/mysqlbinlog.cc@1.143, 2008-04-03 11:31:57-04:00, cmiller@zippy.cornsilk.net +1 -1
    Rename init_time() to my_init_time().

  include/my_time.h@1.22, 2008-04-03 11:31:58-04:00, cmiller@zippy.cornsilk.net +1 -1
    Rename init_time() to my_init_time().

  sql-common/my_time.c@1.41, 2008-04-03 11:31:58-04:00, cmiller@zippy.cornsilk.net +3 -3
    Rename init_time() to my_init_time().

  sql/init.cc@1.21, 2008-04-03 11:31:58-04:00, cmiller@zippy.cornsilk.net +1 -1
    Rename init_time() to my_init_time().

  sql/tztime.cc@1.42.1.1, 2008-04-03 11:31:58-04:00, cmiller@zippy.cornsilk.net +2 -2
    Rename init_time() to my_init_time().

ChangeSet@1.2597.2.2, 2008-04-02 19:47:20+02:00, mleich@five.local.lan +1 -0
  Correct the location of the directory for
  "funcs_1" data load

  mysql-test/Makefile.am@1.98, 2008-04-02 19:47:19+02:00, mleich@five.local.lan +2 -2
    Correct the location of the directory for
    "funcs_1" data load

ChangeSet@1.2485.36.3, 2008-04-01 12:26:12-04:00, cmiller@zippy.cornsilk.net +1 -0
  Test updated.

  mysql-test/r/type_blob.result@1.57, 2008-04-01 12:26:10-04:00, cmiller@zippy.cornsilk.net +1 -0
    Test updated.

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

  BitKeeper/deleted/.del-triggers_master.test@1.2, 2008-03-31 16:26:14+02:00, mleich@five.local.lan +0 -0
    Delete: mysql-test/suite/funcs_1/triggers/triggers_master.test

  mysql-test/Makefile.am@1.97, 2008-03-31 19:47:57+02:00, mleich@five.local.lan +6 -2
    Introduce installation of funcs_1 files in std_data.

  mysql-test/mysql-test-run.pl@1.256, 2008-03-31 19:47:57+02:00, mleich@five.local.lan +2 -2
    The tests within funcs_1 need a server started with
        --secure-file-priv=<MYSQLTEST_VARDIR>
    like the main regression tests.

  mysql-test/std_data/funcs_1/innodb_tb1.txt@1.2, 2008-03-31 16:34:26+02:00, mleich@five.local.lan +0 -0
    Rename: mysql-test/suite/funcs_1/data/innodb_tb1.txt -> mysql-test/std_data/funcs_1/innodb_tb1.txt

  mysql-test/std_data/funcs_1/innodb_tb2.txt@1.2, 2008-03-31 16:34:26+02:00, mleich@five.local.lan +0 -0
    Rename: mysql-test/suite/funcs_1/data/innodb_tb2.txt -> mysql-test/std_data/funcs_1/innodb_tb2.txt

  mysql-test/std_data/funcs_1/innodb_tb3.txt@1.2, 2008-03-31 16:34:26+02:00, mleich@five.local.lan +0 -0
    Rename: mysql-test/suite/funcs_1/data/innodb_tb3.txt -> mysql-test/std_data/funcs_1/innodb_tb3.txt

  mysql-test/std_data/funcs_1/innodb_tb4.txt@1.2, 2008-03-31 16:34:26+02:00, mleich@five.local.lan +0 -0
    Rename: mysql-test/suite/funcs_1/data/innodb_tb4.txt -> mysql-test/std_data/funcs_1/innodb_tb4.txt

  mysql-test/std_data/funcs_1/load_file.txt@1.1, 2008-03-31 19:48:00+02:00, mleich@five.local.lan +1 -0
    New BitKeeper file ``mysql-test/std_data/funcs_1/load_file.txt''

  mysql-test/std_data/funcs_1/load_file.txt@1.0, 2008-03-31 19:48:00+02:00, mleich@five.local.lan +0 -0

  mysql-test/std_data/funcs_1/memory_tb1.txt@1.2, 2008-03-31 16:34:58+02:00, mleich@five.local.lan +0 -0
    Rename: mysql-test/suite/funcs_1/data/memory_tb1.txt -> mysql-test/std_data/funcs_1/memory_tb1.txt

  mysql-test/std_data/funcs_1/memory_tb2.txt@1.2, 2008-03-31 16:34:58+02:00, mleich@five.local.lan +0 -0
    Rename: mysql-test/suite/funcs_1/data/memory_tb2.txt -> mysql-test/std_data/funcs_1/memory_tb2.txt

  mysql-test/std_data/funcs_1/memory_tb3.txt@1.2, 2008-03-31 16:34:58+02:00, mleich@five.local.lan +0 -0
    Rename: mysql-test/suite/funcs_1/data/memory_tb3.txt -> mysql-test/std_data/funcs_1/memory_tb3.txt

  mysql-test/std_data/funcs_1/memory_tb4.txt@1.2, 2008-03-31 16:34:58+02:00, mleich@five.local.lan +0 -0
    Rename: mysql-test/suite/funcs_1/data/memory_tb4.txt -> mysql-test/std_data/funcs_1/memory_tb4.txt

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

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

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

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

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

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

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

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

  mysql-test/suite/funcs_1/README.txt@1.4, 2008-03-31 19:47:57+02:00, mleich@five.local.lan +9 -1
    Extended description

  mysql-test/suite/funcs_1/datadict/datadict_bug_12777.inc@1.2, 2008-03-31 19:47:57+02:00, mleich@five.local.lan +6 -6
    Cleanup

  mysql-test/suite/funcs_1/datadict/datadict_load.inc@1.4, 2008-03-31 19:47:57+02:00, mleich@five.local.lan +8 -8
    Cleanup

  mysql-test/suite/funcs_1/include/innodb_tb1.inc@1.2, 2008-03-31 19:47:57+02:00, mleich@five.local.lan +60 -59
    Adjustment to new storage place of infile.

  mysql-test/suite/funcs_1/include/innodb_tb2.inc@1.2, 2008-03-31 19:47:57+02:00, mleich@five.local.lan +54 -52
    Adjustment to new storage place of infile.

  mysql-test/suite/funcs_1/include/innodb_tb3.inc@1.2, 2008-03-31 19:47:57+02:00, mleich@five.local.lan +62 -60
    Adjustment to new storage place of infile.

  mysql-test/suite/funcs_1/include/innodb_tb4.inc@1.2, 2008-03-31 19:47:57+02:00, mleich@five.local.lan +54 -52
    Adjustment to new storage place of infile.

  mysql-test/suite/funcs_1/include/memory_tb1.inc@1.3, 2008-03-31 19:47:57+02:00, mleich@five.local.lan +53 -51
    Adjustment to new storage place of infile.

  mysql-test/suite/funcs_1/include/memory_tb2.inc@1.3, 2008-03-31 19:47:57+02:00, mleich@five.local.lan +54 -52
    Adjustment to new storage place of infile.

  mysql-test/suite/funcs_1/include/memory_tb3.inc@1.3, 2008-03-31 19:47:57+02:00, mleich@five.local.lan +56 -55
    Adjustment to new storage place of infile.

  mysql-test/suite/funcs_1/include/memory_tb4.inc@1.3, 2008-03-31 19:47:57+02:00, mleich@five.local.lan +54 -52
    Adjustment to new storage place of infile.

  mysql-test/suite/funcs_1/include/myisam_tb1.inc@1.2, 2008-03-31 19:47:57+02:00, mleich@five.local.lan +60 -58
    Adjustment to new storage place of infile.

  mysql-test/suite/funcs_1/include/myisam_tb2.inc@1.2, 2008-03-31 19:47:57+02:00, mleich@five.local.lan +70 -68
    Adjustment to new storage place of infile.

  mysql-test/suite/funcs_1/include/myisam_tb3.inc@1.2, 2008-03-31 19:47:57+02:00, mleich@five.local.lan +62 -60
    Adjustment to new storage place of infile.

  mysql-test/suite/funcs_1/include/myisam_tb4.inc@1.2, 2008-03-31 19:47:57+02:00, mleich@five.local.lan +69 -67
    Adjustment to new storage place of infile.

  mysql-test/suite/funcs_1/include/sp_tb.inc@1.3, 2008-03-31 19:47:57+02:00, mleich@five.local.lan +54 -29
    Adjustment to new storage place of infile.

  mysql-test/suite/funcs_1/r/innodb_func_view.result@1.4, 2008-03-31 19:47:57+02:00, mleich@five.local.lan +4600 -4374
    Updated results

  mysql-test/suite/funcs_1/r/innodb_storedproc_02.result@1.4, 2008-03-31 19:47:58+02:00, mleich@five.local.lan +46 -33
    Updated results

  mysql-test/suite/funcs_1/r/innodb_storedproc_03.result@1.4, 2008-03-31 19:47:58+02:00, mleich@five.local.lan +28 -20
    Updated results

  mysql-test/suite/funcs_1/r/innodb_storedproc_06.result@1.3, 2008-03-31 19:47:58+02:00, mleich@five.local.lan +31 -20
    Updated results

  mysql-test/suite/funcs_1/r/innodb_storedproc_07.result@1.4, 2008-03-31 19:47:58+02:00, mleich@five.local.lan +28 -20
    Updated results

  mysql-test/suite/funcs_1/r/innodb_storedproc_08.result@1.4, 2008-03-31 19:47:58+02:00, mleich@five.local.lan +28 -20
    Updated results

  mysql-test/suite/funcs_1/r/innodb_storedproc_10.result@1.4, 2008-03-31 19:47:58+02:00, mleich@five.local.lan +121 -36
    Updated results

  mysql-test/suite/funcs_1/r/innodb_trig_0102.result@1.4, 2008-03-31 19:47:58+02:00, mleich@five.local.lan +93 -92
    Updated results

  mysql-test/suite/funcs_1/r/innodb_trig_03.result@1.3, 2008-03-31 19:47:58+02:00, mleich@five.local.lan +133 -182
    Updated results

  mysql-test/suite/funcs_1/r/innodb_trig_0407.result@1.3, 2008-03-31 19:47:58+02:00, mleich@five.local.lan +84 -83
    Updated results

  mysql-test/suite/funcs_1/r/innodb_trig_08.result@1.5, 2008-03-31 19:47:58+02:00, mleich@five.local.lan +180 -142
    Updated results

  mysql-test/suite/funcs_1/r/innodb_trig_09.result@1.4, 2008-03-31 19:47:58+02:00, mleich@five.local.lan +81 -79
    Updated results

  mysql-test/suite/funcs_1/r/innodb_trig_1011ext.result@1.3, 2008-03-31 19:47:58+02:00, mleich@five.local.lan +75 -74
    Updated results

  mysql-test/suite/funcs_1/r/innodb_trig_frkey.result@1.3, 2008-03-31 19:47:58+02:00, mleich@five.local.lan +60 -59
    Updated results

  mysql-test/suite/funcs_1/r/innodb_views.result@1.7, 2008-03-31 19:47:58+02:00, mleich@five.local.lan +104 -102
    Updated results

  mysql-test/suite/funcs_1/r/is_columns_innodb.result@1.3, 2008-03-31 19:47:58+02:00, mleich@five.local.lan +298 -287
    Updated results

  mysql-test/suite/funcs_1/r/is_columns_memory.result@1.3, 2008-03-31 19:47:58+02:00, mleich@five.local.lan +285 -274
    Updated results

  mysql-test/suite/funcs_1/r/is_columns_myisam.result@1.3, 2008-03-31 19:47:58+02:00, mleich@five.local.lan +322 -311
    Updated results

  mysql-test/suite/funcs_1/r/is_columns_ndb.result@1.3, 2008-03-31 19:47:58+02:00, mleich@five.local.lan +24 -18
    Updated results

  mysql-test/suite/funcs_1/r/is_tables_innodb.result@1.3, 2008-03-31 19:47:58+02:00, mleich@five.local.lan +298 -287
    Updated results

  mysql-test/suite/funcs_1/r/is_tables_memory.result@1.3, 2008-03-31 19:47:58+02:00, mleich@five.local.lan +285 -274
    Updated results

  mysql-test/suite/funcs_1/r/is_tables_myisam.result@1.3, 2008-03-31 19:47:58+02:00, mleich@five.local.lan +322 -311
    Updated results

  mysql-test/suite/funcs_1/r/is_tables_ndb.result@1.3, 2008-03-31 19:47:58+02:00, mleich@five.local.lan +24 -18
    Updated results

  mysql-test/suite/funcs_1/r/memory_func_view.result@1.4, 2008-03-31 19:47:58+02:00, mleich@five.local.lan +4600 -4374
    Updated results

  mysql-test/suite/funcs_1/r/memory_storedproc_02.result@1.4, 2008-03-31 19:47:58+02:00, mleich@five.local.lan +46 -33
    Updated results

  mysql-test/suite/funcs_1/r/memory_storedproc_03.result@1.4, 2008-03-31 19:47:58+02:00, mleich@five.local.lan +28 -20
    Updated results

  mysql-test/suite/funcs_1/r/memory_storedproc_06.result@1.3, 2008-03-31 19:47:58+02:00, mleich@five.local.lan +31 -20
    Updated results

  mysql-test/suite/funcs_1/r/memory_storedproc_07.result@1.4, 2008-03-31 19:47:58+02:00, mleich@five.local.lan +28 -20
    Updated results

  mysql-test/suite/funcs_1/r/memory_storedproc_08.result@1.4, 2008-03-31 19:47:58+02:00, mleich@five.local.lan +28 -20
    Updated results

  mysql-test/suite/funcs_1/r/memory_storedproc_10.result@1.4, 2008-03-31 19:47:58+02:00, mleich@five.local.lan +121 -36
    Updated results

  mysql-test/suite/funcs_1/r/memory_trig_0102.result@1.4, 2008-03-31 19:47:58+02:00, mleich@five.local.lan +87 -86
    Updated results

  mysql-test/suite/funcs_1/r/memory_trig_03.result@1.3, 2008-03-31 19:47:59+02:00, mleich@five.local.lan +127 -176
    Updated results

  mysql-test/suite/funcs_1/r/memory_trig_0407.result@1.3, 2008-03-31 19:47:59+02:00, mleich@five.local.lan +78 -77
    Updated results

  mysql-test/suite/funcs_1/r/memory_trig_08.result@1.5, 2008-03-31 19:47:59+02:00, mleich@five.local.lan +174 -136
    Updated results

  mysql-test/suite/funcs_1/r/memory_trig_09.result@1.4, 2008-03-31 19:47:59+02:00, mleich@five.local.lan +75 -73
    Updated results

  mysql-test/suite/funcs_1/r/memory_trig_1011ext.result@1.3, 2008-03-31 19:47:59+02:00, mleich@five.local.lan +69 -68
    Updated results

  mysql-test/suite/funcs_1/r/memory_views.result@1.7, 2008-03-31 19:47:59+02:00, mleich@five.local.lan +104 -102
    Updated results

  mysql-test/suite/funcs_1/r/myisam_func_view.result@1.4, 2008-03-31 19:47:59+02:00, mleich@five.local.lan +4600 -4374
    Updated results

  mysql-test/suite/funcs_1/r/myisam_storedproc_02.result@1.4, 2008-03-31 19:47:59+02:00, mleich@five.local.lan +46 -33
    Updated results

  mysql-test/suite/funcs_1/r/myisam_storedproc_03.result@1.4, 2008-03-31 19:47:59+02:00, mleich@five.local.lan +28 -20
    Updated results

  mysql-test/suite/funcs_1/r/myisam_storedproc_06.result@1.3, 2008-03-31 19:47:59+02:00, mleich@five.local.lan +31 -20
    Updated results

  mysql-test/suite/funcs_1/r/myisam_storedproc_07.result@1.4, 2008-03-31 19:47:59+02:00, mleich@five.local.lan +28 -20
    Updated results

  mysql-test/suite/funcs_1/r/myisam_storedproc_08.result@1.4, 2008-03-31 19:47:59+02:00, mleich@five.local.lan +28 -20
    Updated results

  mysql-test/suite/funcs_1/r/myisam_storedproc_10.result@1.4, 2008-03-31 19:47:59+02:00, mleich@five.local.lan +121 -36
    Updated results

  mysql-test/suite/funcs_1/r/myisam_trig_0102.result@1.4, 2008-03-31 19:47:59+02:00, mleich@five.local.lan +93 -92
    Updated results

  mysql-test/suite/funcs_1/r/myisam_trig_03.result@1.3, 2008-03-31 19:47:59+02:00, mleich@five.local.lan +133 -182
    Updated results

  mysql-test/suite/funcs_1/r/myisam_trig_0407.result@1.3, 2008-03-31 19:47:59+02:00, mleich@five.local.lan +84 -83
    Updated results

  mysql-test/suite/funcs_1/r/myisam_trig_08.result@1.5, 2008-03-31 19:47:59+02:00, mleich@five.local.lan +180 -142
    Updated results

  mysql-test/suite/funcs_1/r/myisam_trig_09.result@1.4, 2008-03-31 19:47:59+02:00, mleich@five.local.lan +81 -79
    Updated results

  mysql-test/suite/funcs_1/r/myisam_trig_1011ext.result@1.3, 2008-03-31 19:47:59+02:00, mleich@five.local.lan +75 -74
    Updated results

  mysql-test/suite/funcs_1/r/myisam_views.result@1.7, 2008-03-31 19:47:59+02:00, mleich@five.local.lan +11403 -11406
    Updated results

  mysql-test/suite/funcs_1/storedproc/cleanup_sp_tb.inc@1.2, 2008-03-31 19:48:00+02:00, mleich@five.local.lan +3 -2
    "--echo" instead of SQL command.

  mysql-test/suite/funcs_1/storedproc/load_sp_tb.inc@1.3, 2008-03-31 19:48:00+02:00, mleich@five.local.lan +80 -41
    Adjustment to new storage place of infile
    + correct formatting.

  mysql-test/suite/funcs_1/storedproc/storedproc_02.inc@1.3, 2008-03-31 19:48:00+02:00, mleich@five.local.lan +236 -112
    Backport from 5.1 + correct formatting.

  mysql-test/suite/funcs_1/storedproc/storedproc_03.inc@1.3, 2008-03-31 19:48:00+02:00, mleich@five.local.lan +59 -27
    Minor improvements + correct formatting.

  mysql-test/suite/funcs_1/storedproc/storedproc_06.inc@1.3, 2008-03-31 19:48:00+02:00, mleich@five.local.lan +41 -28
    Backport from 5.1 + correct formatting

  mysql-test/suite/funcs_1/storedproc/storedproc_10.inc@1.3, 2008-03-31 19:48:00+02:00, mleich@five.local.lan +76 -33
    Backport from 5.1. + correct formatting

  mysql-test/suite/funcs_1/t/innodb_trig_0407.test@1.3, 2008-03-31 19:48:00+02:00, mleich@five.local.lan +1 -1
    Cleanup

  mysql-test/suite/funcs_1/t/is_basics_mixed.test@1.2, 2008-03-31 19:48:00+02:00, mleich@five.local.lan +1 -1
    Adjustment to new storage place of outfile.

  mysql-test/suite/funcs_1/t/memory_storedproc_02.test@1.3, 2008-03-31 19:48:00+02:00, mleich@five.local.lan +2 -2
    Cleanup

  mysql-test/suite/funcs_1/t/memory_storedproc_03.test@1.3, 2008-03-31 19:48:00+02:00, mleich@five.local.lan +2 -2
    Cleanup

  mysql-test/suite/funcs_1/t/memory_storedproc_06.test@1.3, 2008-03-31 19:48:00+02:00, mleich@five.local.lan +2 -2
    Cleanup

  mysql-test/suite/funcs_1/t/memory_storedproc_07.test@1.3, 2008-03-31 19:48:00+02:00, mleich@five.local.lan +2 -2
    Cleanup

  mysql-test/suite/funcs_1/t/memory_storedproc_08.test@1.3, 2008-03-31 19:48:00+02:00, mleich@five.local.lan +2 -2
    Cleanup

  mysql-test/suite/funcs_1/t/memory_storedproc_10.test@1.3, 2008-03-31 19:48:00+02:00, mleich@five.local.lan +2 -2
    Cleanup

  mysql-test/suite/funcs_1/t/myisam_storedproc_02.test@1.3, 2008-03-31 19:48:00+02:00, mleich@five.local.lan +2 -2
    Cleanup

  mysql-test/suite/funcs_1/t/myisam_storedproc_03.test@1.3, 2008-03-31 19:48:00+02:00, mleich@five.local.lan +2 -2
    Cleanup

  mysql-test/suite/funcs_1/t/myisam_storedproc_06.test@1.3, 2008-03-31 19:48:00+02:00, mleich@five.local.lan +2 -2
    Cleanup

  mysql-test/suite/funcs_1/t/myisam_storedproc_07.test@1.3, 2008-03-31 19:48:00+02:00, mleich@five.local.lan +2 -2
    Cleanup

  mysql-test/suite/funcs_1/t/myisam_storedproc_08.test@1.3, 2008-03-31 19:48:00+02:00, mleich@five.local.lan +2 -2
    Cleanup

  mysql-test/suite/funcs_1/t/myisam_storedproc_10.test@1.3, 2008-03-31 19:48:00+02:00, mleich@five.local.lan +2 -2
    Cleanup

  mysql-test/suite/funcs_1/triggers/trig_frkey2.inc@1.2, 2008-03-31 19:48:00+02:00, mleich@five.local.lan +51 -51
    Cleanup

  mysql-test/suite/funcs_1/triggers/triggers_0102.inc@1.3, 2008-03-31 19:48:00+02:00, mleich@five.local.lan +114 -114
    Cleanup

  mysql-test/suite/funcs_1/triggers/triggers_03.inc@1.2, 2008-03-31 19:48:00+02:00, mleich@five.local.lan +49 -126
    Backport from 5.1

  mysql-test/suite/funcs_1/triggers/triggers_0407.inc@1.2, 2008-03-31 19:48:00+02:00, mleich@five.local.lan +109 -109
    Backport from 5.1

  mysql-test/suite/funcs_1/triggers/triggers_08.inc@1.2, 2008-03-31 19:48:00+02:00, mleich@five.local.lan +150 -129
    Backport from 5.1

  mysql-test/suite/funcs_1/triggers/triggers_09.inc@1.2, 2008-03-31 19:48:00+02:00, mleich@five.local.lan +76 -78
    Backport from 5.1

  mysql-test/suite/funcs_1/triggers/triggers_1011ext.inc@1.2, 2008-03-31 19:48:00+02:00, mleich@five.local.lan +21 -21
    Backport from 5.1

  mysql-test/suite/funcs_1/views/func_view.inc@1.3, 2008-03-31 19:48:00+02:00, mleich@five.local.lan +111 -163
    Backport from 5.1

  mysql-test/suite/funcs_1/views/views_master.inc@1.5, 2008-03-31 19:48:00+02:00, mleich@five.local.lan +3 -3
    Cleanup

ChangeSet@1.2485.36.2, 2008-03-26 14:52:10-04:00, cmiller@zippy.cornsilk.net +2 -0
  Fix minor complaints of Marc Alff, for patch against B-g#15776.

  mysql-test/t/type_blob.test@1.36, 2008-03-26 14:52:08-04:00, cmiller@zippy.cornsilk.net +4 -1
    Drop table in case we start from a bad state.

  sql/sql_yacc.yy@1.530.1.2, 2008-03-26 14:52:09-04:00, cmiller@zippy.cornsilk.net +1 -1
    yacc/bison is left-recursive, so FIXME statement is wrong.

ChangeSet@1.2485.36.1, 2007-08-31 15:24:43-04:00, cmiller@zippy.cornsilk.net +7 -0
  Bug#15776: 32-bit signed int used for length of blob
  
  Based on contributed patch from Martin Friebe, CLA from 2007-02-24.
  
  The parser lacked support for field sizes after signed long,
  when it should extend to 2**32-1.
  
  Now, we correct that limitation, and also make the error handling
  consistent for casts.

  mysql-test/r/type_blob.result@1.56, 2007-08-31 15:24:41-04:00, cmiller@zippy.cornsilk.net +147 -0
    Verify that blobs may be created with the size that is already
    documented.
    
    Additionally, test the limits of several other types.

  mysql-test/t/type_blob.test@1.35, 2007-08-31 15:24:41-04:00, cmiller@zippy.cornsilk.net +161 -0
    Verify that blobs may be created with the size that is already
    documented.
    
    Additionally, test the limits of several other types.

  sql/field.cc@1.359.1.1, 2007-08-31 15:24:41-04:00, cmiller@zippy.cornsilk.net +14 -2
    atoi() insufficient to gauge the length of some fields.  Change
    it to strtoul().

  sql/item_create.cc@1.68, 2007-08-31 15:24:41-04:00, cmiller@zippy.cornsilk.net +54 -3
    atoi() insufficient to gauge the length of some fields.  Change
    it to strtoul().
    
    If a casted length is too long, raise an error.

  sql/share/errmsg.txt@1.79.1.1, 2007-08-31 15:24:41-04:00, cmiller@zippy.cornsilk.net +30 -30
    Change ER_TOO_BIG_FIELDLENGTH so that it can accept sizes larger
    than 2**15 -- instead, 2**32.

  sql/sql_yacc.yy@1.530.1.1, 2007-08-31 15:24:41-04:00, cmiller@zippy.cornsilk.net +27 -28
    Make lengths take, in addition to NUM, LONG_NUM, ULONGLONG_NUM,
    and DECIMAL_NUM.

  sql/unireg.h@1.49.1.1, 2007-08-31 15:24:41-04:00, cmiller@zippy.cornsilk.net +1 -0
    Define new constant.

