Skip to content
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

IStatement::execute() and IAttachment::execute() functions should return on error pointer to old transaction interface [CORE4387] #4709

Closed
firebird-automations opened this issue Apr 8, 2014 · 6 comments

Comments

@firebird-automations
Copy link
Collaborator

Submitted by: @AlexPeshkoff

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.

Commits: 8b28dd1 FirebirdSQL/fbt-repository@50d178a

@firebird-automations
Copy link
Collaborator Author

Modified by: @AlexPeshkoff

assignee: Alexander Peshkov [ alexpeshkoff ]

@firebird-automations
Copy link
Collaborator Author

Commented by: @AlexPeshkoff

An issue was reported to me privately by Dmitry Emanov

@firebird-automations
Copy link
Collaborator Author

Modified by: @AlexPeshkoff

status: Open [ 1 ] => Resolved [ 5 ]

resolution: Fixed [ 1 ]

Fix Version: 3.0 Beta 1 [ 10332 ]

@firebird-automations
Copy link
Collaborator Author

Modified by: @pcisar

status: Resolved [ 5 ] => Closed [ 6 ]

@firebird-automations
Copy link
Collaborator Author

Modified by: @pavel-zotov

status: Closed [ 6 ] => Closed [ 6 ]

QA Status: No test

@firebird-automations
Copy link
Collaborator Author

Modified by: @pavel-zotov

status: Closed [ 6 ] => Closed [ 6 ]

QA Status: No test => Cannot be tested

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment