Bug #80046

FE broken with postgres

Added by Christian Kuhn over 2 years ago. Updated over 2 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
-
Target version:
Start date:
2017-02-27
Due date:
% Done:

0%

TYPO3 Version:
8
PHP Version:
Tags:
Complexity:
Is Regression:
No
Sprint Focus:
Stabilization Sprint

Description

Looks as if colPos is not encapsulated in " properly.

An exception occurred while executing 'SELECT * FROM "tt_content" WHERE ("tt_content"."pid" IN (1)) AND (colPos=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" <= 1488218520) AND (("tt_content"."endtime" = 0) OR ("tt_content"."endtime" > 1488218520)) AND ((("tt_content"."fe_group" = '') OR ("tt_content"."fe_group" IS NULL) OR ("tt_content"."fe_group" = '0') OR ('0' = ANY)) OR ('-1' = ANY))))) ORDER BY "sorting" ASC': SQLSTATE42703: Undefined column: 7 ERROR: column "colpos" does not exist LINE 1: ...t_content" WHERE ("tt_content"."pid" IN (1)) AND (colPos=0) ... ^


Related issues

Duplicates TYPO3 Core - Task #80506: Enable proper quoting of database fields in Typoscript Closed 2017-03-28

History

#1 Updated by Christian Kuhn over 2 years ago

Morton and me aligned on an (intermediate) solution for v8, guess Morton will push something soon.

#2 Updated by Frank Naegler over 2 years ago

analysing the query shows a mismatch of brackets:

20 opening brackets vs. 22 closing brackets

#3 Updated by Christian Kuhn over 2 years ago

yes. on postgres, colPos is not correctly quoted. this comes from TS and happens with other dbms, too. that's a general issues with where parts from TS and we'll have an intermediate solution in v8 (hopefully before .0 release), and more generic works on that for v9.

#4 Updated by Christian Kuhn over 2 years ago

  • Status changed from New to Closed

Also available in: Atom PDF