>>If you didn't need the deleted() tag before you might check that creating it for that particular query doesn't slow down other queries. No really *good* choices here, but still you can try to find the lesser evil.
>
>The result is significant when having it. It is really slow without it so I guess I will have to request the addition of that tag on the production table.

But if the deleted()- index slows down other queries significantly, you could

set dele off
*-- count with a compound index handling deleted and filter condition
set dele on

to keep the speed in the count and have no deleted() index. But if the index on the integer filed is used elsewhere, you could have a proliferation of tags, which is bad in itself. As I said, no really *good* choices <g>.

regards

thomas