Implicit and explicit castings results in a bad plan - response (2) by TROWKRO

Hi Vlad.
Thank You for Your time and Your answer. I'm well aware that minimizing the use of castings is a good thing :-).
What I'm trying to say, is that the casting itself results in a very bad execution plan bexause the optimizer doesen't calculate the right number of rows.
I should mean that the example:
SEL * FROM Table_1
WHERE CAST(Textfield AS INTEGER) = 1
is an example of a query that might run in many systems around the world. In the former versions of Teradata this query performed very well, but now it doesen't. I'lld like to know if anyone else lives the same experience with this or if this is a local issue in our system.
Regards Troels