Re: Protecting stored procedures in a commercial product
...SQL SECURITY=INVOKER... restricts privs to, um, the invoker's, which should include all that the routine does, but should not include
To see sproc code you must be the user named in the routine DEFINER clause or have SELECT access to the mysql.proc table. Presumably your users will not have that priv.
Subject
Views
Written By
Posted
1335
May 31, 2019 02:33PM
Re: Protecting stored procedures in a commercial product
466
May 31, 2019 03:33PM
353
June 01, 2019 12:38PM
402
June 02, 2019 05:13PM
356
June 02, 2019 07:50PM
Sorry, you can't reply to this topic. It has been closed.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion
of Oracle or any other party.