Alexander and both Norman,
thanks for discussing and making things clearer.
After a research some time ago I was aware of the query/thread problem.
But - and excuse when I ask again - my understanding is, that a real
preemptive thread should solve this issue, because time sharing is
dome on an OS kernel level. Or do I still misunderstand the
"PreemptiveThreadTD 2.0 by Taylor Design" message?
Best,
Marcel
On 23.06.2006, at 21:41, Norman Palardy wrote:
On Jun 23, 2006, at 12:57 PM, Marcel wrote:
Sorry, I forgot... RB 2006 r2
OK
I think in that version that it had been modified to yield to other
threads when it could
So, as long as your actual query ran quickly you could put it in a
thread and the UI could remain as responsive as possible
But the issue with long running queries is, as far as I know, not
one that has been changed and may not be able to be changed
Will would have to comment on that
I think it still has the issue that the SQLIte engine does not have
a way to run any other code while a query is running.
It's 100% synchronous and so you wait until the query completes
regardless f threads, etc
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
