An error occurred fetching the project authors.
- 15 Jul, 2009 1 commit
-
-
Anurag Shekhar authored
match against. Server crashes when executing prepared statement with duplicating MATCH() function calls in SELECT and ORDER BY expressions, e.g.: SELECT MATCH(a) AGAINST('test') FROM t1 ORDER BY MATCH(a) AGAINST('test') This query gets optimized by the server, so the value returned by MATCH() from the SELECT list is reused for ORDER BY purposes. To make this optimization server is comparing items from SELECT and ORDER BY lists. We were getting server crash because comparision function for MATCH() item is not intended to be called at this point of execution. In 5.0 and 5.1 this problem is workarounded by resetting MATCH() item to the state as it was during PREPARE. In 6.0 correct comparision function will be implemented and duplicating MATCH() items from the ORDER BY list will be optimized.
-
- 12 Feb, 2009 1 commit
-
-
Sergey Vojtovich authored
MATCH() function accepts column list as an argument. It was possible to override this requirement with aliased non-column select expression. Which results in server crash. With this fix aliased non-column select expressions are not accepted by MATCH() function, returning an error.
-
- 12 Jan, 2009 1 commit
-
-
Joerg Bruehe authored
BUG#38842 - Fix for 25951 seems incorrect Original changeset: > revision-id: svoj@mysql.com-20081111091051-54pr96nf1z2s30gx > parent: vvaintroub@mysql.com-20081110201804-bi98gcs9avsf58ff > committer: Sergey Vojtovich <svoj@mysql.com> > branch nick: mysql-5.0-bugteam-bug38842 > timestamp: Tue 2008-11-11 13:10:51 +0400
-
- 28 Nov, 2008 1 commit
-
-
Sergey Vojtovich authored
Certain boolean mode queries with truncation operator did not return matching records and calculate relevancy incorrectly.
-
- 11 Nov, 2008 1 commit
-
-
Sergey Vojtovich authored
With fix for bug 25951 index hints are ignored for fulltext searches, as handling of fulltext indexes is different from handling regular indexes. Meaning it is not possible to implement true index hints support for fulltext indexes within the scope of current fulltext architecture. The problem is that prior to fix for bug 25951, some useful index hints still could be given for boolean mode searches. This patch implements special index hints support for fulltext indexes with the following characteristics: - all index hints are still ignored for NLQ mode searches - it cannot work without an index; - for 5.1 and up index hints FOR ORDER BY and FOR GROUP BY are still ignored for fulltext indexes; - boolean mode searches honor USE/FORCE/IGNORE INDEX hints; - as opposed to index hints for regular indexes, index hints for fulltext BOOLEAN mode searches affect the usage of the index for the whole query.
-
- 30 Oct, 2007 1 commit
-
-
svoj@mysql.com/june.mysql.com authored
Fulltext boolean mode phrase search may crash server on platforms where size of pointer is not equal to size of unsigned integer (in other words some 64-bit platforms). The problem was integer overflow. Affects 4.1 only.
-
- 12 Apr, 2007 1 commit
-
-
svoj@mysql.com/april.(none) authored
IGNORE/USE/FORCE INDEX hints were honored when choosing FULLTEXT index. With this fix these hints are ignored. For regular indexes we may perform table scan instead of index lookup when IGNORE INDEX was specified. We cannot do this for FULLTEXT in NLQ mode.
-
- 22 Mar, 2006 1 commit
-
-
msvensson@neptunus.(none) authored
- Use FORMAT as a workaround to only output the first 6 decimals of the value returned from MATCH - This has been done before
-
- 01 Feb, 2006 1 commit
-
-
svoj@april.(none) authored
MATCH and FULLTEXT Fixed that fulltext query using PS results in unexpected behaviour when executed 2 or more times.
-
- 13 Jan, 2006 1 commit
-
-
svoj@april.(none) authored
Allow fulltext index on VARCHAR columns longer than max key length.
-
- 26 Nov, 2005 1 commit
-
-
serg@serg.mylan authored
-
- 12 Nov, 2005 1 commit
-
-
svoj@mysql.com authored
-
- 12 Aug, 2005 1 commit
-
-
timour@mysql.com authored
"Process NATURAL and USING joins according to SQL:2003". * Some of the main problems fixed by the patch: - in "select *" queries the * expanded correctly according to ANSI for arbitrary natural/using joins - natural/using joins are correctly transformed into JOIN ... ON for any number/nesting of the joins. - column references are correctly resolved against natural joins of any nesting and combined with arbitrary other joins. * This patch also contains a fix for name resolution of items inside the ON condition of JOIN ... ON - in this case items must be resolved only against the JOIN operands. To support such 'local' name resolution, the patch introduces a stack of name resolution contexts used at parse time. NOTICE: - This patch is not complete in the sense that - there are 2 test cases that still do not pass - one in join.test, one in select.test. Both are marked with a comment "TODO: WL#2486". - it does not include a new test specific for the task
-
- 02 Aug, 2005 1 commit
-
-
svoj@mysql.com authored
Repair crashes mysql when table has fulltext index.
-
- 28 Jul, 2005 1 commit
-
-
monty@mysql.com authored
-
- 17 Jun, 2005 1 commit
-
-
jimw@mysql.com authored
which the query contained more words than we allocated space. (Bug #7858)
-
- 09 Mar, 2005 1 commit
-
-
serg@serg.mylan authored
-
- 16 Feb, 2005 1 commit
-
-
dean@mysql.com authored
Test case for bug#8522, to test for out of bounds memory access in ft_nlq_find_relevance().
-
- 14 Feb, 2005 1 commit
-
-
svoj@mysql.com authored
Fix for crash when using a double quote in boolean fulltext query.
-
- 18 Jan, 2005 1 commit
-
-
serg@serg.mylan authored
-trunc* bug - don't increase yweaks in this case
-
- 24 Nov, 2004 1 commit
-
-
serg@serg.mylan authored
mi_flush_bulk_insert (on dup key error in mi_write) was mangling info->dupp_key_pos
-
- 22 Nov, 2004 1 commit
-
-
serg@serg.mylan authored
bug#6705 - (+trunc1* +trunc2*) fulltext.test, fulltext.result: bug#6705
-
- 17 Nov, 2004 1 commit
-
-
serg@serg.mylan authored
-
- 29 Oct, 2004 1 commit
-
-
serg@serg.mylan authored
-
- 15 Sep, 2004 1 commit
-
-
wax@kishkin.ru authored
porting mysql_test_run on Linux and Windows
-
- 10 Jun, 2004 1 commit
-
-
serg@serg.mylan authored
correct prefix compare with my_strnncoll
-
- 27 May, 2004 2 commits
-
-
monty@mysql.com authored
-
serg@serg.mylan authored
-
- 10 May, 2004 1 commit
-
-
serg@serg.mylan authored
"phrase search" should not match partial words (it should not match 'paraphrase searches')
-
- 29 Feb, 2004 1 commit
-
-
serg@serg.mylan authored
-
- 21 Feb, 2004 1 commit
-
-
serg@serg.mylan authored
-
- 16 Feb, 2004 1 commit
-
-
monty@mysql.com authored
Added more DBUG statements Ensure that we are comparing end space with BINARY strings Use 'any_db' instead of '' to mean any database. (For HANDLER command) Only strip ' ' when comparing CHAR, not other space-like characters (like \t)
-
- 15 Feb, 2004 1 commit
-
-
serg@serg.mylan authored
test results updated
-
- 04 Feb, 2004 1 commit
-
-
serg@serg.mylan authored
-
- 10 Dec, 2003 1 commit
-
-
Deprecate the use of TYPE=... Preferred syntax is ENGINE=
-
- 20 Nov, 2003 1 commit
-
-
serg@serg.mylan authored
-
- 18 Nov, 2003 2 commits
-
-
monty@mashka.mysql.fi authored
-
serg@serg.mylan authored
-
- 08 Nov, 2003 2 commits
-
-
serg@sergbook.mylan authored
a bug in latin1_german2 FT fixed
-
serg@sergbook.mylan authored
one simple trunc* test
-