Project

General

Profile

Actions

Bug #49177

closed

INSERT cache in DB-table 'cache_pagesection' produces the MySQL-Error 'Duplicate Entry'

Added by Juergen Kussmann almost 11 years ago. Updated over 8 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
Caching
Target version:
-
Start date:
2013-06-17
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
4.5
PHP Version:
5.3
Tags:
Complexity:
Is Regression:
No
Sprint Focus:

Description

Hi,
if there are two concurrent PHP-Requests, which try to write the same Cache of DB-table 'cache_pagesection', than the MySQL-Error 'Duplicate Entry' can appear.

My Bugfix fixes to bug.


Files


Related issues 1 (0 open1 closed)

Related to TYPO3 Core - Bug #59907: Pagesection caching fails - 'Duplicate entry for key PRIMARY' in cache_pagesection when t3lib_extMgm::addTypoScriptSetup is usedClosed2014-06-26

Actions
Actions #1

Updated by Markus Klein almost 11 years ago

  • Status changed from New to Accepted
  • Target version set to next-patchlevel

Hi Jürgen,

thanks for your patch.
Would you mind pushing your patch to our review system?

Details can be found here: http://wiki.typo3.org/Contribution_Walkthrough_Tutorials

~Markus

Actions #2

Updated by Alexander Opitz almost 11 years ago

Your patch is ok if an update statement returns 0 rows cause there was nothing to update.
The problem that between select and insert another process can insert the row is left, but isn't easy fixable.

Actions #3

Updated by Mathias Schreiber over 8 years ago

  • Target version deleted (next-patchlevel)
Actions #4

Updated by Benni Mack over 8 years ago

  • Status changed from Accepted to Needs Feedback
  • Is Regression set to No

Can you please check again with 6.2 or 7 LTS or master? The code changed quite a lot and we're using the more flexible caching framework now.

Actions #5

Updated by Juergen Kussmann over 8 years ago

Hi Benni,

please close this bug-report. In our TYPO3 6.2, wo don't use this bugfix anymore and our (big) TYPO3-instance/-project run fine without that bugfix.

Actions #6

Updated by Riccardo De Contardi over 8 years ago

  • Status changed from Needs Feedback to Closed

closed as requested by the reporter

Thank you

Actions

Also available in: Atom PDF