- 11 Sep, 2008 3 commits
-
-
Magnus Svensson authored
-
Magnus Svensson authored
-
Magnus Svensson authored
-
- 10 Sep, 2008 2 commits
-
-
Horst Hunger authored
-
Horst Hunger authored
- Updated slow_query_log_file_basic and general_log_file basis instead of the func version as the func version run good but the basic versions fail. - Sent innodb.test to dev@innodb.com. - variables.test has differences probably due to a bug in mtr or in the SET statement (see bug#39369). - general_log_file_basic.test and slow_query_log_file_bsaic.test have differences, which might be produced by the new mtr (see bug#38124).
-
- 09 Sep, 2008 1 commit
-
-
Magnus Svensson authored
-
- 06 Sep, 2008 4 commits
-
-
Magnus Svensson authored
-
Magnus Svensson authored
-
He Zhenxing authored
-
He Zhenxing authored
-
- 05 Sep, 2008 13 commits
-
-
Magnus Svensson authored
-
Magnus Svensson authored
-
Magnus Svensson authored
-
Magnus Svensson authored
-
Magnus Svensson authored
-
Magnus Svensson authored
-
Magnus Svensson authored
- fix scheduler bug
-
Magnus Svensson authored
-
Magnus Svensson authored
-
Magnus Svensson authored
-
Magnus Svensson authored
- Rearrange spawn worker code
-
Magnus Svensson authored
-
Magnus Svensson authored
-
- 04 Sep, 2008 1 commit
-
-
He Zhenxing authored
-
- 29 Aug, 2008 3 commits
-
-
Magnus Svensson authored
-
Magnus Svensson authored
-
Magnus Svensson authored
-
- 28 Aug, 2008 4 commits
-
-
kent@mysql.com authored
-
Georgi Kodinov authored
-
Georgi Kodinov authored
-
Georgi Kodinov authored
-
- 27 Aug, 2008 9 commits
-
-
Gleb Shchepa authored
returns unexpected result If: 1. a table has a not nullable BIT column c1 with a length shorter than 8 bits and some additional not nullable columns c2 etc, and 2. the WHERE clause is like: (c1 = constant) AND c2 ..., the SELECT query returns unexpected result set. The server stores BIT columns in a tricky way to save disk space: if column's bit length is not divisible by 8, the server places reminder bits among the null bits at the start of a record. The rest bytes are stored in the record itself, and Field::ptr points to these rest bytes. However if a bit length of the whole column is less than 8, there are no remaining bytes, and there is nothing to store in the record at its regular place. In this case Field::ptr points to bytes actually occupied by the next column in a record. If both columns (BIT and the next column) are NOT NULL, the Field::eq function incorrectly deduces that this is the same column, so query transformation/equal item elimination code (see build_equal_items_for_cond) may mix these columns and damage conditions containing references to them.
-
Mats Kindahl authored
-
Georgi Kodinov authored
-
Georgi Kodinov authored
When switching to indexed ORDER BY we must be sure to reset the index read flag if we are switching from a covering index to non-covering.
-
Mats Kindahl authored
-
Mats Kindahl authored
-
Evgeny Potemkin authored
used causes server crash. When the loose index scan access method is used values of aggregated functions are precomputed by it. Aggregation of such functions shouldn't be performed in this case and functions should be treated as normal ones. The create_tmp_table function wasn't taking this into account and this led to a crash if a query has MIN/MAX aggregate functions and employs temporary table and loose index scan. Now the JOIN::exec and the create_tmp_table functions treat MIN/MAX aggregate functions as normal ones when the loose index scan is used.
-
Mats Kindahl authored
-
Mats Kindahl authored
-