Project

General

Profile

Actions
Copy link

Bug #64044

closed

Revert fix for #63275 until concept is worked out and agreed upon

Added by Helmut Hummel over 9 years ago. Updated over 5 years ago.

Status:
Closed
Priority:
Must have
Assignee:
-
Category:
-
Target version:
-
Start date:
2014-12-26
Due date:
% Done:

100%

Estimated time:
TYPO3 Version:
7
PHP Version:
Tags:
Complexity:
Is Regression:
No
Sprint Focus:

Description

It may be a useful feature, but then it must be documented as such.
Even more important, it needs to be evaluated whether the comments given by Sebastian are valid or not: https://forge.typo3.org/issues/7848#note-5
How is the decision here? What is the reasoning on why the comments are not valid?
How does "contains" compare to "in" now? What are the differences and how should these be documented?
I prepare a revert until these things are worked out.

Related issues 2 (0 open — 2 closed)

Related to TYPO3 Core - Feature #7848: Support array / multiple values in $query->containsClosed2010-05-212010-06-04

Actions
Related to TYPO3 Core - Bug #63275: Typo3DbQueryParser generates broken SQL for array in CONTAINS-comparisonClosedStefan Neufeind2014-11-23

Actions
Actions
Copy link

Also available in: Atom PDF