Actions
Bug #26077
closed
Fallback to DELETE if TRUNCATE not allowed
Status:
Closed
Priority:
Should have
Assignee:
Category:
Database API (Doctrine DBAL)
Target version:
Start date:
2011-04-18
Due date:
% Done:
0%
Estimated time:
TYPO3 Version:
4.4
PHP Version:
5.3
Tags:
Complexity:
medium
Is Regression:
No
Sprint Focus:
Description
We have an installation within a very restrictive security environment where the db-guys disabled truncate rights on the db. Now the clear-cache commands don't work. I suggest a fallback when TRUNCATE is not allowed and switch to DELETE...
Related Issue: http://forge.typo3.org/issues/17189
Updated by Oliver Hader over 13 years ago
- Target version changed from 1061 to 1264
Updated by Christian Kuhn over 13 years ago
- Category changed from Caching to Database API (Doctrine DBAL)
This should be changed in t3lib_db then, taking care of a truncate alternative is not domain of the caching classes.
Updated by Oliver Hader over 13 years ago
- Target version changed from 1264 to 1341
Updated by
Updated by Mathias Schreiber almost 10 years ago
- Target version set to 7.4 (Backend)
- Is Regression set to No
Updated by Morton Jonuschat over 9 years ago
- Status changed from New to Closed
- Assignee set to Morton Jonuschat
Checking the current privileges on every call to TRUNCATE to determine if a fallback to DELETE is needed will not be implemented to solve a very specific edge case.
The required MySQL privileges for the database/user documented in the INSTALL file, TRUNCATE (DROP privilege) is a hard requirement.
Actions