From f339e8e20a8203516e18db3d1b6aad0f49bb8273 Mon Sep 17 00:00:00 2001 From: Tizian Schmidlin <noreply@example.com> Date: Fri, 15 Dec 2017 16:47:11 +0100 Subject: [PATCH] [TASK] Update Breaking-82878-RemovedFieldNoCacheInDatabaseTablePages.rst Add SQL to execute to check if the change affects the system or not. Releases: master Resolves: #83343 Change-Id: I255af9e14d49bae5256ce90a267075b7cc28ce4b Reviewed-on: https://review.typo3.org/55095 Tested-by: TYPO3com <no-reply@typo3.com> Reviewed-by: Christian Kuhn <lolli@schwarzbu.ch> Tested-by: Christian Kuhn <lolli@schwarzbu.ch> --- ...-82878-RemovedFieldNoCacheInDatabaseTablePages.rst | 11 ++++++++--- 1 file changed, 8 insertions(+), 3 deletions(-) diff --git a/typo3/sysext/core/Documentation/Changelog/9.0/Breaking-82878-RemovedFieldNoCacheInDatabaseTablePages.rst b/typo3/sysext/core/Documentation/Changelog/9.0/Breaking-82878-RemovedFieldNoCacheInDatabaseTablePages.rst index f27e96ea1d4b..86a4e69dc78f 100644 --- a/typo3/sysext/core/Documentation/Changelog/9.0/Breaking-82878-RemovedFieldNoCacheInDatabaseTablePages.rst +++ b/typo3/sysext/core/Documentation/Changelog/9.0/Breaking-82878-RemovedFieldNoCacheInDatabaseTablePages.rst @@ -37,7 +37,12 @@ TypoScript through :ts:`config.no_cache = 1` in conjunction with a condition on However, it is better to set a very low cache timeout, or investigate why caching is configured wrongly in an extension or plugin. -Also, use the SQL query to quickly check if your installation is even using this option at all. -If not, it is not necessary to migrate anything. +Also, use the following SQL query to quickly check if your installation is even using this option at all. +If not, it is not necessary to migrate anything: -.. index:: Database, Frontend, NotScanned \ No newline at end of file +.. code-block:: sql + + SELECT uid,title FROM pages WHERE no_cache = 1 + + +.. index:: Database, Frontend, NotScanned -- GitLab