- 12 Oct, 2006 5 commits
-
-
kaa@polly.local authored
into polly.local:/home/kaa/src/maint/mysql-5.0-maint
-
kaa@polly.local authored
into polly.local:/home/kaa/src/maint/mysql-5.0-maint
-
kaa@polly.local authored
-
tsmith/tim@siva.hindu.god authored
into siva.hindu.god:/usr/home/tim/m/bk/tmp/50
-
tsmith/tim@siva.hindu.god authored
-
- 11 Oct, 2006 5 commits
-
-
andrey@example.com authored
into example.com:/work/bug23074/my50-bug23074
-
kaa@polly.local authored
into polly.local:/tmp/maint/bug11655/my50-bug11655
-
andrey@example.com authored
into example.com:/work/bug23074/my50-bug23074
-
andrey@example.com 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
-
Kristofer.Pettersson@naruto. authored
into naruto.:C:/cpp/mysql-5.0-maint
-
- 09 Oct, 2006 5 commits
-
-
cmiller@zippy.cornsilk.net authored
into zippy.cornsilk.net:/home/cmiller/work/mysql/bug17583/my50-bug17583
-
cmiller@zippy.cornsilk.net authored
Porting forward tests to replacement files.
-
cmiller@zippy.cornsilk.net authored
into zippy.cornsilk.net:/home/cmiller/work/mysql/bug17583/my50-bug17583
-
cmiller@zippy.cornsilk.net 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.
-
tsmith/tim@siva.hindu.god authored
into siva.hindu.god:/usr/home/tim/m/bk/tmp/50
-
- 04 Oct, 2006 8 commits
-
-
iggy@rolltop.ignatz42.dyndns.org authored
into rolltop.ignatz42.dyndns.org:/mnt/storeage/mysql-5.0-maint
-
iggy@rolltop.ignatz42.dyndns.org authored
into rolltop.ignatz42.dyndns.org:/mnt/storeage/bug19660/my50-bug19660
-
cmiller@zippy.cornsilk.net authored
into zippy.cornsilk.net:/home/cmiller/work/mysql/bug19356/my50-bug19356
-
cmiller@zippy.cornsilk.net authored
The executing code had a safety assertion so that it refused to free Items that it didn't create. However, there is a case, undefined user variables, which would put Items into the list to be freed. Instead, do something that is more risky in expectation that the code will be refactored soon, as Kostja wants to do: Remove the assertions from prepare() and execute(). Put one assertion at a higher level, before stmt->set_params_from_vars(), which may then create new to-be-freed Items .
-
iggy@rolltop.ignatz42.dyndns.org authored
into rolltop.ignatz42.dyndns.org:/mnt/storeage/mysql-5.0-maint
-
iggy@rolltop.ignatz42.dyndns.org authored
The server variable warning_count should include the number of warnings, errors and notes according to the manual
-
kaa@polly.local 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
-
tsmith/tim@siva.hindu.god authored
Set a flag when a SHOW command is parsed, and check it in log_slow_statement(). SHOW commands are not counted as slow queries, even if they use table scans.
-
- 03 Oct, 2006 9 commits
-
-
iggy@rolltop.ignatz42.dyndns.org authored
-
msvensson@neptunus.(none) authored
into neptunus.(none):/home/msvensson/mysql/mysql-5.0-maint
-
msvensson@neptunus.(none) authored
into neptunus.(none):/home/msvensson/mysql/mysql-5.0-maint
-
msvensson@shellback.(none) authored
into shellback.(none):/home/msvensson/mysql/mysql-5.0-maint
-
into mysql.com:/usr/home/bar/mysql-5.0-rpl
-
msvensson@shellback.(none) authored
into shellback.(none):/home/msvensson/mysql/mysql-5.0-maint
-
msvensson@shellback.(none) authored
into shellback.(none):/home/msvensson/mysql/mysql-4.1-maint
-
into mysql.com:/usr/home/bar/mysql-4.1-rpl
-
into mysql.com:/usr/home/ram/work/bug22271/my50-bug22271
-
- 02 Oct, 2006 8 commits
-
-
msvensson@shellback.(none) authored
into shellback.(none):/home/msvensson/mysql/mysql-5.0-maint
-
msvensson@shellback.(none) authored
into shellback.(none):/home/msvensson/mysql/mysql-5.0-maint
-
msvensson@shellback.(none) authored
into shellback.(none):/home/msvensson/mysql/mysql-5.0
-
msvensson@shellback.(none) authored
into shellback.(none):/home/msvensson/mysql/mysql-4.1-maint
-
msvensson@shellback.(none) authored
This was available from gcc 3.1, so diable it before that Update m_ctype.h to use the new macro
-
tsmith/tim@siva.hindu.god authored
into siva.hindu.god:/usr/home/tim/m/bk/41
-
tsmith/tim@siva.hindu.god authored
into siva.hindu.god:/usr/home/tim/m/bk/41
-
tsmith/tim@siva.hindu.god authored
into siva.hindu.god:/usr/home/tim/m/bk/40
-