Mikael Ronstrom
8ac7705722
Removed column_list and fixed all issues relating to this change
2009-10-21 12:40:21 +02:00
Mikael Ronstrom
f42cc4a67f
Merged in latest wl3352 tree, fixed some non-partition build issues
2009-10-19 13:06:21 +02:00
Mikael Ronstrom
8cf025ec3f
Fix for non-partition builds
2009-10-19 09:10:25 +02:00
Mikael Ronstrom
1f38322dc4
Merged in latest changes
2009-10-16 17:44:49 +02:00
Mikael Ronstrom
d52305530c
Removed GLOBAL INDEX syntax, need to develop GLOBAL indexes before adding syntax for it
2009-10-16 17:41:15 +02:00
Mikael Ronstrom
05d7593fe3
Fixed review comments
2009-10-16 17:08:34 +02:00
Mikael Ronstrom
1ef62bf621
Fixed removal of column_list keyword for VALUES part, retained for PARTITION BY RANGE/LIST COLUMN_LIST, not entirely working yet
2009-10-16 16:16:06 +02:00
Mikael Ronstrom
b216aab1c4
BUG#47837, Duplicate field names were allowed in both column list partitioning and key partitioning, added check to give error in this case
2009-10-06 17:01:59 +02:00
Mikael Ronstrom
8ca9f1e987
BUG#47838, NULL values in ranges was dropped due to missing else part in store_tuple_to_record, added more tests
2009-10-06 16:22:54 +02:00
Mikael Ronstrom
19ef2eff9c
BUG#47838, NULL values in ranges was dropped due to missing else part in store_tuple_to_record
2009-10-06 16:22:15 +02:00
Mikael Ronstrom
bd80727833
BUG#47776, Fixed character set handling, used wrong length, eventually also found that didn't need to convert to my_strnxfrm-format for column list partitioned tables, also column list partitioned tables can use multi-byte character sets in partition fields as well as where strxfrm multiplies the number of bytes in the string
2009-10-05 16:10:18 +02:00
Mikael Ronstrom
08b57e5387
BUG#47754, used number of parts instead of number of list values as end part for list partitioning in column list partitioning
2009-10-02 11:31:05 +02:00
Mikael Ronstrom
c9865cdb90
Fixed no_ to num_ change for NDB handler
2009-10-01 17:15:50 +02:00
Mikael Ronstrom
226171ab11
Added more test cases
2009-10-01 16:50:11 +02:00
Mikael Ronstrom
f9b0e5db3f
BUG#47752, missed to sort values in list partitioning
2009-10-01 15:09:20 +02:00
Mikael Ronstrom
1fe164a20e
Changed all no_ to num_ to avoid strange names like no_list_values which is not expected to be number of list values, rather a boolea indicating no list values
2009-10-01 15:04:42 +02:00
Mikael Ronstrom
b34643b8d2
Forgot to add result files for WL#3352 new test cases
2009-09-15 17:27:10 +02:00
Mikael Ronstrom
12627d4072
WL#3352, Introducing Column list partitioning, makes it possible to partition on most data types, makes it possible to prune on multi-field partitioning
2009-09-15 17:07:52 +02:00
Joerg Bruehe
51c27a6942
Merge 5.1 up into 5.4-build ("trunk").
2009-08-29 21:26:00 +02:00
Alexander Nozdrin
6fbb712fed
Merge from mysql-trunk.
2009-08-27 16:46:34 +04:00
Alexander Nozdrin
12a4514274
Merge from mysql-trunk-build.
2009-08-27 14:27:30 +04:00
Joerg Bruehe
7810f50aa4
Automerge "trunk" (5.4.2 cloning + version number increase to 5.4.3)
...
into "trunk-build".
2009-08-27 10:44:50 +02:00
Alexander Nozdrin
b1252bdf96
Fix default.conf
2009-08-26 19:44:27 +04:00
Alexander Nozdrin
37072db77b
Merge from mysql-5.1-bugteam
2009-08-26 19:43:32 +04:00
joerg.bruehe@sun.com
a8037cbf9d
Raise version number after cloning 5.4.2-beta
2009-08-26 11:59:49 +02:00
Guilhem Bichot
0e8f2efa6e
fix for Bug#46897 'Test "index_merge_innodb" fails (mostly)':
...
that was already analyzed by Oracle: EXPLAIN can return 3 or 4 in "rows"; using replace_column to work around this.
2009-08-25 17:53:43 +02:00
Guilhem Bichot
27d142386c
Applying fix from Oracle (Marko) for Bug #46657 "InnoDB plugin: invalid read in index_merge_innodb test (Valgrind)"
2009-08-25 17:12:44 +02:00
Joerg Bruehe
4a9cc7ea87
Automerge "trunk" -> "trunk-build".
2009-08-24 22:25:26 +02:00
Davi Arnaut
31afccc407
Bug#45261: Crash, stored procedure + decimal
...
The problem was that creating a DECIMAL column from a decimal
value could lead to a failed assertion as decimal values can
have a higher precision than those attached to a table. The
assert could be triggered by creating a table from a decimal
with a large (> 30) scale. Also, there was a problem in
calculating the number of digits in the integral and fractional
parts if both exceeded the maximum number of digits permitted
by the new decimal type.
The solution is to ensure that truncation procedure is executed
when deducing a DECIMAL column from a decimal value of higher
precision. If the integer part is equal to or bigger than the
maximum precision for the DECIMAL type (65), the integer part
is truncated to fit and the fractional becomes zero. Otherwise,
the fractional part is truncated to fit into the space left
after the integer part is copied.
This patch borrows code and ideas from Martin Hansson's patch.
2009-08-24 16:47:08 -03:00
Alfranio Correia
793e523b4e
auto-merge mysql-5.1-bugteam (local) --> mysql-5.1-bugteam
2009-08-24 11:37:44 +01:00
Alfranio Correia
bb14ffb452
auto-merge mysql-5.1-bugteam (local) --> mysql-5.1-bugteam
2009-08-24 10:24:52 +01:00
Jonathan Perkin
c4fa4f31ae
Apply changes from mysql-5.1.38-release clone:
...
- Add conditionals for bundled zlib and innodb plugin.
- Apply patch from bug#46834 to install the test suite in RPMs.
- Add plugins to RPMs. Disable example plugins.
2009-08-24 10:13:34 +01:00
Alexander Nozdrin
6c83ca3a98
Backporting patch for Bug#46650 (Innodb assertion autoinc_lock == lock
...
in lock_table_remove_low on INSERT SELECT) to mysql-trunk.
2009-08-24 10:48:57 +04:00
Mattias Jonsson
001007caac
merge
2009-08-21 18:00:38 +02:00
Mattias Jonsson
586ee5d616
Bug#46639: 1030 (HY000): Got error 124 from storage engine on
...
INSERT ... SELECT ...
Problem was that when bulk insert is used on an empty
table/partition, it disables the indexes for better
performance, but in this specific case it also tries
to read from that partition using an index, which is
not possible since it has been disabled.
Solution was to allow index reads on disabled indexes
if there are no records.
Also reverted the patch for bug#38005, since that was a workaround
in the partitioning engine instead of a fix in myisam.
2009-08-21 17:38:29 +02:00
Georgi Kodinov
d5bda7c313
reverted the fix for bug #46019 from 5.1-bugteam
2009-08-21 17:41:48 +03:00
Georgi Kodinov
9a856bd483
automerge
2009-08-21 17:12:03 +03:00
Georgi Kodinov
37cff7c047
Revert of the fix for bug #46019 .
2009-08-21 17:10:55 +03:00
Martin Hansson
2749874edb
Merge.
2009-08-21 14:31:40 +02:00
Martin Hansson
a1589a1061
Merge.
2009-08-21 12:13:03 +02:00
Joerg Bruehe
7ae2baea09
Upmerge a merge changeset from 5.0 to 5.1, no code change involved.
2009-08-21 11:56:44 +02:00
Ramil Kalimullin
f59400f4c3
Fix for bug #46456 [Ver->Prg]: HANDLER OPEN + TRUNCATE + DROP
...
(temporary) TABLE, crash
Problem: if one has an open "HANDLER t1", further "TRUNCATE t1"
doesn't close the handler and leaves handler table hash in an
inconsistent state, that may lead to a server crash.
Fix: TRUNCATE should implicitly close all open handlers.
Doc. request: the fact should be described in the manual accordingly.
2009-08-21 10:55:35 +05:00
Joerg Bruehe
56d903a9a3
Merge the correction for the bug#37098 fix into 5.0-build
2009-08-20 22:07:40 +02:00
Joerg Bruehe
6a02c3bce2
automerge the correction for bug#37098 into 5.1-build
2009-08-20 21:58:27 +02:00
Joerg Bruehe
b2e31f6d01
Merge the correction to the bug#37098 fix from 5.1 to 5.4.
2009-08-20 21:50:12 +02:00
Joerg Bruehe
d2d5cdc45e
Merge the correction to the bug#37098 fix from 5.0 to 5.1.
2009-08-20 21:41:12 +02:00
Joerg Bruehe
55f7c2f35f
Get rid of manual pages which aren't used.
...
This is a partial correction to the original fix for bug#37098
Get rid of "Installed (but unpackaged)" files in the RPM build
which used a wrong variable.
2009-08-20 21:08:09 +02:00
Georgi Kodinov
f4676ae522
merge of bug #46019 to 5.1-bugteam
2009-08-20 17:11:22 +03:00
Martin Hansson
85609034cb
Bug#46616: Merge
2009-08-20 14:30:59 +02:00
Martin Hansson
ea6dc4145c
Bug#46616: Assertion `!table->auto_increment_field_not_null' on
...
view manipulations
The bespoke flag was not properly reset after last call to
fill_record. Fixed by resetting in caller mysql_update.
2009-08-20 13:56:29 +02:00
