- 26 Oct, 2007 1 commit
-
-
istruewing@stella.local authored
Disabling and enabling indexes on a non-empty table grows the index file. Disabling indexes just sets a flag per non-unique index and does not free the index blocks of the affected indexes. Re-enabling indexes creates new indexes with new blocks. The old blocks remain unused in the index file. Fixed by dropping and re-creating all indexes if non-empty disabled indexes exist when enabling indexes. Dropping all indexes resets the internal end-of-file marker to the end of the index file header. It also clears the root block pointers of every index and clears the deleted blocks chains. This way all blocks are declared as free.
-
- 10 Oct, 2007 1 commit
-
-
istruewing@stella.local authored
into stella.local:/home2/mydev/mysql-5.0-axmrg
-
- 09 Oct, 2007 2 commits
-
-
istruewing@stella.local authored
into stella.local:/home2/mydev/mysql-5.0-bug15522
-
istruewing@stella.local authored
Added test case. The fix for Bug#20662 does also fix this one.
-
- 04 Oct, 2007 3 commits
-
-
joerg@trift2. authored
into trift2.:/MySQL/M50/push-5.0
-
jperkin@production.mysql.com authored
into production.mysql.com:/usersnfs/jperkin/bk/bug-27692/5.0
-
jperkin@production.mysql.com authored
were accidentally removed during a previous rototill of this code. Fixes bug#27692. While it can be argued we should strive to provide a 'secure by default' installation, this happens to be the setup currently documented in the manual as the default, so defer changes that improve security out of the box to a co-ordinated effort later on. For now, make a note about the test databases and anonymous user in mysql_install_db and recommend that mysql_secure_installation be ran for users wishing to remove these defaults. [..re-commit of previously lost change..]
-
- 02 Oct, 2007 1 commit
-
-
Updated variable size arrays to use vector like Jonas did for 5.1 so that my build would not break
-
- 01 Oct, 2007 1 commit
-
-
joerg@trift2. authored
into trift2.:/MySQL/M50/push-5.0
-
- 28 Sep, 2007 3 commits
-
-
istruewing@stella.local authored
into stella.local:/home2/mydev/mysql-5.0-axmrg
-
istruewing@stella.local authored
into stella.local:/home2/mydev/mysql-5.0-axmrg
-
istruewing@stella.local authored
into stella.local:/home2/mydev/mysql-4.1-axmrg
-
- 27 Sep, 2007 2 commits
-
-
df@pippilotta.erinye.com authored
into pippilotta.erinye.com:/shared/home/df/mysql/build/mysql-5.0-build
-
df@pippilotta.erinye.com authored
-
- 26 Sep, 2007 1 commit
-
-
- 25 Sep, 2007 1 commit
-
-
df@pippilotta.erinye.com authored
into pippilotta.erinye.com:/shared/home/df/mysql/build/mysql-5.0-build
-
- 22 Sep, 2007 1 commit
-
-
jonathan@bagpuss.adsl.perkin.org.uk authored
cmake list are auto-generated and thus still required. Correct fix not yet known.
-
- 20 Sep, 2007 2 commits
-
-
gluh@mysql.com/eagle.(none) authored
-
gluh@mysql.com/eagle.(none) authored
added get_field_default_value() function which obtains default value from the field (used in store_create_info() & get_schema_column_record() functions)
-
- 19 Sep, 2007 1 commit
-
-
gluh@eagle.(none) authored
into mysql.com:/home/gluh/MySQL/Merge/5.0-opt
-
- 15 Sep, 2007 1 commit
-
-
gshchepa@devsrv-b.mysql.com authored
Post-fix for bug#27695.
-
- 14 Sep, 2007 17 commits
-
-
gshchepa@devsrv-b.mysql.com authored
into devsrv-b.mysql.com:/data0/gshchepa/mysql-5.0-opt
-
joerg@trift2. authored
into trift2.:/MySQL/M50/push-5.0
-
joerg@trift2. authored
into trift2.:/MySQL/M50/push-5.0
-
joerg@trift2. authored
into trift2.:/MySQL/M41/push-4.1
-
gkodinov/kgeorge@magare.gmz authored
into magare.gmz:/home/kgeorge/mysql/autopush/B31001-5.0-opt
-
gkodinov/kgeorge@magare.gmz authored
The optimizer sets index traversal in reverse order only if there are used key parts that are not compared to a constant. However using the primary key as an ORDER BY suffix rendered the check incomplete : going in reverse order must still be used even if all the parts of the secondary key are compared to a constant. Fixed by relaxing the check and set reverse traversal even when all the secondary index keyparts are compared to a const. Also account for the case when all the primary keys are compared to a constant.
-
sergefp@pylon.mylan authored
into mysql.com:/home/psergey/mysql-5.0-bug30324
-
sergefp@mysql.com authored
- The bug was caused by COUNT(DISTINCT ...) code using Unique object in a way that assumed that BIT(N) column occupies a contiguous space in temp_table->record[0] buffer. - The fix is to make COUNT(DISTINCT ...) code instruct create_tmp_table to create temporary table with column of type BIGINT, not BIT(N).
-
tomas@whalegate.ndb.mysql.com authored
into whalegate.ndb.mysql.com:/home/tomas/mysql-5.0-ndb-merge
-
tomas@whalegate.ndb.mysql.com authored
into whalegate.ndb.mysql.com:/home/tomas/mysql-5.0-ndb-merge
-
istruewing@stella.local authored
into stella.local:/home/mydev/mysql-5.0-axmrg
-
istruewing@stella.local authored
into stella.local:/home/mydev/mysql-5.0-axmrg
-
istruewing@stella.local authored
into stella.local:/home/mydev/mysql-5.0-axmrg
-
gshchepa@devsrv-b.mysql.com authored
into devsrv-b.mysql.com:/data0/gshchepa/mysql-5.0-opt
-
gshchepa/uchum@gleb.loc authored
into gleb.loc:/home/uchum/work/bk/5.0-opt-27695
-
istruewing@stella.local authored
into stella.local:/home/mydev/mysql-4.1-axmrg
-
gshchepa/uchum@gleb.loc authored
into gleb.loc:/home/uchum/work/bk/5.0-opt
-
- 13 Sep, 2007 2 commits
-
-
joerg@trift2. authored
into trift2.:/MySQL/M50/tmp-5.0
-
gshchepa/uchum@gleb.loc authored
Declaring an all space column name in the SELECT FROM DUAL or in a view leads to misleading warning message: "Leading spaces are removed from name ' '". The Item::set_name method has been modified to raise warnings like "Name ' ' has become ''" in case of the truncation of an all space identifier to an empty string identifier instead of the "Leading spaces are removed from name ' '" warning message.
-