- 11 Oct, 2006 8 commits
-
-
unknown authored
into polly.local:/home/kaa/src/maint/m41-maint--07OGk
-
unknown authored
into polly.local:/home/kaa/src/maint/m41-maint--07OGk sql/item_timefunc.cc: Auto merged
-
unknown authored
into example.com:/work/bug23074/my41-bug23074
-
unknown authored
sql/item_timefunc.cc: Exclude
-
unknown authored
into polly.local:/home/kaa/src/maint/m41-maint--07OGk sql/item_timefunc.cc: Auto merged
-
unknown authored
into polly.local:/home/kaa/src/maint/m41-maint--07OGk sql/field.cc: Auto merged sql/item_timefunc.cc: Auto merged mysql-test/r/func_time.result: Manually merged mysql-test/t/func_time.test: Manually merged
-
unknown authored
set. This has always worked because when flag is !=0 then HA_VAR_LENGTH_KEY is always set. Therefore, a test case cannot reveal a faulty behavior. Fix for bug#23074: typo in myisam/sort.c myisam/sort.c: fix typo. Nevertheless, it has worked as expected because when a bit in flag is set HA_VAR_LENGTH_KEY has been always set too. Actually, no problem exposed through DDL.
-
unknown authored
into naruto.:C:/cpp/mysql-4.1-maint sql/item_timefunc.cc: Auto merged
-
- 09 Oct, 2006 2 commits
-
-
unknown authored
into zippy.cornsilk.net:/home/cmiller/work/mysql/bug17583/my41-bug17583 client/mysql.cc: Auto merged
-
unknown authored
When the client program had its stdout file descriptor closed by the calling shell, after some amount of work (enough to fill a socket buffer) the server would complain about a packet error and then disconnect the client. This is a serious security problem. If stdout is closed before the mysql is exec()d, then the first socket() call allocates file number 1 to communicate with the server. Subsequent write()s to that file number (as when printing results that come back from the database) go back to the server instead in the command channel. So, one should be able to craft data which, upon being selected back from the server to the client, and injected into the command stream become valid MySQL protocol to do something nasty when sent /back/ to the server. The solution is to close explicitly the file descriptor that we *printf() to, so that the libc layer and the OS layer both agree that the file is closed. BitKeeper/etc/collapsed: BitKeeper file /home/cmiller/work/mysql/bug17583/my41-bug17583/BitKeeper/etc/collapsed client/mysql.cc: If standard output is not open (specifically, if dup() of its file number fails) then we explicitly close it so that future uses of the file descriptor behave correctly for a closed file. mysql-test/r/mysql_client.result: Prove that the problem of writing SQL output to the command socket no longer exists. mysql-test/t/mysql_client.test: Prove that the problem of writing SQL output to the command socket no longer exists.
-
- 04 Oct, 2006 2 commits
-
-
unknown authored
into rolltop.ignatz42.dyndns.org:/mnt/storeage/mysql-4.1-maint client/mysqldump.c: Auto merged
-
unknown authored
- bug #11655 "Wrong time is returning from nested selects - maximum time exists - input and output TIME values were not validated properly in several conversion functions - bug #20927 "sec_to_time treats big unsigned as signed" - integer overflows were not checked in several functions. As a result, input values like 2^32 or 3600*2^32 were treated as 0 - BIGINT UNSIGNED values were treated as SIGNED in several functions - in cases where both input string truncation and out-of-range TIME value occur, only 'truncated incorrect time value' warning was produced include/my_time.h: Added defines for the TIME limits Added defines for the warning flags set by str_to_time() and check_time_range() Added check_time_range() declaration mysql-test/r/func_sapdb.result: Fixed testcases which relied on incorrect TIMEDIFF() behaviour mysql-test/r/func_time.result: Fixed testcase which relied on incorrect behaviour Added testcases for out-of-range values in SEC_TO_TIME(), TIME_TO_SEC(), ADDTIME(), SUBTIME() and EXTRACT() mysql-test/t/func_time.test: Added testcases for out-of-range values in SEC_TO_TIME(), TIME_TO_SEC(), ADDTIME(), SUBTIME() and EXTRACT() sql-common/my_time.c: Added check_time_range() to be used from str_to_time() and item_timefunc.cc Added new out-of-range flag to str_to_time() warnings Use '%u' instead of '%d' in my_*_to_str() because the arguments are unsigned sql/field.cc: Replaced out-of-range checks with checks for flags returned by str_to_time() sql/item_timefunc.cc: Added wrappers over make_datetime() and make_time() which perform out-of-range checks on input values Moved common code in Item_func_sec_to_time::val_str() and Item_func_sec_to_time::val_int() into a separate function sec_to_time() Replaced calls to make_datetime() with make_datetime_with_warn() in Item_func_add_time and Item_func_timediff Checks for 'unsigned int' overflows in Item_func_maketime Use make_time_with_warn() instead of make_time() in Item_func_maketime Fixed incorrect sizeof() in Item_func_str_to_date::get_time() sql/time.cc: Check for return value of str_to_time() along with warning flags
-
- 03 Oct, 2006 8 commits
-
-
unknown authored
client/mysqldump.c: Bug#19660 mysqldump --single-transaction should be with CONSISTENT SNAPSHOT - Remove old BEGIN syntax and replace with START TRANSATION. Add CONSISTENT SNAPSHOT option for servers that support it.
-
unknown authored
into neptunus.(none):/home/msvensson/mysql/mysql-4.1-maint
-
unknown authored
into neptunus.(none):/home/msvensson/mysql/mysql-4.1-maint
-
unknown authored
into neptunus.(none):/home/msvensson/mysql/mysql-4.1-maint sql/item_func.cc: Auto merged
-
unknown authored
into neptunus.(none):/home/msvensson/mysql/mysql-4.1-maint
-
unknown authored
into shellback.(none):/home/msvensson/mysql/mysql-4.1-maint
-
unknown authored
into mysql.com:/usr/home/bar/mysql-4.1-rpl mysql-test/r/cast.result: Auto merged mysql-test/r/ps.result: Auto merged sql/item_func.cc: Auto merged
-
unknown authored
into mockturtle.local:/home/dlenev/src/mysql-4.1-rt-merge sql/sql_select.cc: Auto merged
-
- 02 Oct, 2006 13 commits
-
-
unknown authored
into shellback.(none):/home/msvensson/mysql/mysql-4.1-maint
-
unknown authored
This was available from gcc 3.1, so diable it before that Update m_ctype.h to use the new macro include/m_ctype.h: Use macro ATTRIBUTE_FORMAT_FPTR on function pointer include/my_global.h: Add ATTRIBUTE_FORMAT_FPTR macro for setting format specifier also on function pointers This was available from gcc 3.1, so diable it before that
-
unknown authored
into siva.hindu.god:/usr/home/tim/m/bk/41 scripts/mysqlhotcopy.sh: Auto merged
-
unknown authored
into siva.hindu.god:/usr/home/tim/m/bk/41
-
unknown authored
into siva.hindu.god:/usr/home/tim/m/bk/40
-
unknown authored
-
unknown authored
When compiling with qcc on QNC the define __GNUC__will be set although it doesn't support full GNU syntax - disable __attribute__ when using qcc include/my_global.h: Disable __attribute__ when compiling with qcc
-
unknown authored
-
unknown authored
-
unknown authored
into neptunus.(none):/home/msvensson/mysql/mysql-4.1-maint mysql-test/r/ctype_utf8.result: Auto merged mysql-test/t/ctype_utf8.test: Auto merged
-
unknown authored
into neptunus.(none):/home/msvensson/mysql/mysql-4.1-maint mysql-test/r/ctype_utf8.result: Manual merge mysql-test/t/ctype_utf8.test: Manual merge
-
unknown authored
into mysql.com:/home/svoj/devel/mysql/merge/mysql-4.1-engines
-
unknown authored
into mysql.com:/home/svoj/devel/mysql/merge/mysql-4.1-engines mysql-test/r/myisam.result: Auto merged mysql-test/t/myisam.test: Auto merged sql/table.cc: Auto merged
-
- 30 Sep, 2006 3 commits
-
-
unknown authored
into rama.(none):/home/jimw/my/mysql-4.1-clean include/my_global.h: Auto merged
-
unknown authored
include/my_global.h: Disable __attribute__ on g++ < 3.4. There are actually some forms of it that are supported, but rather than create more ATTRIBUTE_<foo> macros to handle them, it is easier to just disable them all. We will catch the compiler warnings with more recent versions of g++.
-
unknown authored
into rama.(none):/home/jimw/my/mysql-4.1-clean
-
- 29 Sep, 2006 4 commits