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
If stored procedure with execute statement with external database fails at runtime, external database remains attached. [CORE2138] #2569
Comments
Commented by: @hvlad Do you have reproducible test case ? |
Modified by: @hvladassignee: Vlad Khorsun [ hvlad ] |
Commented by: Alexandre Moradell (amoradell) Yes I will post one tomorrow (23 october) |
Commented by: Alexandre Moradell (amoradell) -- But with this one, I get an error (see file attached) and REFERENCEDB stays attached . |
Modified by: Alexandre Moradell (amoradell)Attachment: execute_statement_external_database_bad.png [ 11111 ] |
Commented by: Alexandre Moradell (amoradell) The test case : -- the bad one : compile is ok but variable NOMPrenom is not recognized (see file attached) SET TERM ^ ; GRANT EXECUTE ON PROCEDURE XXXRECUPAUTHOBAD TO SYSDBA; -- the correct one : I declare a local variable and pass the variable GRANT EXECUTE ON PROCEDURE XXXRECUPAUTHO TO SYSDBA; -- With this query, it's ok : I get the results (found a match or null) and when I commit, REFERENCEDB is detached. -- But with this one, I get an error (see file attached) and REFERENCEDB stays attached . -- firebird.log extract |
Commented by: @hvlad The bug was only if AUTONOMOUS transaction used. If statement prepare fails then its AUTONOMOUS transaction was not finished (not rolled back) and correspondingly its attachment was not released. |
Modified by: @hvladstatus: Open [ 1 ] => Resolved [ 5 ] resolution: Fixed [ 1 ] Fix Version: 2.5 Beta 1 [ 10251 ] |
Modified by: @pcisarstatus: Resolved [ 5 ] => Closed [ 6 ] |
Modified by: @pavel-zotovQA Status: No test |
Submitted by: Alexandre Moradell (amoradell)
Attachments:
execute_statement_external_database_bad.png
I tried the new feature Execute Statement with external database.
As I test, alter and run the stored procedure, I got error messages (problem with variables not recognized)
After several tries, I placed the variables correctly and execution was ok, I commit and disconnect from calling database (where the SP was created).
The external database was not opened via any other clients. And I saw that this external database was attached.
I supposed the first errors didn't detach properly the external database.
Commits: 14a9ecf
The text was updated successfully, but these errors were encountered: