Bug #17284
closed
no content in workspace preview when using select.selectFields
Added by gregory almost 18 years ago.
Updated over 6 years ago.
Description
Looking for performance, i always restrict fields used in my select clause thanks to selectFields that way :
select.selectFields = header,bodytext // example which only fetch bodytext and header fields
The problem with this method is that my CONTENT won't retrieve any content in case i'm not in LIVE workspace. In my opinion, this is not the intended behaviour, since the selectFields function should take into account workspaces.
(issue imported from #M5575)
Files
- File 17284.patch 17284.patch added
- Category deleted (
Miscellaneous)
- Status changed from Accepted to Under Review
- Target version deleted (
0)
Attached is a patch that fixes this issue.
- Project changed from 624 to TYPO3 Core
Patch set 2 of change Id9d1e7dcf56b5aeeec3070ff11416e82ec1bb978 has been pushed to the review server.
It is available at http://review.typo3.org/2089
Patch set 3 of change Id9d1e7dcf56b5aeeec3070ff11416e82ec1bb978 has been pushed to the review server.
It is available at http://review.typo3.org/2089
Patch set 4 of change Id9d1e7dcf56b5aeeec3070ff11416e82ec1bb978 has been pushed to the review server.
It is available at http://review.typo3.org/2089
Patch set 1 of change I6b2b68ed03163e9e0d7dd281aafea8af67fec224 has been pushed to the review server.
It is available at http://review.typo3.org/4950
- Status changed from Under Review to Resolved
- % Done changed from 0 to 100
- Status changed from Resolved to Under Review
- Status changed from Under Review to Resolved
This solution breaks aggregate functions. Especially, the TypoScript method numRows causes an SQL error:
Mixing of GROUP columns (MIN,MAX,COUNT,...) with no GROUP columns is illegal if there is no GROUP BY clause
... and this is the according ticket
#34152 (stdWrap function numRows() fails in 4.6 due to wrong SELECT clause)
- Status changed from Resolved to Closed
Also available in: Atom
PDF