- 18 Apr, 2008 2 commits
- 17 Apr, 2008 2 commits
- 16 Apr, 2008 5 commits
- 15 Apr, 2008 2 commits
- 14 Apr, 2008 2 commits
- 11 Apr, 2008 3 commits
- 10 Apr, 2008 9 commits
-
-
unknown authored
into zippy.cornsilk.net:/home/cmiller/work/mysql/mysql-5.1-build
-
unknown authored
into zippy.cornsilk.net:/home/cmiller/work/mysql/mysql-5.1-build mysql-test/t/type_blob.test: Auto merged sql/field.cc: Auto merged sql/sql_yacc.yy: Auto merged sql/tztime.cc: Auto merged sql/unireg.h: Auto merged sql/share/errmsg.txt: Auto merged mysql-test/r/type_blob.result: manual merge sql/item_create.cc: manual merge
-
unknown authored
sql/field.cc: Fix indentation of new line.
-
unknown authored
into hh-nb.hungers:/work/merge/mysql-5.1-build BitKeeper/etc/ignore: auto-union
-
unknown authored
BitKeeper/etc/ignore: Added mysql-test/linux_sys_vars.inc mysql-test/load_sysvars.inc mysql-test/windows_sys_vars.inc to the ignore list
-
unknown authored
-
unknown authored
into zippy.cornsilk.net:/home/cmiller/work/mysql/mysql-5.1-build
-
unknown authored
into zippy.cornsilk.net:/home/cmiller/work/mysql/mysql-5.1-build sql/field.cc: Auto merged sql/unireg.h: Auto merged mysql-test/r/type_blob.result: manual merge. mysql-test/t/type_blob.test: manual merge. sql/item_create.cc: manual merge. sql/share/errmsg.txt: manual merge. sql/sql_yacc.yy: manual merge.
-
unknown authored
into zippy.cornsilk.net:/home/cmiller/work/mysql/mysql-5.0-build mysql-test/r/type_blob.result: Auto merged mysql-test/t/type_blob.test: Auto merged sql/field.cc: Auto merged sql/item_create.cc: Auto merged sql/share/errmsg.txt: Auto merged sql/sql_yacc.yy: Auto merged sql/unireg.h: Auto merged
-
- 09 Apr, 2008 7 commits
-
-
unknown authored
into zippy.cornsilk.net:/home/cmiller/work/mysql/bug15776-encore/my51-bug15776-encore sql/field.cc: Auto merged sql/item_create.cc: Auto merged sql/share/errmsg.txt: Auto merged sql/unireg.h: Auto merged mysql-test/r/type_blob.result: manual merge. mysql-test/t/type_blob.test: manual merge. sql/sql_yacc.yy: merge by hand.
-
unknown authored
into zippy.cornsilk.net:/home/cmiller/work/mysql/bug15776/my51-bug15776 mysql-test/r/type_blob.result: Auto merged mysql-test/t/type_blob.test: Auto merged sql/field.cc: Auto merged sql/unireg.h: Auto merged
-
unknown authored
into zippy.cornsilk.net:/home/cmiller/work/mysql/bug15776-encore/my50-bug15776-encore sql/field.cc: Auto merged sql/item_create.cc: Auto merged sql/sql_yacc.yy: Auto merged sql/share/errmsg.txt: Auto merged sql/unireg.h: Auto merged mysql-test/r/type_blob.result: manual merge. mysql-test/t/type_blob.test: manual merge.
-
unknown authored
into zippy.cornsilk.net:/home/cmiller/work/mysql/mysql-5.0-build mysql-test/r/type_blob.result: Auto merged mysql-test/t/type_blob.test: Auto merged sql/field.cc: Auto merged sql/unireg.h: Auto merged
-
unknown authored
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: 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: 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: 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: Make BLOB size the maximum that the packed value in field_blob::get_length() allows.
-
unknown authored
into five.local.lan:/work/trees/mysql-5.1-build-src-clean
-
unknown authored
#12713 Error in a stored function called from a SELECT doesn't cause ROLLBACK of statem mysql-test/r/func_rollback.result: Expected results mysql-test/t/func_rollback.test: New test
-
- 08 Apr, 2008 4 commits
-
-
unknown authored
into mysql1000.(none):/home/andrei/MySQL/BARE/mysql-5.1-release
-
unknown authored
Add ChangeLog if it exists - Removed separate 'normal+rowrepl' test run, not needed any longer - Removed separate 'rpl' test run, included in main test run already - Renamed some test "comments", to use similar naming style - Limited one of the Cluster test runs to 'ndb' and 'rpl_ndb' suites - Reordered test runs, to be aligned with Windows test runs mysql.spec.sh: - No longer including the "Example" storage engine - Added to configure "--without-ENGINE" if not to compile engine as plugin Docs/Makefile.am: Add ChangeLog if it exists Makefile.am: - Removed separate 'normal+rowrepl' test run, not needed any longer - Removed separate 'rpl' test run, included in main test run already - Renamed some test "comments", to use similar naming style - Limited one of the Cluster test runs to 'ndb' and 'rpl_ndb' suites - Reordered test runs, to be aligned with Windows test runs support-files/mysql.spec.sh: - No longer including the "Example" storage engine - Added to configure "--without-ENGINE" if not to compile engine as plugin
-
unknown authored
Among two claimed artifacts the critical one is in that the Table map of a query following the failing with a duplicate key error CREATE-SELECT is skipped from instantionating (and thus binlogging). That leads to sending a "chopped" group of the data row-events without the table map head to the slave. The slave can not apply the only data row events. It's not easy to force the slave to react with an error in such a case (the second complaint on the bug report), because the lack of a table Rows_log_event::do_apply_event the data row event handler is a common situation which normally designates the event has to be filtered out basing on the repliation do/ingore rules decision. Fixed: table map creating and binlogging is restored via deploying the standard cleanup call in select_create::abort(). No error is reported if by chance the table map was not been binlogged. Leaving this out to resolve with considering how to combine the do/ingore rules with the situation when erronoulsy the Table_map is not written to binlog. mysql-test/suite/rpl/r/rpl_row_create_table.result: results changed mysql-test/suite/rpl/t/rpl_row_create_table.test: regression test for the bug sql/sql_insert.cc: adding resetting of thd binlogging state that was missed for the particular case of failing CREATE..SELECT
-
unknown authored
Problem: SELECTs prohibited for a transactional SE in autocommit mode if read_only is set. Fix: allow them. mysql-test/r/read_only_innodb.result: Fix for bug #35732: read-only blocks SELECT statements in InnoDB - test result. mysql-test/t/read_only_innodb.test: Fix for bug #35732: read-only blocks SELECT statements in InnoDB - test case. sql/handler.cc: Fix for bug #35732: read-only blocks SELECT statements in InnoDB - in autocommit mode thd->transaction.all list is empty thus is_real_trans set to TRUE for any SELECTs, so using it in the "read_only" check is insufficient. ha_check_and_coalesce_trx_read_only() changed to return number of engines with read-write changes. This value is used in the "read-only" check and checks for GLOBAL READ LOCK. sql/lock.cc: Fix for bug #35732: read-only blocks SELECT statements in InnoDB - added assert(protect_against_global_read_lock) before decreasing, in order to catch (uint) 0 - 1 situation due to wrong wait_if_global_read_lock()/start_waiting_global_read_lock() call sequence.
-
- 05 Apr, 2008 2 commits
- 04 Apr, 2008 2 commits
-
-
unknown authored
into trift2.:/MySQL/M51/tmp-5.1
-
unknown authored
into trift2.:/MySQL/M51/tmp-5.1 Null merge - changes specific to 5.1.24-rc are superseded by better ones done in parallel. mysql-test/suite/funcs_1/r/innodb_storedproc_02.result: Null merge. mysql-test/suite/funcs_1/r/innodb_trig_03e.result: Null merge. mysql-test/suite/funcs_1/r/memory_storedproc_02.result: Null merge. mysql-test/suite/funcs_1/r/memory_trig_03e.result: Null merge. mysql-test/suite/funcs_1/r/myisam_storedproc_02.result: Null merge. mysql-test/suite/funcs_1/r/myisam_trig_03e.result: Null merge. mysql-test/suite/funcs_1/r/ndb_storedproc_02.result: Null merge. mysql-test/suite/funcs_1/r/ndb_trig_03e.result: Null merge. mysql-test/suite/funcs_1/storedproc/storedproc_02.inc: Null merge. mysql-test/suite/funcs_1/storedproc/storedproc_master.inc: Null merge. mysql-test/suite/funcs_1/r/innodb_storedproc.result: Null merge - changes specific to 5.1.24-rc are superseded by better ones done in parallel. mysql-test/suite/funcs_1/r/memory_storedproc.result: Null merge - changes specific to 5.1.24-rc are superseded by better ones done in parallel. mysql-test/suite/funcs_1/r/myisam_storedproc.result: Null merge - changes specific to 5.1.24-rc are superseded by better ones done in parallel. mysql-test/suite/funcs_1/r/ndb_storedproc.result: Null merge - changes specific to 5.1.24-rc are superseded by better ones done in parallel.
-