-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Request: ability to run select queries on a separate thread #236
Comments
@isurukej Everything should be running in the same queue as long as it's the same connection. Do you have code that reproduces the issue? |
Thanks your reply, But I mean that when 'insert' more 2000 records in 'transactions' block and run 'select' quarry in that time. So 'select' quarry run after finished finished 'insert' quarries. I think because "Threads that open transactions and savepoints will block other threads from executing statements while the transaction is open." in Swift 2. So I run 'insert' quarries in separate Connection. is that OK? |
@isurukej Ah, so it doesn't sound like this is a bug then. You were asking for a feature request to run SELECT statements in a different thread? Let me think about the repercussions of that. |
Thanks. |
Added to Feature Requests. |
'Insert and 'Select' quarries run separate thread in swift - 2 at the same time. Because in swift 2 version "Threads that open transactions and savepoints will block other threads from executing statements while the transaction is open."
The text was updated successfully, but these errors were encountered: