- 09 Aug, 2006 1 commit
-
-
svoj@may.pils.ru authored
Problem described in this bug report affects MyISAM tables only. Running mysqld --flush instructs mysqld to sync all changes to disk after each SQL statement. It worked well for INSERT and DELETE statements, but it did sync for UPDATE only in case if there was index change (change of colum that has an index). If no updated column has an index, data wasn't synced to disk. This fix makes UPDATE statement to sync data to disk even if there is no index change (that is only data change) and mysqld is run with --flush option.
-
- 01 Aug, 2006 1 commit
-
-
into mysql.com:/users/lthalmann/bk/MERGE/mysql-4.1-merge
-
- 31 Jul, 2006 1 commit
-
-
into mysql.com:/users/lthalmann/bk/MERGE/mysql-4.1-merge
-
- 29 Jul, 2006 2 commits
-
-
into mysql.com:/Users/kent/mysql/bk/mysql-4.1
-
Corrected typo
-
- 28 Jul, 2006 4 commits
-
-
into mysql.com:/Users/kent/mysql/bk/mysql-4.1
-
Man page for mysqld command move to section 8 (bug#21220)
-
Man page for "mysqld" command move to section 8 (bug#21220)
-
Man page for "mysqld" command move to section 8 (bug#21220)
-
- 26 Jul, 2006 2 commits
-
-
kroki/tomash@moonlight.intranet authored
Too many cursors (more than 1024) could lead to memory corruption. This affects both, stored routines and C API cursors, and the threshold is per-server, not per-connection. Similarly, the corruption could happen when the server was under heavy load (executing more than 1024 simultaneous complex queries), and this is the reason why this bug is fixed in 4.1, which doesn't support cursors. The corruption was caused by a bug in the temporary tables code, when an attempt to create a table could lead to a write beyond allocated space. Note, that only internal tables were affected (the tables created internally by the server to resolve the query), not tables created with CREATE TEMPORARY TABLE. Another pre-condition for the bug is TRUE value of --temp-pool startup option, which, however, is a default. The cause of a bug was that random memory was overwritten in bitmap_set_next() due to out-of-bound memory access.
-
aivanov@mysql.com authored
-
- 24 Jul, 2006 5 commits
-
-
joerg@trift2. authored
into trift2.:/M41/push-4.1
-
joerg@trift2. authored
into trift2.:/M41/push-4.1
-
msvensson@neptunus.(none) authored
- Send confusing output to /dev/null
-
into mysql.com:/Users/kent/mysql/bk/mysql-4.1-new
-
Filter out strange control characters, messes up logs
-
- 23 Jul, 2006 1 commit
-
-
into mysql.com:/usr/home/ram/work/4.1.b16327
-
- 20 Jul, 2006 1 commit
-
-
holyfoot/hf@mysql.com/deer.(none) authored
into mysql.com:/home/hf/work/mysql-4.1.19983
-
- 19 Jul, 2006 2 commits
-
-
msvensson@neptunus.(none) authored
- backport patch from 5.0 - "table" can be NULL in temporary fields used for type conversion
-
Added new "mysql_explain_log" man page Added missing install of "myisam_ftdump" man page Added missing install of "mysqlman" man page
-
- 18 Jul, 2006 3 commits
-
-
evgen@moonbone.local authored
into moonbone.local:/work/tmp_merge-4.1-opt-mysql
-
evgen@moonbone.local authored
into moonbone.local:/work/tmp_merge-4.1-opt-mysql
-
Please use "ul" when merging this changeset to 5.0.
-
- 17 Jul, 2006 2 commits
-
-
joerg@trift2. authored
1) When initializing a boolean variable, do not use string representations '"false"' and '"true"' but rather the boolean values 'false' and 'true'. 2) Add the module to the various Windows description files.
-
joerg@trift2. authored
In 5.0, this is already solved, so that is a null-merge ("ul").
-
- 15 Jul, 2006 1 commit
-
-
pekka@orca.ndb.mysql.com authored
into orca.ndb.mysql.com:/space_old/pekka/ndb/version/my41-1.2461
-
- 14 Jul, 2006 5 commits
-
-
kent@mysql.com/g4-2.local authored
Command "ndb_mgm" is an optional tool, and should only be in "ndb-tools" package (bug#21058)
-
joerg@trift2. authored
-
into mysql.com:/usr/home/ram/work/4.1.b15195
-
to avoid the potential security problem. (see bug #15195: Security Breach with MERGE table)
-
gkodinov/kgeorge@rakia.(none) authored
into rakia.(none):/home/kgeorge/mysql/autopush/B17212-4.1-opt
-
- 13 Jul, 2006 6 commits
-
-
holyfoot/hf@mysql.com/deer.(none) authored
into mysql.com:/home/hf/work/mysql-4.1.16017
-
holyfoot/hf@mysql.com/deer.(none) authored
into mysql.com:/home/hf/work/mysql-4.1.16017
-
cmiller@zippy.(none) authored
into zippy.(none):/home/cmiller/work/mysql/m41-maint--07AB5
-
cmiller@zippy.(none) authored
into zippy.(none):/home/cmiller/work/mysql/m41-maint--07AB5
-
into anubis.greendragongames.com:/home/greenman/workspace-mysql/mysql/pending/bug-4.1-15977
-
do not look for client-specific commands while inside a multi-line comment. we will allow multi-comments pretty much anywhere within SQL-statements, but client-specific commands (help, use, print, ...) must be the first token in the input.
-
- 12 Jul, 2006 3 commits
-
-
mkindahl@dl145k.mysql.com authored
into dl145k.mysql.com:/data0/mkindahl/bk/mysql-4.1-rpl
-
gkodinov/kgeorge@macbook.gmz authored
* don't use join cache when the incoming data set is already ordered for ORDER BY This choice must be made because join cache will effectively reverse the join order and the results will be sorted by the index of the table that uses join cache.
-
cmiller@maint1.mysql.com authored
into maint1.mysql.com:/data/localhome/cmiller/mysql-4.1
-