Bug #69660
closed
Epic #64459: Make TYPO3 run on PostgreSQL
Invalid SQL query originating in BackendUtility::readPageAccess(1, 31)
100%
Description
BackendUtility::readPageAccess(1, 31) results in the following SELECT call:
DatabaseConnection::exec_SELECTquery("*", "pages", "uid=1 AND pages.deleted=0 AND 31", "", "", "1")
The error happens somewhere between in the readPageAccess, the following call is possibly wrong:
BackendUtility::getRecord("pages", 1, "*", " AND 31")
Database: PostgreSQL 9.4.4
TYPO3 7.5-dev
Updated by Morton Jonuschat about 9 years ago
- Status changed from New to In Progress
The actual origin of the wrong query seems to be further up the call chain...
Updated by Gerrit Code Review about 9 years ago
- Status changed from In Progress 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 http://review.typo3.org/43186
Updated by Gerrit Code Review about 9 years ago
Patch set 2 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/43186
Updated by Morton Jonuschat about 9 years ago
- Status changed from Under Review to Resolved
- % Done changed from 0 to 100
Applied in changeset 15b328f7e357db4681a32ed7e981afdbe3ec7d9b.
Updated by