Ingo Schommer 0215fdd262 DOC Clarify sanitisation in searchEngine() under boolean mode
This came up in https://github.com/silverstripe/silverstripe-cms/issues/1452, and wasn't fully addressed.
Either we allow boolean mode and all the constraints this brings around special character usage,
or we filter out those special characters, which makes boolean mode pointless.
You can't just pass arbitrary user input in a power-user function like this.
See https://dev.mysql.com/doc/refman/5.6/en/fulltext-boolean.html

Context: This used to work for some examples like "foo>*" under MyISAM,
presumably because it had a more lenient parser. InnoDB rightfully complains about this now.
2020-04-09 10:32:45 +12:00
2019-11-20 16:26:13 +13:00
2017-04-28 14:59:42 +12:00
2018-06-01 10:14:42 +12:00
2017-10-12 11:53:12 +13:00
2017-12-05 12:14:22 +00:00
2020-02-28 11:48:18 +13:00
2019-02-01 15:56:29 +13:00
2018-02-08 10:32:56 +00:00
2018-03-27 11:49:04 +01:00

SilverStripe Framework

Build Status Latest Stable Version Latest Unstable Version codecov SilverStripe supported module Total Downloads License

PHP framework forming the base for the SilverStripe CMS (https://silverstripe.org). Requires a silverstripe-installer base project. Typically used alongside the cms module.

Installation

See installation on different platforms, and installation from source.

Bugtracker

Bugs are tracked on github.com. Please read our issue reporting guidelines.

Development and Contribution

If you would like to make changes to the SilverStripe core codebase, we have an extensive guide to contributing code.

Attribution

Description
No description provided
Readme 162 MiB
Languages
PHP 99.4%
Scheme 0.5%