You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 16, 2018. It is now read-only.
I've upgraded to 1.12.7 and a lot of our sites are breaking locally. It seems the fix for some security issue is not backward compatiple with certain ORDER statements.
I have a search table with fulltext search and try to order by a result.
// Using MySQL database.$sBoolQuery = 'database search';
$oSelect ->from(array('s' => 'search_index'))
->where('MATCH (s.titel, s.content) AGAINST (? IN BOOLEAN MODE)', $sBoolQuery)
->order('(1.5 * (MATCH (s.titel) AGAINST (' . $oDb->quote($sQuery) . ')) + MATCH (s.titel, s.content) AGAINST (' . $oDb->quote($sQuery) . ')) DESC')
->limit('100');
This is no longer working. The resulting query is now:
SELECT`s`.*FROM`search_index`AS`s`WHERE (MATCH (s.titel, s.content) AGAINST ('+database search'INBOOLEAN MODE))
ORDER BY`(1`.`5 * (MATCH (s`.`titel) AGAINST ('database search')) + MATCH (s`.`titel, s`.`content) AGAINST ('database search'))`DESCLIMIT100
For convenience the table create SQL
CREATETABLE `search_index` (
`id`INT(10) UNSIGNED NOT NULL,
`module`VARCHAR(255) NOT NULL,
`titel`VARCHAR(255) NOT NULL,
`content`TEXTNOT NULL,
`lang`VARCHAR(50) NULL DEFAULT NULL,
INDEX `lang` (`lang`),
FULLTEXT INDEX `titel` (`titel`),
FULLTEXT INDEX `titel_content` (`titel`, `content`)
)
COLLATE='utf8_general_ci'
ENGINE=MyISAM;
I feel like this is not an expected difference.
The text was updated successfully, but these errors were encountered:
Hi,
I've upgraded to 1.12.7 and a lot of our sites are breaking locally. It seems the fix for some security issue is not backward compatiple with certain ORDER statements.
I have a search table with fulltext search and try to order by a result.
This is no longer working. The resulting query is now:
For convenience the table create SQL
I feel like this is not an expected difference.
The text was updated successfully, but these errors were encountered: