PySQLQuery class not making sure cursor is closed
Bug #275225 reported by
Nikoleta Verbeck
| Affects | Status | Importance | Assigned to | Milestone | ||
|---|---|---|---|---|---|---|
| PySQLPool | Status tracked in Pre-1.0 | |||||
| Pre-1.0 |
Fix Released
|
High
|
Nikoleta Verbeck | |||
Bug Description
In the try/catch of each query function in PySQLQuery the cursor is not made sure to be closed in case of a sql error.
This bug was originally reported to me by Alessandro
Related branches
Revision history for this message
| Nikoleta Verbeck (nerdynick) wrote | #1 |
Revision history for this message
| Nikoleta Verbeck (nerdynick) wrote | #2 |
| Changed in pysqlpool: | |
| assignee: | nobody → nerdynick |
| importance: | Undecided → High |
| milestone: | none → 0.3 |
| status: | New → Fix Committed |
| Changed in pysqlpool: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
Here is a patch to resolve the issue. This fix has also been committed against the trunk as well.