mariadb

Tree: 3f641968fc

Author	SHA1	Message	Date
Sergey Vojtovich	3f641968fc	BUG#51866 - crash with repair by sort and fulltext keys Repairing MyISAM table with fulltext indexes and low myisam_sort_buffer_size may crash the server. Estimation of number of index entries was done incorrectly, causing further assertion failure or server crash. Docs note: min value for myisam_sort_buffer_size has been changed from 4 to 4096.	16 years ago
MySQL Build Team	cab2b49617	Backport into build-201002030816-5.0.87sp1 > ------------------------------------------------------------ > revno: 2818.1.48 > revision-id: joro@sun.com-20091210092838-zbz9ugqay1tn7rxm > parent: joro@sun.com-20091207143856-ojmmqr0bm1haxvca > committer: Georgi Kodinov <joro@sun.com> > branch nick: B49250-5.0-bugteaam > timestamp: Thu 2009-12-10 11:28:38 +0200 > message: > Bug #49250 : spatial btree index corruption and crash > > SPATIAL and FULLTEXT indexes don't support algorithm > selection. > Disabled by creating a special grammar rule for these > in the parser. > Added some encasulation of duplicate parser code.	16 years ago
Sergey Vojtovich	37934f862e	BUG#50351 - ft_min_word_len=2 Causes query to hang Performing fulltext prefix search (a word with truncation operator) may cause a dead-loop. ft_min_word_len value doesn't matter actually. The problem was introduced along with "smarter index merge" optimization.	16 years ago
Georgi Kodinov	4cfda7fd3b	Bug #49445 : Assertion failed: 0, file .\item_row.cc, line 55 with fulltext search and row op. The search for fulltext indexes is searching for some special predicate layouts. While doing so it's not checking for the number of columns of the expressions it tries to calculate. And since row expressions can't return a single scalar value there was a crash. Fixed by checking if the expressions are scalar (in addition to being constant) before calling Item::val_xxx() methods.	16 years ago
Georgi Kodinov	ee06414b5a	Bug #49250 : spatial btree index corruption and crash SPATIAL and FULLTEXT indexes don't support algorithm selection. Disabled by creating a special grammar rule for these in the parser. Added some encasulation of duplicate parser code.	16 years ago
Georgi Kodinov	49a7e81863	Bug #47930 : MATCH IN BOOLEAN MODE returns too many results inside subquery Re-setting a fulltext index was a no-operation if not all the matches of a search were consumed by reading them. This was preventing a joined table using a fulltext index in a subquery that requires only 1 row of output (e.g. EXISTS) from working correctly because the second execution of the sub-query has the fulltext index cursor in a wrong state and was not finding results. Fixed by making the re-init code _ftb_init_index_search() to re-set open cursors in addition to depleted ones.	16 years ago
Anurag Shekhar	7c670fc3e1	Bug#37740 Server crashes on execute statement with full text search and 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.	17 years ago
Sergey Vojtovich	f3d921c082	BUG#42907 - Multi-term boolean fulltext query containing a 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.	17 years ago
Sergey Vojtovich	659a2183dd	BUG#36737 - having + full text operator crashes mysql 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.	17 years ago
Joerg Bruehe	c13bbbdace	Backport of a 5.0.74 fix into 5.0.72sp1: 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	17 years ago
Sergey Vojtovich	85d4cbae24	BUG#37245 - Full text search problem Certain boolean mode queries with truncation operator did not return matching records and calculate relevancy incorrectly.	17 years ago
Sergey Vojtovich	83f96dcf47	BUG#38842 - Fix for 25951 seems incorrect 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.	17 years ago
svoj@mysql.com/june.mysql.com	cbd3dfbbcb	BUG#11392 - fulltext search bug 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.	18 years ago
svoj@mysql.com/april.(none)	c16c5db7a8	BUG#29464 - load data infile into table with big5 chinese fulltext index hangs 100% cpu Moved a test case for BUG#29464 into fulltext3.test, since it requires big5 character set.	19 years ago
svoj@mysql.com/april.(none)	e11d75e45b	BUG#29445 - match ... against () never returns 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.	19 years ago
serg@janus.mylan	859304f708	fix for smarter index mergein fulltext to work for queries like "+a (b)"	19 years ago
svoj@mysql.com/june.mysql.com	31c8efc812	BUG#29445 - match ... against () never returns 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".	19 years ago
svoj@mysql.com/june.mysql.com	69acbc7759	BUG#29464 - load data infile into table with big5 chinese fulltext index 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.	19 years ago
svoj@mysql.com/april.(none)	005d8c5284	BUG#25951 - ignore/use index does not work with fulltext 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.	19 years ago
msvensson@neptunus.(none)	451a7129bb	Bug#18071 Result from MATCH() uses too many decimals - Use FORMAT as a workaround to only output the first 6 decimals of the value returned from MATCH - This has been done before	20 years ago
serg@serg.mylan	b283fb79d0	MATCH(a,b) AGAINST (... IN NATURAL LANGUAGE MODE) remove explicit $<ulong_num>$ from sql_yacc.yy	20 years ago
svoj@april.(none)	332be5bdd9	BUG#14496: Crash or strange results with prepared statement, MATCH and FULLTEXT Fixed that fulltext query using PS results in unexpected behaviour when executed 2 or more times.	20 years ago
svoj@april.(none)	4426d2ea30	BUG#14194: Problem with fulltext boolean search and apostrophe Fixed that single apostrophe was considered as a word character.	20 years ago
svoj@april.(none)	5581ef960a	BUG#13835: max key length is 1000 bytes when trying to create a fulltext index Allow fulltext index on VARCHAR columns longer than max key length.	20 years ago
serg@serg.mylan	701de9be0a	followup for for the bug#5686	20 years ago
svoj@mysql.com	5d8cefe0b4	Fix for BUG#5686 - #1034 - Incorrect key file for table - only utf8	20 years ago
timour@mysql.com	a247282aa6	Implementation of WL#2486 - "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	21 years ago
svoj@mysql.com	19fe33e16c	BUG#11684 fix. Repair crashes mysql when table has fulltext index.	21 years ago
monty@mysql.com	3c12d0ae54	Added end marker for tests to make future merges easier	21 years ago
jimw@mysql.com	176143413e	Fix hang/crash with Boolean full-text search against an unindexed field for which the query contained more words than we allocated space. (Bug #7858)	21 years ago
serg@serg.mylan	1e09c15a8b	don't close binlog in the destructor - use explictit MYSQL_LOG::cleanup for this	21 years ago
dean@mysql.com	87718094aa	fulltext.test, fulltext.result: Test case for bug#8522, to test for out of bounds memory access in ft_nlq_find_relevance().	21 years ago
svoj@mysql.com	643b602832	Bug#8351 Fix for crash when using a double quote in boolean fulltext query.	21 years ago
serg@serg.mylan	b4624288a7	myisam/ft_boolean_search.c -trunc* bug - don't increase yweaks in this case	21 years ago
serg@serg.mylan	e8203e437a	bug#6784 mi_flush_bulk_insert (on dup key error in mi_write) was mangling info->dupp_key_pos	21 years ago
serg@serg.mylan	dca2182fdc	ft_boolean_search.c: bug#6705 - (+trunc1* +trunc2*) fulltext.test, fulltext.result: bug#6705	21 years ago
serg@serg.mylan	2d8c21f700	test for bug#5528	21 years ago
serg@serg.mylan	d2bfefc3c1	proper max_records estimation for sort-repair of fulltext indexes	21 years ago
wax@kishkin.ru	eb7515366b	WL#964 porting mysql_test_run on Linux and Windows	21 years ago
serg@serg.mylan	78fa465b92	bug#3964 and related issues: FTB problems with charsets where one byte can match many correct prefix compare with my_strnncoll	22 years ago
monty@mysql.com	518019f511	Remove some code from sql_yacc.cc that doesn't do anything except produce warnings on VC++	22 years ago
serg@serg.mylan	1998dd786e	backport bug#2708 fix from 4.1	22 years ago
serg@serg.mylan	2cbc4e71fc	backport from 4.1: "phrase search" should not match partial words (it should not match 'paraphrase searches')	22 years ago
serg@serg.mylan	0ea1dd850d	bug#3011 - multi-byte charset in fulltext	22 years ago
serg@serg.mylan	bcd14123bc	ftb +(+(many -parens)) bug fixed	22 years ago
monty@mysql.com	f43093ec0e	After merge fixes 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)	22 years ago
serg@serg.mylan	15249d6a72	bug#2708 test results updated	22 years ago
serg@serg.mylan	069f6892f7	beautify SHOW INDEX	22 years ago
antony@ltantony.rdg.cyberkinetica.homeunix.net	fcf96dbb18	WorkLog#1323 Deprecate the use of TYPE=... Preferred syntax is ENGINE=	22 years ago
serg@serg.mylan	8ca1836207	yet another trunc* bug	22 years ago

1 2 3

140 Commits (3f641968fc91950bf974a8dbfe0cd6d913cab75a)