Allow the use of management statements in PSQL blocks [CORE5887] #6145
Comments
Modified by: @asfernandesassignee: Adriano dos Santos Fernandes [ asfernandes ] |
Modified by: @asfernandesstatus: Open [ 1 ] => Resolved [ 5 ] resolution: Fixed [ 1 ] Fix Version: 4.0 Beta 1 [ 10750 ] |
Modified by: @pavel-zotovstatus: Resolved [ 5 ] => Resolved [ 5 ] QA Status: No test => Deferred Test Details: Have question about "Statement failed, SQLSTATE = 25000 / no transaction for request". |
Modified by: @pavel-zotovstatus: Resolved [ 5 ] => Resolved [ 5 ] QA Status: Deferred => Done with caveats Test Details: Have question about "Statement failed, SQLSTATE = 25000 / no transaction for request". => Added check for all statements mentioned in "README.management_statements_psql.md " except: Sent letter to dimitr, hvlad and alex, 09.03.2019 13:43. |
Modified by: @pavel-zotovstatus: Resolved [ 5 ] => Closed [ 6 ] |
Modified by: @pavel-zotovstatus: Closed [ 6 ] => Closed [ 6 ] Test Details: Added check for all statements mentioned in "README.management_statements_psql.md " except: Sent letter to dimitr, hvlad and alex, 09.03.2019 13:43. => Added check for all statements mentioned in "README.management_statements_psql.md " except: alter session reset. Sent letter to dimitr, hvlad and alex, 09.03.2019 13:43. |
Submitted by: @asfernandes
Current management (SET ... / ALTER SESSION) statements are valid only
as top-level statements (and hence in EXECUTE STATEMENT too), i.e.,
cannot be in EXECUTE BLOCK or stored routine.
This is a problem, as some of these statements are good to be executed
in ON CONNECT triggers.
I propose a simple way to allow them in PSQL.
There is no reason to create BLR codes for them.
DSQL can generate them as EXECUTE STATEMENT (blr_exec_sql).
They will be validated (dsqlPass) as others statements in prepare time,
and will be validated as now when executed.
Commits: 200720e 3909a7e
====== Test Details ======
Added check for all statements mentioned in "README.management_statements_psql.md " except: alter session reset.
Test for SET TRUSTED ROLE was implemented as separate file "core_5887-trusted_role.fbt"
Test for "ALTER SESSION RESET" was deferred.
Sent letter to dimitr, hvlad and alex, 09.03.2019 13:43.
The text was updated successfully, but these errors were encountered: