From: "Svein Erling Tysvær" <svein.erling.tysvaer@...>

> Occasionally, there is a third, obvious option: Simplify the query. I'm
> still on Fb 1.5 myself, but assume that a few of the queries I've written
> throughout the years could benefit from 'SELECT FROM (SELECT...' (Fb 2.0,
> I think) and particularly 'WITH [RECURSIVE]...' (Fb 2.1). Though, of
> course, there will still be lots of optimized queries that run slow, and
> that one either have to live with being slow, redesign the database (that
> can in some cases be a fourth option) or use one of the options Geoff
> suggests.
>
> As for your 'thread moving' thing, if it is a complex where clause that
> makes the query slow, you could have the time consuming query in one
> thread and then (after it finishes) just look up the primary keys (or
> whatever the time consuming query returns that could be used in a where
> clause) it returned in a separate query in your main thread (note that I
> know too little about threads and may overlook complexity).
>

Can't you put the animation in a separate thread instead of the query? That
way the animation should still get it's own time slot to do it's thing while
the query chugs away doing it's thing. I've used that technique before and
it seems to work for most situations.

Woody (TMW)