An error occurred fetching the project authors.
- 08 Jan, 2008 1 commit
-
-
evgen@moonbone.local authored
server crash. The filesort implementation has an optimization for subquery execution which consists of reusing previously allocated buffers. In particular the call to the read_buffpek_from_file function might be skipped when a big enough buffer for buffer descriptors (buffpeks) is already allocated. Beside allocating memory for buffpeks this function fills allocated buffer with data read from disk. Skipping it might led to using an arbitrary memory as fields' data and finally to a crash. Now the read_buffpek_from_file function is always called. It allocates new buffer only when necessary, but always fill it with correct data.
-
- 22 Oct, 2007 1 commit
-
-
kaa@polly.(none) authored
an error, asserts server In case of a fatal error during filesort in find_all_keys() the error was returned without the necessary handler uninitialization. Fixed by changing the code so that handler uninitialization is performed before returning the error.
-
- 24 Jul, 2007 1 commit
-
-
evgen@moonbone.local authored
When the SQL_BIG_RESULT flag is specified SELECT should store items from the select list in the filesort data and use them when sending to a client. The get_addon_fields function is responsible for creating necessary structures for that. But this function was allowed to do so only for SELECT and INSERT .. SELECT queries. This makes the SQL_BIG_RESULT useless for the CREATE .. SELECT queries. Now the get_addon_fields allows storing select list items in the filesort data for the CREATE .. SELECT queries.
-
- 01 Jul, 2007 1 commit
-
-
igor@olga.mysql.com authored
This bug may manifest itself not only with the queries for which the index-merge access method is chosen. It also may display itself for queries with DISTINCT. The bug was in how the Unique::get method used the merge_buffers function. To compare elements in the the queue employed by merge_buffers() it must use the buffpek_compare function rather than the function for binary comparison.
-
- 08 Jun, 2007 1 commit
-
-
igor@olga.mysql.com authored
ORDER BY and LIMIT 1. The bug was introduced by the patch for bug 21727. The patch erroneously skipped initialization of the array of headers for sorted records for non-first evaluations of the subquery. To fix the problem a new parameter has been added to the function make_char_array that performs the initialization. Now this function is called for any invocation of the filesort procedure. Yet it allocates the buffer for sorted records only if this parameter is NULL.
-
- 18 May, 2007 1 commit
-
-
dkatz@damien-katzs-computer.local authored
Fixed a problem and compiler warning on 64bit platforms so that they only allocated UINT_MAX number of BUFFPEKS.
-
- 17 May, 2007 1 commit
-
-
dkatz@damien-katzs-computer.local authored
Fixed a compiler warning on platforms where uint != ulong from the first pushed fix.
-
- 16 May, 2007 1 commit
-
-
dkatz@damien-katzs-computer.local authored
Added checks to detect integer overflow and fixed other bugs on the error path.
-
- 07 Mar, 2007 1 commit
-
-
gkodinov/kgeorge@macbook.gmz authored
DATE/DATETIME values are out of the currently supported 4 basic value types (INT,STRING,REAL and DECIMAL). So expressions (not fields) of compile type DATE/DATETIME are generally considered as STRING values. This is not so when they are compared : then they are compared as INTEGER values. But the rule for comparison as INTEGERS must be checked explicitly each time when a comparison is to be performed. filesort is one such place. However there the check was not done and hence the expressions (not fields) of type DATE/DATETIME were sorted by their string representation. Fixed to compare them as INTEGER values for filesort.
-
- 22 Feb, 2007 1 commit
-
-
monty@mysql.com/narttu.mysql.fi authored
Fixed a couple of usage of not initialized warnings (unlikely cases)
-
- 26 Jan, 2007 1 commit
-
-
igor@olga.mysql.com authored
The bug report has demonstrated the following two problems. 1. If an ORDER/GROUP BY list includes a constant expression being optimized away and, at the same time, containing single-row subselects that return more that one row, no error is reported. Strictly speaking the standard allows to ignore error in this case. Yet, now a corresponding fatal error is reported in this case. 2. If a query requires sorting by expressions containing single-row subselects that, however, return more than one row, then the execution of the query may cause a server crash. To fix this some code has been added that blocks execution of a subselect item in case of a fatal error in the method Item_subselect::exec.
-
- 31 Dec, 2006 1 commit
-
-
kent@mysql.com/kent-amd64.(none) authored
Corrected spelling in copyright text Makefile.am: Don't update the files from BitKeeper Many files: Removed "MySQL Finland AB & TCX DataKonsult AB" from copyright header Adjusted year(s) in copyright header Many files: Added GPL copyright text Removed files: Docs/Support/colspec-fix.pl Docs/Support/docbook-fixup.pl Docs/Support/docbook-prefix.pl Docs/Support/docbook-split Docs/Support/make-docbook Docs/Support/make-makefile Docs/Support/test-make-manual Docs/Support/test-make-manual-de Docs/Support/xwf
-
- 23 Dec, 2006 1 commit
-
-
kent@mysql.com/kent-amd64.(none) authored
Changed header to GPL version 2 only
-
- 14 Dec, 2006 1 commit
-
-
monty@mysql.com/narttu.mysql.fi authored
- Removed not used variables and functions - Added #ifdef around code that is not used - Renamed variables and functions to avoid conflicts - Removed some not used arguments Fixed some class/struct warnings in ndb Added define IS_LONGDATA() to simplify code in libmysql.c I did run gcov on the changes and added 'purecov' comments on almost all lines that was not just variable name changes
-
- 21 Nov, 2006 1 commit
-
-
sergefp@mysql.com authored
-
- 20 Nov, 2006 1 commit
-
-
monty@mysql.com/nosik.monty.fi authored
(Mostly in DBUG_PRINT() and unused arguments) Fixed bug in query cache when used with traceing (--with-debug) Fixed memory leak in mysqldump Removed warnings from mysqltest scripts (replaced -- with #)
-
- 01 Nov, 2006 1 commit
-
-
igor@rurik.mysql.com authored
This is a performance issue for queries with subqueries evaluation of which requires filesort. Allocation of memory for the sort buffer at each evaluation of a subquery may take a significant amount of time if the buffer is rather big. With the fix we allocate the buffer at the first evaluation of the subquery and reuse it at each subsequent evaluation.
-
- 03 Oct, 2006 1 commit
-
-
jani@ua141d10.elisa.omakaista.fi authored
wrong results in order by in some rare cases.
-
- 20 Sep, 2006 1 commit
-
-
igor@rurik.mysql.com authored
that returns the results of aggregation by GROUP_CONCAT. The crash was due to an overflow happened for the field sortoder->length. The fix prevents this overflow exploiting the fact that the value of sortoder->length cannot be greater than the value of thd->variables.max_sort_length.
-
- 13 Oct, 2005 1 commit
-
-
monty@mysql.com authored
Move handling of suffix_length from strnxfrm_bin() to filesort to ensure proper sorting of all kind of binary objects field::sort_key() now adds length last for varbinary/blob VARBINARY/BLOB is now sorted by filesort so that shorter strings comes before longer ones Fixed issues in test cases from last merge
-
- 12 Sep, 2005 1 commit
-
-
monty@mishka.mysql.com authored
Fix for bug #13025; Server crash in filesort because wrong call to handler::position()
-
- 21 Jun, 2005 1 commit
-
-
evgen@moonbone.local authored
Field with wrong buffer was used to make sort key, which results in producing same sort key for all records.
-
- 07 Apr, 2005 1 commit
-
-
monty@mysql.com authored
Fixed warnings by valgrind for sum_distinct.test Enable buffered-record-reads after filesort for InnoDB tables with short primary key Enabled sort-with-data for MyISAM temporary files
-
- 15 Mar, 2005 1 commit
-
-
ramil@mysql.com authored
-
- 09 Mar, 2005 1 commit
-
-
timour@mysql.com authored
The reported problems were due to two completely unrelated omissions. 1) The file sort procedure didn't correctly create the sort key in make_sortkey when the sortkey was an unsigned integer. 2) The name resolution procedure for column references inside a HAVING clause did not propagate the unsigned_flag of the resolved references. This patch corrects both problems.
-
- 28 Feb, 2005 1 commit
-
-
monty@mysql.com authored
(No really critical errors found, but a few possible wrong results)
-
- 25 Feb, 2005 1 commit
-
-
monty@mysql.com authored
(Found during build process)
-
- 16 Feb, 2005 1 commit
-
-
hf@deer.(none) authored
-
- 15 Feb, 2005 1 commit
-
-
monty@mysql.com authored
Simple optimzations done while reviewing code
-
- 08 Feb, 2005 1 commit
-
-
hf@deer.(none) authored
-
- 26 Jan, 2005 1 commit
-
-
bar@mysql.com authored
my_strnxfrm_utf8 now requires 2 bytes per character in filesort key, instead of 3 bytes per character. Shorter filesort keys make sorting faster.
-
- 18 Jan, 2005 1 commit
-
-
monty@mysql.com authored
-
- 15 Jan, 2005 2 commits
-
-
monty@mysql.com authored
-
monty@mysql.com authored
-
- 13 Jan, 2005 2 commits
-
-
bar@mysql.com authored
-
monty@mysql.com authored
-
- 07 Jan, 2005 1 commit
-
-
mskold@mysql.com authored
-
- 06 Jan, 2005 1 commit
-
-
monty@mysql.com authored
Split TABLE to TABLE and TABLE_SHARE (TABLE_SHARE is still allocated as part of table, will be fixed soon) Created Field::make_field() and made Field_num::make_field() to call this Added 'TABLE_SHARE->db' that points to database name; Changed all usage of table_cache_key as database name to use this instead Changed field->table_name to point to pointer to alias. This allows us to change alias for a table by just updating one pointer. Renamed TABLE_SHARE->real_name to table_name Renamed TABLE->table_name to alias Renamed TABLE_LIST->real_name to table_name
-
- 12 Nov, 2004 1 commit
-
-
bell@sanja.is.com.ua authored
-
- 11 Nov, 2004 1 commit
-
-
konstantin@mysql.com authored
-