- 09 Jan, 2007 2 commits
-
-
kroki/tomash@moonlight.home authored
into moonlight.home:/home/tomash/src/mysql_ab/mysql-4.1-bug23443
-
kroki/tomash@moonlight.home authored
server The problem was that when memory was exhausted HEAP engine could crash (GROUP BY uses HEAP TABLE). Alternatively, if SET was used, it could report an error "You may only use constant expressions with SET" instead of "Out of memory (Needed NNNNNN bytes)". The solution is: - pass MY_WME to (some) calls to my_malloc() to get correct message. - fix heap_write() so that the first key is skipped during cleanup on ENOMEM because it wasn't inserted and doesn't have to be deleted. No test case is provided because we can't test out-of-memory behaviour in our current test framework.
-
- 11 Nov, 2006 1 commit
-
-
Test for base directory when a RPM install corrected
-
- 10 Nov, 2006 6 commits
-
-
joerg@trift2. authored
into trift2.:/MySQL/M41/push-4.1
-
joerg@trift2. authored
into trift2.:/MySQL/M41/push-4.1
-
df@kahlann.erinye.com authored
into kahlann.erinye.com:/home/df/mysql/build/mtr-4.1
-
df@kahlann.erinye.com authored
-
petr/cps@outpost.site authored
into outpost.site:/home/cps/mysql/trees/4.1-runtime-bug9191
-
Added --force-restart pseudo server argument to shell version as well
-
- 09 Nov, 2006 1 commit
-
-
joerg@trift2. authored
Adapt to the different path of the server program, if installation was by RPM. Missing in the first changeset for bug#17194.
-
- 08 Nov, 2006 2 commits
-
-
joerg@trift2. authored
into trift2.:/MySQL/M41/clone-4.1
-
joerg@trift2. authored
into trift2.:/MySQL/M41/clone-4.1
-
- 07 Nov, 2006 3 commits
-
-
into mysql.com:/Users/kent/mysql/bk/lic/my41-lic
-
Added LICENSE.mysql, removed LICENSE.doc README.NW. Removed obselete section about MySQLEULA.txt and README.NW. README: Added reference to the EXCEPTIONS-CLIENT file. Changed reference to the commercial license file. Corrected references into chapters in the manual. .del-MySQLEULA.txt~4a1afd9284f9be5a: Delete: Docs/MySQLEULA.txt
-
joerg@trift2. authored
-
- 05 Nov, 2006 2 commits
-
-
petr/cps@outpost.site authored
into outpost.site:/home/cps/mysql/trees/4.1-runtime-bug9191
-
petr/cps@outpost.site authored
-
- 03 Nov, 2006 4 commits
-
-
msvensson@neptunus.(none) authored
-
kroki/tomash@moonlight.intranet authored
-
iggy@rolltop.ignatz42.dyndns.org authored
-
kent/mysqldev@suse9-x86.mysql.com authored
Create block around DBUG_ENTER late in function
-
- 02 Nov, 2006 8 commits
-
-
cmiller@zippy.cornsilk.net authored
-
cmiller@zippy.cornsilk.net authored
into zippy.cornsilk.net:/home/cmiller/work/mysql/mysql-4.1-maint
-
msvensson@shellback.(none) authored
into shellback.(none):/home/msvensson/mysql/mysql-4.1-maint
-
Raise version number to 4.1.23
-
thek@kpdesk.mysql.com authored
into kpdesk.mysql.com:/home/thek/dev/mysql-4.1-maint
-
thek@kpdesk.mysql.com authored
- 'false' not defined in C, use FALSE instead.
-
into mysql.com:/usr/home/ram/work/bug22913/my41-bug22913
-
We don't check for errors that may occur during data printing.
-
- 01 Nov, 2006 6 commits
-
-
kostja@bodhi.local authored
into bodhi.local:/opt/local/work/mysql-4.1-runtime
-
joerg@trift2. authored
Necessary changes if one of the test scripts is to be used with a RPM installation (bug#17194). This change handles finding the server and the other programs, but it does not solve the problem to get a writable "var" directory. If we want to avoid world-writable directories below "/usr/share/mysql-test" (and we do!), any automatic solution would require fixed decisions which may not match the local installation. For the Perl script, use "--vardir"; for the shell script, create "mysql-test/var" manually.
-
msvensson@shellback.(none) authored
into shellback.(none):/home/msvensson/mysql/mysql-4.1-maint
-
msvensson@shellback.(none) authored
into shellback.(none):/home/msvensson/mysql/mysql-4.1-maint
-
petr/cps@mysql.com/owlet.local authored
(4.1 version, with post-review fixes) The fix for another Bug (6439) limited FROM_UNIXTIME() to TIMESTAMP_MAX_VALUE which is 2145916799 or 2037-12-01 23:59:59 GMT, however unix timestamp in general is not considered to be limited by this value. All dates up to power(2,31)-1 are valid. This patch extends allowed TIMESTAMP range so, that max TIMESTAMP value is power(2,31)-1. It also corrects FROM_UNIXTIME() and UNIX_TIMESTAMP() functions, so that max allowed UNIX_TIMESTAMP() is power(2,31)-1. FROM_UNIXTIME() is fixed accordingly to allow conversion of dates up to 2038-01-19 03:14:07 UTC. The patch also fixes CONVERT_TZ() function to allow extended range of dates. The main problem solved in the patch is possible overflows of variables, used in broken-time representation to time_t conversion (required for UNIX_TIMESTAMP).
-
thek@kpdesk.mysql.com authored
into kpdesk.mysql.com:/home/thek/dev/mysql-4.1-maint
-
- 31 Oct, 2006 5 commits
-
-
msvensson@shellback.(none) authored
- Only read *.pid - Only allow it to contain a number
-
msvensson@shellback.(none) authored
-
msvensson@shellback.(none) authored
-
thek@kpdesk.mysql.com authored
- Because my_seek actually is capable of returning an error code we should exploit that in the best possible way. - There might be kernel errors or other errors we can't predict and capturing the return value of all system calls gives us better understanding of possible errors.
-
into mysql.com:/usr/home/ram/work/bug23412/my41-bug23412
-