Core

Hello Core-Team,

since typo3 4.6.0, i think, there is a new implementation of the backend search, which is find in module page or list on every page in the bottom.

There is a difference between searching for words which can be interpreted as integers or not.

The problem:
For example there is a database-table with a field named zipcode. The zipcode-field is defined as a varchar-field, because a zipcode can start with a 0 like "01234". If the field is of type integer, it is not possible to store "01234".

If I try to search for 01234 it is interpreted as integer and the text-field zipcode is ignored while search.

I think the problem could be find in the implementation of the searchString:
File: typo3/class.db_list.inc Method: makeSearchString().

Unfortunately I'm not able to fix something like this and present a patch. For my project I've modified this method to make no equal-parts on integer-interpreted-strings. Now always a like-part is generated ignoring the type/eval-setting in the TCA. (I think this is the way before typo3 4.6.0 and therefore no improvement.)

Thank you for your attention and ignore my bad english writing ;-)
And thank you for typo3 - I like it much - great work.