|
If you were logged in you would be able to see more operations.
|
|
|
| QA Status: |
Cannot be tested
|
|
When executing unknown SQL statement one should be ready that this is START TRANSACTION or COMMIT, therefore value returned by I***::execute() function should be assigned to current transaction (that's exactly what ISQL in Alpha2 does). But in case of any error API returns NULL (causing transaction leek in ISQL). To avoid need to analyze IStatus before assigning to current transaction in any user program it's good idea to make API return on error old transaction interface pointer.
|
|
Description
|
When executing unknown SQL statement one should be ready that this is START TRANSACTION or COMMIT, therefore value returned by I***::execute() function should be assigned to current transaction (that's exactly what ISQL in Alpha2 does). But in case of any error API returns NULL (causing transaction leek in ISQL). To avoid need to analyze IStatus before assigning to current transaction in any user program it's good idea to make API return on error old transaction interface pointer. |
Show » |
| There are no subversion log entries for this issue yet.
|
|
Improvement
Closed
Major
IStatement::execute() and IAttachment::execute() functions should return on error pointer to old transaction interface