🚀 go-pugleaf

I'm writing an application that searches a table in an Access database where
the result set can conceivably be the entire table (which ranges from 30,000
to 250,000 records).  All searches are read-only.

I tried using asynchronous fetching with a client cursor, but the performance
is pretty bad, and memory usage quite high - as one would expect with having
to create a copy of many thousands of records (each of which is about 600
bytes in size).

When I switched to a "server" cursor, the fetches increased in speed by at
least an order of magnitude.

However, for large searches, this could still mean a long wait for users who
have relatively slow processors.

So, I'd like to let the user kill a search that's taking too long.

Opening the query on a separate thread and killing it is easy enough, but
what are the repercussions?

Will there be memory leaks?  

Better yet, is there a more graceful way to terminate a long query that has
to run synchronously (since MS was thoughtful enough to make asynchronous
fetches impossible with a server cursor)?


--
 - Mike

Remove 'spambegone.net' and reverse to send e-mail.