summaryrefslogtreecommitdiff
path: root/mysql-test/r/fulltext.result
Commit message (Collapse)AuthorAgeFilesLines
* Create 'main' test directory and move 't' and 'r' thereMichael Widenius2018-03-291-778/+0
|
* Merge bb-10.2-ext into 10.3Marko Mäkelä2018-02-151-0/+20
|\
| * Merge remote-tracking branch 'origin/10.2' into bb-10.2-extAlexander Barkov2018-02-081-0/+20
| |\
| | * Merge branch 'github/10.1' into 10.2Sergei Golubchik2018-02-061-0/+20
| | |\ | |/ /
| | * Merge remote-tracking branch '5.5' into 10.0Vicențiu Ciorbaru2018-01-241-0/+20
| | |\
| | | * MDEV-14743: Server crashes in Item_func_match::init_searchOleksandr Byelkin2018-01-121-0/+20
| | | | | | | | | | | | | | | | | | | | | | | | Remove non prepared (and so belonging to removed clauses FT functions) from the list. in later version it will be fixed by building the list during preparation.
* | | | 0.1: SQL-level System VersioningDaniel Fiala2017-05-051-1/+1
|/ / /
* | | MDEV-7635: Update tests to adapt to the new default sql_modeNirbhay Choubey2017-02-101-0/+1
| | |
* | | Part of MDEV-10134 Add full support for DEFAULTMichael Widenius2016-06-301-1/+1
|/ / | | | | | | | | | | | | Print default values for BLOB's. This is a part commit for automatic changes to make the real commit smaller. All changes here are related to that we now print DEFAULT NULL for blob and text fields, like we do for all other fields.
* | Merge branch '5.5' into 10.0Sergei Golubchik2015-12-131-1/+1
|\ \ | |/
| * Merge branch 'mysql/5.5' into 5.5Sergei Golubchik2015-12-091-1/+1
| |\
| | * Bug #20007383: HANDLE_FATAL_SIGNAL (SIG=11) IN UPDATE_REF_AND_KEYS.Mithun C Y2015-10-121-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Issue: ====== The fulltext predicate is inside a subquery and involves an outer reference; it thus cannot be used for FT index look-up, but MySQL does not see it, which causes a illegal access. Solution: ========= Solution is backported from bug#21140088. Outer reference can not be used as argument of the MATCH function. Added check for outer reference.
| | * post-merge test result updateGeorgi Kodinov2010-12-171-9/+0
| | |
| | * mergeGeorgi Kodinov2010-11-261-0/+45
| | |\
| | | * Bug#54484 explain + prepared statement: crash and Got error -1 from storage ↵Sergey Glukhov2010-10-181-0/+36
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | engine Subquery executes twice, at top level JOIN::optimize and ::execute stages. At first execution create_sort_index() function is called and FT_SELECT object is created and destroyed. HANDLER::ft_handler is cleaned up in the object destructor and at second execution FT_SELECT::get_next() method returns error. The fix is to reinit HANDLER::ft_handler field before re-execution of subquery.
| | * | Manual merge of mysql-5.1-bugteam into mysql-trunk-merge.Alexey Kopytov2010-04-021-0/+13
| | |\ \ | | | |/ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Conflicts: Text conflict in mysql-test/r/func_str.result Text conflict in mysql-test/suite/sys_vars/r/myisam_sort_buffer_size_basic_32.result Text conflict in mysql-test/suite/sys_vars/r/myisam_sort_buffer_size_basic_64.result Text conflict in mysql-test/t/func_str.test Text conflict in sql/mysqld.cc Text conflict in sql/protocol.cc Text conflict in storage/myisam/mi_open.c
| | | * BUG#51866 - crash with repair by sort and fulltext keysSergey Vojtovich2010-03-251-0/+13
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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.
| | * | Manual merge from mysql-trunk-merge.Alexander Nozdrin2010-02-241-0/+20
| | |\ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Conflicts: - client/mysql.cc - client/mysqldump.c - configure.in - mysql-test/r/csv.result - mysql-test/r/func_time.result - mysql-test/r/show_check.result - mysql-test/r/sp-error.result - mysql-test/r/sp.result - mysql-test/r/sp_trans.result - mysql-test/r/type_blob.result - mysql-test/r/type_timestamp.result - mysql-test/r/warnings.result - mysql-test/suite/rpl/r/rpl_sp.result - sql/mysql_priv.h - sql/mysqld.cc - sql/sp.cc - sql/sql_base.cc - sql/sql_table.cc - sql/sql_trigger.cc - sql/sql_view.cc - sql/table.h - sql/share/errmsg.txt - mysql-test/suite/sys_vars/r/log_bin_trust_routine_creators_basic.result
| | | * \ Manual merge of mysql-5.1-bugteam to mysql-trunk-merge.Alexey Kopytov2010-02-221-0/+20
| | | |\ \ | | | | |/
| | | | * Merge fix for bug50351 to mysql-5.1-bugteam.Sergey Vojtovich2010-02-091-0/+20
| | | | |\
| | | | | * BUG#50351 - ft_min_word_len=2 Causes query to hangSergey Vojtovich2010-02-021-0/+20
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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.
| | | * | | Manual merge from mysql-5.1-bugteam.Alexander Nozdrin2010-02-031-0/+8
| | | |\ \ \ | | | | |/ / | | | | | | | | | | | | | | | | | | | | | | | | Conflicts: - configure.in - mysql-test/include/setup_fake_relay_log.inc - sql/sql_select.cc
| | * | | | Patch for WL#3736: Extended Table, Column and Index Comments.Alexander Nozdrin2010-02-201-6/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The task is to (a) add a comment on indexes and (b) increase the maximum length of column, table and the new index comments. The patch committed on behalf of Yoshinori Matsunobu (Yoshinori.Matsunobu@Sun.COM).
| | * | | | Manual merge from mysql-trunk-merge.Alexander Nozdrin2010-02-031-0/+8
| | |\ \ \ \ | | | | |/ / | | | |/| | | | | | | | Conflicts: - sql/sql_select.cc
| | | * | | Bug #49445: Assertion failed: 0, file .\item_row.cc, line 55 withGeorgi Kodinov2010-02-021-0/+8
| | | | |/ | | | |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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.
| | * | | Manual merge from mysql-trunk-merge.Alexander Nozdrin2009-12-161-0/+14
| | |\ \ \ | | | | |/ | | | |/| | | | | | | | | | | | | | | | | | | | | | | | | | Conflicts: - include/my_no_pthread.h - mysql-test/r/sp-ucs2.result - sql/log.cc - sql/sql_acl.cc - sql/sql_yacc.yy
| | | * | Manual merge of mysql-5.1-bugteam into mysql-trunk-merge.Alexey Kopytov2009-12-161-0/+14
| | | |\ \ | | | | |/
| | | | * merge of bug #49250 to 5.1-bugteamGeorgi Kodinov2009-12-111-0/+14
| | | | |\
| | | | | * Bug #49250 : spatial btree index corruption and crashGeorgi Kodinov2009-12-101-0/+14
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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.
| | * | | | Manual merge from mysql-trunk-merge.Alexander Nozdrin2009-12-121-0/+39
| | |\ \ \ \ | | | |/ / / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Conflicts: - extra/comp_err.c - mysql-test/collections/default.experimental - mysql-test/r/archive.result - mysql-test/r/select.result - mysql-test/suite/binlog/r/binlog_unsafe.result - mysql-test/suite/binlog/t/binlog_unsafe.test - mysql-test/suite/rpl/t/disabled.def - mysql-test/t/archive.test - mysql-test/t/select.test - sql/item.cc - sql/item.h - sql/item_timefunc.cc - sql/sql_base.cc - sql/sql_delete.cc - sql/sql_load.cc - sql/sql_partition.cc - sql/sql_table.cc - storage/innobase/handler/ha_innodb.cc - vio/vio.c
| | | * | | Manual merge from mysql-trunk.Alexander Nozdrin2009-12-111-0/+8
| | | |\ \ \ | | | | |/ / | | | |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Conflicts: - client/mysqltest.cc - mysql-test/collections/default.experimental - mysql-test/suite/rpl/t/disabled.def - sql/mysqld.cc - sql/opt_range.cc - sql/sp.cc - sql/sql_acl.cc - sql/sql_partition.cc - sql/sql_table.cc
| | | * | | Bug #47930: MATCH IN BOOLEAN MODE returns too many resultsGeorgi Kodinov2009-10-271-0/+39
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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.
| | * | | | Bug#9801 Views: imperfect error messageMarc Alff2009-11-021-1/+1
| | | |/ / | | |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Backport for 5.5 The root cause of this bug is that the grammar for GROUP BY clauses, when using WITH CUBE or WITH ROLLUP, cause conflicts with the grammar for VIEW, when using WITH CHECK OPTION. The solution is to implement two token look ahead when parsing a WITH token, to disambiguate the non standard WITH CUBE and WITH ROLLUP syntaxes. Patch based on code from Marc Alff and Antony Curtis
| | * | | Bug#34374 mysql generates incorrect warningSergei Golubchik2009-10-191-0/+8
| | |/ / | | | | | | | | | | | | backport to next-mr
| | * | merging with 5.0 bugteam treeAnurag Shekhar2009-07-151-0/+8
| | |\ \ | | | |/
| | | * Bug#37740 Server crashes on execute statement with full text search and Anurag Shekhar2009-07-151-0/+8
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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.
| | * | BUG#42907 - Multi-term boolean fulltext query containing aSergey Vojtovich2009-04-231-0/+8
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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.
| | * | Merge 5.0-bugteam -> 5.1-bugteam.Sergey Vojtovich2009-02-121-0/+4
| | |\ \ | | | |/
| | | * BUG#36737 - having + full text operator crashes mysqlSergey Vojtovich2009-02-121-0/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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.
| | * | Merge.Sergey Vojtovich2008-12-091-0/+9
| | |\ \ | | | |/
| | | * BUG#37245 - Full text search problemSergey Vojtovich2008-11-281-0/+9
| | | | | | | | | | | | | | | | | | | | Certain boolean mode queries with truncation operator did not return matching records and calculate relevancy incorrectly.
| | * | Merge.Sergey Vojtovich2008-11-181-0/+28
| | |\ \ | | | |/
| | | * BUG#38842 - Fix for 25951 seems incorrectSergey Vojtovich2008-11-111-0/+28
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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.
| | * | Fix for Bug#32538: View definition picks up character set,anozdrin/alik@quad.2008-02-121-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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.
| | * | Merge mysql.com:/home/svoj/devel/mysql/BUG11392/mysql-5.0-enginessvoj@june.mysql.com2007-11-021-0/+6
| | |\ \ | | | |/ | | | | | | | | into mysql.com:/home/svoj/devel/mysql/BUG11392/mysql-5.1-engines
| | | * Merge mysql.com:/home/svoj/devel/mysql/BUG11392/mysql-4.1-enginessvoj@june.mysql.com2007-11-021-0/+6
| | | |\ | | | | | | | | | | | | | | | into mysql.com:/home/svoj/devel/mysql/BUG11392/mysql-5.0-engines
| | | | * BUG#11392 - fulltext search bugsvoj@mysql.com/june.mysql.com2007-10-301-0/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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.
| | * | | BUG#29464 - load data infile into table with big5 chinese fulltext indexsvoj@mysql.com/april.(none)2007-07-131-4/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | hangs 100% cpu Moved a test case for BUG#29464 into fulltext3.test, since it requires big5 character set.
| | * | | BUG#29445 - match ... against () never returnssvoj@mysql.com/april.(none)2007-07-131-1/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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.
| | * | | fix for smarter index mergein fulltextserg@janus.mylan2007-07-111-0/+3
| | | | | | | | | | | | | | | | | | | | to work for queries like "+a (b)"
View Lorry Controller Status