Bug #82501
closed
Introduction package broken using PostgreSQL
0%
Description
After installing the introduction package on a TYPO3 8.7.6 and a PostgreSQL database and opening the first frontend page an exception in thrown due to an SQL error:
An exception occurred while executing 'SELECT * FROM "tt_content" WHERE ("tt_content"."pid" IN (2)) AND (=3) AND (("tt_content"."sys_language_uid" IN (0, -1)) OR (("l18n_parent" = 0) AND ("tt_content"."sys_language_uid" = 0))) AND (("tt_content"."deleted" = 0) AND ("tt_content"."t3ver_state" <= 0) AND ("tt_content"."pid" <> -1) AND ("tt_content"."hidden" = 0) AND ("tt_content"."starttime" <= 1505734620) AND (("tt_content"."endtime" = 0) OR ("tt_content"."endtime" > 1505734620)) AND ((("tt_content"."fe_group" = '') OR ("tt_content"."fe_group" IS NULL) OR ("tt_content"."fe_group" = '0') OR ('0' = ANY(string_to_array("tt_content"."fe_group"::text, ','))) OR ('-1' = ANY(string_to_array("tt_content"."fe_group"::text, ',')))))) ORDER BY "sorting" ASC': SQLSTATE[42601]: Syntax error: 7 FEHLER: Syntaxfehler bei »=« LINE 1: ...t_content" WHERE ("tt_content"."pid" IN (2)) AND (=3) AND ((... ^
Problem is a syntax error in the SQL query of TYPO3\CMS\Frontend\ContentObject\ContentObjectRenderer::exec_getQuery("tt_content", array): SELECT * FROM "tt_content" WHERE ("tt_content"."pid" IN (2)) AND (=3) where a wrong SQL condition AND (=3) is used.
Updated by Christian Kuhn over 6 years ago
weird. we have an acceptance test for exactly that: install system on postgres, load introduction package and verify frontend comes up.
Updated by Tymoteusz Motylewski almost 6 years ago
- Status changed from New to Closed
@Stephan, please reopen the issue if it's still failing for you with newest TYPO3.
Then please provide more info like postgres version, introduction package version and so.
Updated by Stephan Großberndt over 5 years ago
- Status changed from Closed to Needs Feedback
The acceptance tests do not log or care for sql errors. This is a general problem. The acceptance test still finds its buttons because it does not use the view where the error occurs. I will test whether its still an issue, but I bet it is.
Updated by Christian Eßl about 4 years ago
- Related to Epic #90719: PostgreSQL related issues added
Updated by Manuel Selbach about 4 years ago
@Stephan Großberndt Do you have more information about that issue?
I tried it as it's described in the current master and was not able to reproduce the error.
I'm using PostgreSQL 9.6.16, with latest master of TYPO3 and PHP 7.2.19.
Is it still present in version 9.5?
Updated by Riccardo De Contardi over 2 years ago
- Status changed from Needs Feedback to Closed
A lot of time passed with no feedback; I think it's safe to close this issue for now.
If you think that this is the wrong decision, please reopen it or ping me and I'll do it. Otherwise, open a new fresh issue with a reference to this one.
Thank you.