search

WanderInCode / pyodbc

Automatically exported from code.google.com/p/pyodbc
MIT No Attribution
0 stars 0 forks source link

Connection is busy with results for another hstmt (0) #317

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1.Open 2 cursors at the same time and process the result of the 2 cursors one 
by one
2.
3.

What is the expected output? What do you see instead?
Each cursor should have its own thread and execute without any problem

What version of the product are you using? On what operating system?
Windows 7 Enterpise

Please provide any additional information below.

Original issue reported on code.google.com by prem1pre on 4 Apr 2013 at 7:17

GoogleCodeExporter commented 8 years ago 
Each cursor does not get its own thread.  Thread management is up to the 
programmer.

You will need to determine if your database driver supports multiple cursors 
per connection - SQL Server does, I'm not sure about PostgreSQL (they don't 
have cursors separate from cnxns really).

Original comment by mich...@kleehammer.com on 14 Jul 2013 at 4:06