Project

General

Profile

Actions
Copy link

Bug #33700

closed

Invalid behavior of search for integer in Backend search

Added by Xavier Perseguers about 12 years ago. Updated over 5 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
Miscellaneous
Target version:
-
Start date:
2012-02-06
Due date:
% Done:

100%

Estimated time:
TYPO3 Version:
4.6
PHP Version:
5.3
Tags:
Complexity:
medium
Is Regression:
Sprint Focus:

Description

Backend search (and Live search once #31761 has been merged) do not behave as stated in the 4.6 Release notes (http://wiki.typo3.org/TYPO3_4.6#Live_Search):

In previous TYPO3 versions, there were several problems with Backend search:

  • ...
  • it searched "uid" and other numeric fields even if the value was not numeric
  • it used LIKE x search on numeric fields
  • ...

In fact current implementation does not replace the LIKE operator with an SQL equal statement for numeric fields but whenever a query that can be interpreted as integer is encountered, regardless of the underlying column type.

Example: If you have pages "102 W", "102 E", you used to be able to search for "102" and get them, but now the query is casted to an integer and the page title is search for an equality on "102" resulting in an empty result list.

The underlying column type should be used instead (code to cache this information is already available within DBAL and Helmut started months ago to backport it to Core itself: #28654).

Files

issue33700.diff (1.35 KB) issue33700.diff Francois Suter, 2012-02-09 15:15

Related issues 3 (0 open — 3 closed)

Related to TYPO3 Core - Bug #31761: Live search does not implement search propertiesClosedFrancois Suter2011-11-11

Actions
Related to TYPO3 Core - Task #28654: Move field info caching to coreRejected2011-08-01

Actions
Has duplicate TYPO3 Core - Bug #42177: Backend-Search: Using search-words which can be interpreted as integer.Closed2012-10-19

Actions
Actions
Copy link

Also available in: Atom PDF