An error occurred fetching the project authors.
- 16 Mar, 2006 1 commit
-
-
mikael@zim.(none) authored
A crash after ALTER TABLE t1 RENAME ...
-
- 14 Mar, 2006 1 commit
-
-
mikael@zim.(none) authored
-
- 13 Mar, 2006 2 commits
-
-
jimw@mysql.com authored
When doing an ALTER TABLE on a table using partitioning, force the table definition to get reloaded, since it may become invalid whenever the ALTER TABLE fails (even for an ALTER TABLE without specific partitioning changes).
-
mikael@zim.(none) authored
-
- 11 Mar, 2006 2 commits
-
-
mikael@zim.(none) authored
Made sure that no subpartition stuff in non-subpartitioned table
-
mikael@zim.(none) authored
with ALTER TABLE ADD/REORGANIZE PARTITION Ensure that default subpartitioning is removed when subpartitions are defined in ADD/REORGANIZE PARTITION
-
- 09 Mar, 2006 2 commits
-
-
mikael@zim.(none) authored
-
mikron@mikael-ronstr-ms-dator.local authored
-
- 08 Mar, 2006 2 commits
-
-
jimw@mysql.com authored
Make partitioned tables report the row format of the underlying tables (when they are all the same).
-
jimw@mysql.com authored
Temporary tables are no longer allowed to be partitioned.
-
- 07 Mar, 2006 1 commit
-
-
gluh@eagle.intranet.mysql.r18.ru authored
NULL value handling
-
- 01 Mar, 2006 1 commit
-
-
gluh@eagle.intranet.mysql.r18.ru authored
store copy of partition function string
-
- 24 Feb, 2006 2 commits
-
-
reggie@linux.site authored
BUG# 17432: Partitions: wrong result, SELECT ... WHERE <column> is null
-
reggie@linux.site authored
BUG# 17430 Partitions: crash on SELECT * FROM t1 WHERE f_int1 IS NULL
-
- 16 Feb, 2006 3 commits
-
-
jimw@mysql.com authored
a partitioned table, the value of auto_increment fields was not calculated until after deciding what partition to add the row into, which led to rows being written to the wrong partitions (or spurious errors).
-
jimw@mysql.com authored
When creating a new partition, a bogus memory allocation problem was reported.
-
jimw@mysql.com authored
-
- 15 Feb, 2006 3 commits
-
-
jimw@mysql.com authored
KEY event. Partitioning wrongly claimed to be able to handle HA_DUPP_POS when it was supported by the underlying storage engine, which resulted in a crash when handling REPLACE statements.
-
gluh@eagle.intranet.mysql.r18.ru authored
In presense of subpartitioning use get_part_partition_id() to calculate part_id
-
gluh@eagle.intranet.mysql.r18.ru authored
use part_info->no_subparts to calculate partition range in case of subpartitions
-
- 13 Feb, 2006 1 commit
-
-
jimw@mysql.com authored
used. The problem is that the actual engine was not stored in the .par file, causing confusion when the default engine was changed. Now the actual storage engine is stored for subpartitions, as was intended.
-
- 17 Jan, 2006 1 commit
-
-
Optimised version of ADD/DROP/REORGANIZE partitions for non-NDB storage engines. New syntax to handle REBUILD/OPTIMIZE/ANALYZE/CHECK/REPAIR partitions Quite a few bug fixes
-
- 04 Jan, 2006 1 commit
-
-
sergefp@mysql.com authored
- post-...-post review fixes - Added "integer range walking" that allows to do partition pruning for "a <=? t.field <=? b" by finding used partitions for a, a+1, a+2, ..., b-1, b.
-
- 27 Dec, 2005 1 commit
-
-
sergefp@mysql.com authored
-
- 15 Dec, 2005 1 commit
-
-
holyfoot@deer.(none) authored
-
- 21 Nov, 2005 1 commit
-
-
patg@krsna.patg.net authored
Post-review fixes to original changeset http://lists.mysql.com/internals/32422
-
- 19 Nov, 2005 1 commit
-
-
patg@krsna.patg.net authored
Patch that fixes crashing when partition uses blackole for underlying tables.
-
- 20 Sep, 2005 2 commits
-
-
partitioned tables
-
Select count(*) returned 2 on empty table where handler used exact count
-
- 14 Sep, 2005 1 commit
-
-
Used AND when modulo should have been used to calculate partition id for PARTITION BY KEY and SUBPARTITION BY KEY
-
- 20 Jul, 2005 1 commit
-
-
tulin@dl145b.mysql.com authored
-
- 18 Jul, 2005 1 commit
-
-
mronstrom@mysql.com authored
-