|
Hi, ADS-team. Why you decided to limit the right to disable all triggers? For ver.11 "no permissions are required for users to disable triggers on themselves", but now for ver.12 "In order to disable triggers on the current connection, membership in the DB:Admin group is required". We can't include all our users in DB:Admin group for security reasons and without that our ERP-application has stopped working :(. How is it possible to get around ? |
|
The behavior change in ADS 12 was introduced to resolve security concerns. The decision to implement was taken after due discussion, and security implication was considered more important. Now, however we are discussing this again, and are looking at the possibility of providing a work around so as to avoid breaking current application. If feasible, this will be provided in an upcoming service pack of ADS12. Thanks. Thank you. We are looking for it
(24 Nov '15, 13:06)
Igor
|
|
IIRC permission check within a stored procedure does not happen. So, as a workaround, you could try to bypass it with a stored procedure: CREATE PROCEDURE RunSQL(s MEMO) BEGIN EXECUTE IMMEDIATE _s; END; Usage execute procedure runsql('execute procedure sp_DisableTriggers(...)');
Many thanks, Joachim.
(24 Nov '15, 18:48)
Igor
Unfortunately this method dosn't work - can't disable triggers from procedure poQuery: Error 7200: AQE Error: State = HY000; NativeError = 5154; [SAP][Advantage SQL Engine][ASA] Error 5154: Execution of the stored procedure failed. Procedure Name: runsql. Error 7200: AQE Error: State = HY000; NativeError = 5196;
(24 May '16, 06:10)
Igor
|
Hi Same applies to me. For batch procesing I need to disable triggers otherwise it will be to slow.
Yes, but not only for that. Sometimes it is necessary to bypass the logic triggers. Independently users do not do, and enjoy the scripts that are written in the program