- 10 Mar, 2010 1 commit
-
-
Mattias Jonsson authored
(regression) Problem was that partition pruning did not exclude the last partition if the range was beyond it (i.e. not using MAXVALUE) Fix was to not include the last partition if the partitioning function value was not within the partition range.
-
- 08 Mar, 2010 2 commits
-
-
Georgi Kodinov authored
-
Georgi Kodinov authored
Spatial indexes were not checking for out-of-record condition in the handler next command when the previous command didn't found rows. Fixed by making the rtree index to check for end of rows condition before re-using the key from the previous search. Fixed another crash if the tree has changed since the last search. Added a test case for the other error.
-
- 04 Mar, 2010 1 commit
-
-
Georgi Kodinov authored
Spatial indexes were not checking for out-of-record condition in the handler next command when the previous command didn't found rows. Fixed by making the rtree index to check for end of rows condition before re-using the key from the previous search. Fixed another crash if the tree has changed since the last search. Added a test case for the other error.
-
- 05 Mar, 2010 4 commits
-
-
Gleb Shchepa authored
consider clustered primary keys Choosing a shortest index for the covering index scan, the optimizer ignored the fact, that the clustered primary key read involves whole table data. The find_shortest_key function has been modified to take into account that fact that a clustered PK has a longest key of possible covering indices.
-
Tatiana A. Nurnberg authored
-
Tatiana A. Nurnberg authored
-
Ramil Kalimullin authored
for ORDER BY on a TEXT or VARCHAR field" backported to 5.1.
-
- 04 Mar, 2010 3 commits
-
-
Tatiana A. Nurnberg authored
-
Tatiana A. Nurnberg authored
-
Tatiana A. Nurnberg authored
-
- 02 Mar, 2010 6 commits
-
-
Tatiana A. Nurnberg authored
-
Tatiana A. Nurnberg authored
-
Tatiana A. Nurnberg authored
-
Tatiana A. Nurnberg authored
If an outer query is broken, a subquery might not even get set up. EXPLAIN EXTENDED did not expect this and merrily tried to de-ref all of the half-setup info. We now catch this case and print as much as we have, as it doesn't cost us anything (doesn't make regular execution slower). backport from 5.1
-
Tatiana A. Nurnberg authored
-
Georgi Kodinov authored
-
- 01 Mar, 2010 7 commits
-
-
Staale Smedseng authored
This patch fixes some typos and poorly formulated sentences in the output from mysqld --help --verbose. Some of the problems described in the bug report are already handled by the patch for Bug#49447, and are therefore not included in this patch.
-
Andrei Elkin authored
START SLAVE UNTIL MASTER ... specifies only SQL thread to stop. rpl_slave_skip erronously deployed waiting for stop of both threads. Corrected with deploying the correct macro. Notice, earlier a similar bug@47749 was fixed in mysql-trunk.
-
Georgi Kodinov authored
-
Georgi Kodinov authored
-
Georgi Kodinov authored
-
Georgi Kodinov authored
-
Georgi Kodinov authored
-
- 28 Feb, 2010 1 commit
-
-
Ramil Kalimullin authored
for same data when using bit fields Problem: checksum for BIT fields may be computed incorrectly in some cases due to its storage peculiarity. Fix: convert a BIT field to a string then calculate its checksum.
-
- 27 Feb, 2010 3 commits
-
-
Andrei Elkin authored
disabling the test to not run on PB
-
Davi Arnaut authored
-
Davi Arnaut authored
POSIX standard, reinitialization of a pthread_once is a gray area, but it is needed to support subsequent initializations of the client library.
-
- 26 Feb, 2010 12 commits
-
-
Andrei Elkin authored
-
Andrei Elkin authored
-
Staale Smedseng authored
A client doing multiple mysql_library_init() and mysql_library_end() calls over the lifetime of the process may experience lost character set data, potentially even a SIGSEGV. This patch reinstates the reloading of character set data when a mysql_library_init() is done after a mysql_library_end().
-
Sergey Glukhov authored
Item_field::print method does not take into account fields whose values may be null. The fix is to print 'NULL' if field value is null.
-
Georgi Kodinov authored
-
Andrei Elkin authored
-
Georgi Kodinov authored
-
Georgi Kodinov authored
Fixed a syntax error in mysqld_multi.sh
-
Sergey Vojtovich authored
-
Davi Arnaut authored
The problem was that the CSV storage engine does not support NULL fields, yet in some early 5.1 version the log tables (general_log and slow_log) were created with null fields. On top of this, when altering a CSV table column, all fields of the table must be NOT NULL otherwise the alteration fails. The solution is to ensure that during upgrade all columns of the log tables are NOT NULL.
-
Andrei Elkin authored
-
Sergey Glukhov authored
-