Actions
Bug #65714
closed
Wrong query cache entry when using "in" constraint with null value
Status:
Closed
Priority:
Must have
Assignee:
-
Category:
Database API (Doctrine DBAL)
Target version:
-
Start date:
2015-03-13
Due date:
% Done:
0%
Estimated time:
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.
Updated by
Actions