mirror of
https://github.com/silverstripe/silverstripe-cms
synced 2024-10-22 08:05:56 +02:00
e51bd421a6
> InnoDB FULLTEXT indexes have special transaction handling characteristics due its caching and batch processing behavior. Specifically, updates and insertions on a FULLTEXT index are processed at transaction commit time, which means that a FULLTEXT search can only see committed data. The following example demonstrates this behavior. The FULLTEXT search only returns a result after the inserted lines are committed. https://dev.mysql.com/doc/refman/5.6/en/innodb-fulltext-index.html#innodb-fulltext-index-transaction |
||
---|---|---|
_config | ||
.tx | ||
client | ||
code | ||
lang | ||
templates | ||
tests | ||
_config.php | ||
.codecov.yml | ||
.editorconfig | ||
.eslintignore | ||
.eslintrc.js | ||
.gitattributes | ||
.gitignore | ||
.nvmrc | ||
.sass-lint.yml | ||
.travis.yml | ||
.upgrade.yml | ||
behat.yml | ||
composer.json | ||
CONTRIBUTING.md | ||
LICENSE | ||
package.json | ||
phpcs.xml.dist | ||
phpunit.xml.dist | ||
README.md | ||
silverstripe_version | ||
webpack.config.js | ||
yarn.lock |
SilverStripe CMS
PHP Content Management System (CMS), see http://silverstripe.org. Requires the framework
module and a silverstripe-installer
base project.
Installation
See installation instructions.
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.