Bug #80046
closed
FE broken with postgres
0%
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) ... ^
Updated by Christian Kuhn about 7 years ago
Morton and me aligned on an (intermediate) solution for v8, guess Morton will push something soon.
Updated by Frank Nägler about 7 years ago
analysing the query shows a mismatch of brackets:
20 opening brackets vs. 22 closing brackets
Updated by Christian Kuhn about 7 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.