Bug #82664: Workspaces: MSSQL cannot GROUP BY aliased column - TYPO3 Core - TYPO3 Forge

Custom queries

Accessibility
Easy tasks
Forge Triage
JavaScript issues
JavaScript Issues (w/o Epics/Stories)
My open issues
No feedback within 90 days
Open Bugs
Open issues of 10
Recently modified
Regressions
Stabilization Issues
Usability or UX

Actions

Copy link

Bug #82664

closed

Workspaces: MSSQL cannot GROUP BY aliased column

Added by Susanne Moog about 7 years ago. Updated about 6 years ago.

Status:

Closed

Priority:

Should have

Assignee:

Susanne Moog

Category:

Workspaces

Target version:

Start date:

2017-10-04

Due date:

% Done:

100%

Estimated time:

TYPO3 Version:

PHP Version:

Tags:

Complexity:

Is Regression:

Sprint Focus:

Related issues 1 (0 open — 1 closed)

Related to TYPO3 Core - Task #82811: Extend WorkspaceServiceTests for fetchPagesWithVersionsInTable

Closed

Susanne Moog

2017-10-19

Actions

Issue # Delay: days Cancel

History
Notes
Property changes
Associated revisions

Actions

Copy link

Updated by Gerrit Code Review about 7 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/54281

Actions

Copy link

Updated by Oliver Hader about 7 years ago

Sidenote: On MSSQL SELECT is processed after GROUP BY - that's the reason alias names cannot be used here.

Actions

Copy link

Updated by Susanne Moog about 7 years ago

To be complete ;)

DBMS evaluate statements in the following order:
FROM
WHERE
GROUP BY
HAVING
SELECT
ORDER BY

DBMS with additional logic may be able to resolve aliases set in SELECT in other parts already, but to be safe we should write statements as though there is no additional logic.

Actions

Copy link

Updated by Gerrit Code Review about 7 years ago

Patch set 1 for branch TYPO3_8-7 of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/54308

Actions

Copy link