An error occurred fetching the project authors.
- 23 Apr, 2009 1 commit
-
-
Sergey Vojtovich authored
single quote fails in 5.1.x Performing fulltext prefix search (a word with truncation operator) may cause a dead-loop. The problem was in smarter index merge algorithm - it was writing record reference to an incorrect memory area.
-
- 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.
-
- 12 Feb, 2008 1 commit
-
-
anozdrin/alik@quad. authored
but not collation. The problem here was that text literals in a view were always dumped with character set introducer. That lead to loosing collation information. The fix is to dump character set introducer only if it was in the original query. That is now possible because there is no problem any more of loss of character set of string literals in views -- after WL#4052 the view is dumped in the original character set.
-
- 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 Jul, 2007 2 commits
-
-
svoj@mysql.com/april.(none) authored
hangs 100% cpu Moved a test case for BUG#29464 into fulltext3.test, since it requires big5 character set.
-
svoj@mysql.com/april.(none) authored
Part 2: Searching fulltext index for a word with boolean mode truncation operator may cause infinite loop. The problem was that "smarter index merge" was used with "trunc-words", which must never happen. Affects 5.1 only.
-
- 11 Jul, 2007 1 commit
-
-
serg@janus.mylan authored
to work for queries like "+a (b)"
-
- 10 Jul, 2007 1 commit
-
-
svoj@mysql.com/june.mysql.com authored
Part 1: Do not perform index search for a plus-word with truncation operator in case there are other plus-words in expression. Specifically this optimization was enforced for expression like "+word1 +word2*", but wasn't enforced for expression like "+word1 word2*".
-
- 05 Jul, 2007 1 commit
-
-
svoj@mysql.com/june.mysql.com authored
hangs 100% cpu Fulltext parser may fall into infinite loop when it gets illegal multibyte sequence (or a sequence that doesn't have mapping to unicode). Affects 5.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.
-
- 30 Oct, 2006 1 commit
-
-
Problem: Too confusing error message when cannot convert between string and column character sets on INSERT and UPDATE. Fix: producing a better error message, instead of "Data too long" in such cases Additional changes: Adding "DROP TABLE IF EXISTS" into several tests to be safe against failures in previous tests.
-
- 28 Jul, 2006 1 commit
-
-
sergefp@mysql.com authored
- Make the range-et-al optimizer produce E(#table records after table condition is applied), - Make the join optimizer use this value, - Add "filtered" column to EXPLAIN EXTENDED to show fraction of records left after table condition is applied - Adjust test results, add comments
-
- 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
-
- 22 Feb, 2006 1 commit
-
-
msvensson@neptunus.(none) authored
-
- 14 Feb, 2006 1 commit
-
-
serg@serg.mylan authored
remove explicit $<ulong_num>$ from sql_yacc.yy
-
- 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.
-
- 26 Jan, 2006 1 commit
-
-
svoj@april.(none) authored
Remove implicit limit for query word number.
-
- 13 Jan, 2006 2 commits
-
-
svoj@april.(none) authored
Fixed that single apostrophe was considered as a word character.
-
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.
-
- 17 Jun, 2005 1 commit
-
-
jimw@mysql.com authored
which the query contained more words than we allocated space. (Bug #7858)
-
- 09 Mar, 2005 2 commits
-
-
serg@serg.mylan authored
-
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
-
- 28 Oct, 2004 1 commit
-
-
bar@mysql.com authored
into the column character set on INSERT/UPDATE.
-
- 15 Sep, 2004 1 commit
-
-
wax@kishkin.ru authored
porting mysql_test_run on Linux and Windows
-
- 20 Jul, 2004 1 commit
-
-
bell@sanja.is.com.ua authored
-
- 23 Jun, 2004 1 commit
-
-
serg@serg.mylan authored
more logical table/index_flags return HA_ERR_WRONG_COMMAND instead of abstract methods where appropriate max_keys and other limits renamed to max_supported_keys/etc max_keys/etc are now wrappers to max_supported_keys/etc ha_index_init/ha_rnd_init/ha_index_end/ha_rnd_end are now wrappers to real {index,rnd}_{init,end} to enforce strict pairing
-