Subject | RE: [firebird-support] Aborting isc_dsql_execute calls from another thread (Win32) |
---|---|
Author | Alan McDonald |
Post date | 2006-03-23T20:49:05Z |
>you're making the connection in the main thread of the app and then
> Windows.
>
> The code sequence is:
>
> // Foreground
> m_tr->Prepare( m_stmt, inCmd, m_bindings );
> m_stmt->DescribeOutputBindings( m_bindings );
> m_bindings->PrepareBuffer();
>
> // Background
> m_tr->Execute( m_stmt );
> m_hasNext = m_stmt->Fetch( m_bindings );
>
> // Foreground
> m_hasNext = m_stmt->Fetch( m_bindings );
>
> As I mentioned, we can abort the Fetch loop easily in the UI, but
> aborting the slow preparation of the query is my task. It sounds
> from your comments like it would make sense to move the first three
> calls into the background thread as well?
>
> TIA,
> ________________________________________________________
> Richard Wesley Software Engineer
executing a query in a thread? to this connection?
How are you managing the fact the the client lib is not thread safe and that
separate thread must have there own connection?
Alan