Bug #58511
closed
addUnionStatement does not respect MM_match_fields
0%
Description
Hello Core-Team,
it seems that we have another part in persistence of extbase where MM_match_fields was not implemented.
I have added a query like that:
$query->equals('categories.uid', $category);
Because of the dot inside parseOperand() calls method addUnionStatement and here we have to add MM_match_fields, too.
Stefan
Updated by Gerrit Code Review over 10 years ago
- Status changed from New to Under Review
Patch set 1 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/29870
Updated by Gerrit Code Review over 10 years ago
Patch set 2 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/29870
Updated by Frans Saris over 10 years ago
Why use the .uid? And not just:
$query->equals('categories', $category);
Updated by Stefan Froemken over 10 years ago
Good Morning Frans,
as you can see in the ticket the union statement will only be added if propertypath contains a dot. Sure, I can change it to categories.title, but the result is the same. My test checks, if mm_match_fields is also considered in case of union statements.
Stefan
Updated by Gerrit Code Review over 10 years ago
Patch set 3 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/29870
Updated by Gerrit Code Review over 10 years ago
Patch set 4 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/29870
Updated by Gerrit Code Review over 10 years ago
Patch set 5 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/29870
Updated by Mathias Schreiber about 9 years ago
- Target version deleted (
next-patchlevel)
Updated by Stefan Froemken about 9 years ago
- Status changed from Under Review to Closed
This issue was solved with: https://forge.typo3.org/issues/27057