Bug #65714

Wrong query cache entry when using "in" constraint with null value

Added by Markus Opahle over 4 years ago. Updated about 3 years ago.

Status:
Closed
Priority:
Must have
Assignee:
-
Category:
Database API (Doctrine DBAL)
Target version:
-
Start date:
2015-03-13
Due date:
% Done:

0%

TYPO3 Version:
6.2
PHP Version:
Tags:
Complexity:
Is Regression:
No
Sprint Focus:

Description

When building a query like this:

$query->matching($query->in('mypropery', array(1,2)));

the querybuilder caches something like "... myproperty IN ..."

When building a query like this:

$query->matching($query->in('mypropery', null));

the querybuilder caches something like "... 1<>1 ..." under the same identifier as above.

This leeds to errors / empty results when the value of the constraint changes from null value to non null values or vice versa.


Related issues

Related to TYPO3 Core - Task #77460: Drop extbase query cache Closed 2016-08-09

History

#1 Updated by Morton Jonuschat about 3 years ago

  • Status changed from New to Closed

Extbase QueryCache has been removed in TYPO3 8.3, implicitly fixing this bug.

Also available in: Atom PDF