It is a bad choice if he works with largish tables and this is the only criteria in his WHERE clause. If he's working with small tables, have other criteria that are selective or have some reason for response times not being of importance (e.g. nightly batch processing), reducing the application code can be useful.

Though of course, you're absolutely right in that it is not a good choice if performance is important and there are no other selective indexed criteria.

By the way, the workaround I suggested only works when FIELD is never null (but then, Harriv has already confirmed this to be the case),
Set

-----Original Message-----
From: firebird-support@yahoogroups.com [mailto:firebird-support@yahoogroups.com] On Behalf Of Dimitry Sibiryakov
Sent: 10. mars 2009 16:27
To: firebird-support@yahoogroups.com
Subject: Re: [firebird-support] Problem with query parameter

> I'm trying to avoid dynamic dynamic or almost-duplicate query in the
> application code.

Look at your query's plan. You prefer long DB answer time. Bad choice.

SY, SD.