Task #53146
closed
Hard-coded MM table name in CategoryCollection
0%
Description
There's a conceptual question about class \TYPO3\CMS\Core\Category\Collection\CategoryCollection (and possible also in \TYPO3\CMS\Frontend\Category\Collection\CategoryCollection, if https://review.typo3.org/23905 gets merged).
Going up the inheritance tree, these classes inherit from \TYPO3\CMS\Core\Collection\AbstractRecordCollection which stores in a static variable ($storageTableName) the name of the table where the collection is defined.
Class \TYPO3\CMS\Core\Category\Collection\CategoryCollection relies on a MM table (sys_category_record_mm) to store relations to items in the category-based selection. This table name is hard-coded in the getCollectedRecords() method. Is that correct? Or should it be a (static?) variable like $storageTableName?
Updated by Philipp Gampe over 10 years ago
- Status changed from New to Needs Feedback
IMHO it should be a TCA setting. Can you ask the same question on the core list?
I would like to gather further feedback on this.
Updated by Alexander Opitz about 10 years ago
Is there feedback? Did this change already?
Updated by Francois Suter about 10 years ago
Not a single answer to the discussion started in the Core list. IMO we might just as well drop the topic. It's not really important. Maybe it's even desirable that the MM table cannot be changed, so we know that all relations are centralised.
Updated by Lorenz Ulrich almost 10 years ago
ATM (personally) I don't see a use-case for changing the MM table name.
Updated by Alexander Opitz over 9 years ago
- Status changed from Needs Feedback to Closed
- Target version deleted (
6.2.0)
Closing this issue for now. We can came up if there is an use-case.