An error occurred fetching the project authors.
- 20 Jul, 2006 1 commit
-
-
mikael/pappa@dator5.(none) authored
Problem was with handling NULL values in ranges
-
- 05 Jul, 2006 1 commit
-
-
mikael@dator5.(none) authored
-
- 15 Jun, 2006 1 commit
-
-
- 06 Jun, 2006 1 commit
-
-
- 28 May, 2006 1 commit
-
-
New test cases added
-
- 18 Apr, 2006 1 commit
-
-
- 12 Apr, 2006 1 commit
-
-
BUG#18962: DROP PARTITION fails when partitions dropped for subpartitions with default naming procedure Fixed naming procedures for default partitioning and default subpartitioning
-
- 13 Mar, 2006 1 commit
-
-
rburnett@production.mysql.com authored
Bug # 17894 - Comparison with "less than" operator fails with range partition The problem here was that on queries such as < 3, the range given is NULL < n < 3. The null part works correctly where the null value is stored in rec[0] and the field is marked as being null. However, when the 3 is processed, the 3 is places on rec[0] but the null flag is left uncleared. partition_range.result: Results block for bug #17894 partition_range.test: Test block for bug #17894 partition_list.result: Results block for bug #17173 partition_list.test: Test block for bug #17173 opt_range.cc: call set_notnull to clear any null flag that may have been set
-
- 15 Dec, 2005 1 commit
-
-
holyfoot@deer.(none) authored
-
- 20 Sep, 2005 1 commit
-
-
partitioned tables
-
- 20 Jul, 2005 1 commit
-
-
tulin@dl145b.mysql.com authored
-
- 18 Jul, 2005 1 commit
-
-
mronstrom@mysql.com authored
-