Hello,

I wonder what you think on that.

When a parametrized query containg a LIKE operator gets prepared, the
optimizer doesn't know the parameter value for the LIKE operand, thus it
won't take an index on that column into account.

Imagine I feed the parameter value with something like 'Firebird%', an
index could be used of course, but not in case of a parametrized query.
Would it be technical possible in Firebird to produce some kind of
re-evaluate an adapted plan once the parameter values are known?

Regards,
Thomas