Project

General

Profile

Actions

Bug #92376

closed

Doctrine 2.11.x breaks prepared parameters

Added by Tizian Schmidlin about 4 years ago. Updated almost 4 years ago.

Status:
Closed
Priority:
Should have
Assignee:
Category:
-
Start date:
2020-09-22
Due date:
% Done:

100%

Estimated time:
TYPO3 Version:
9
PHP Version:
Tags:
Complexity:
no-brainer
Is Regression:
Sprint Focus:

Description

Hello there,

we ran into an issue with Doctrine DBAL in the last two days.

Since 2.11 of doctrine/dbal prepared statements lead to issues regarding prepared statements where mysql simply isn't able to apply the parameters for some reason.

Until 2.10.4 it works fine.

Reproducible with powermail and an internal extension, both using Extbase with queries like these:

$query->equals('field.relation.someotherrelation', 'my param')

It all seems to be the same problem:
  1. Generation of empty where statements

For the moment we fixated the version of dbal to 2.10.*, I guess this should be done in the core by default, too.

Reproducible in 10.4 and 9.5


Files

ArgumentCountError.png (186 KB) ArgumentCountError.png Christopher Schnell, 2020-09-23 11:12

Related issues 2 (0 open2 closed)

Related to TYPO3 Core - Bug #92865: 10.4.10 breaks compatibility with doctrine/dbal 2.12Closed2020-11-17

Actions
Has duplicate TYPO3 Core - Bug #92515: Limit DBAL of Core 9 and 10 to 2.10ClosedMarkus Klein2020-10-08

Actions
Actions

Also available in: Atom PDF