Thanks Rhys.Is there an other way? With your solution the customer can't use standard SQL (they are forced to use our procedure), which means much more support requests.best regardsLukasOn Mon, Oct 24, 2016 at 3:53 PM, <Rhys.Campbell@swisscom.com> wrote:Revoke the DROP permission from the user in question. Create a stored procedure that can drop the tables using the SQL SECURITY DEFINER clause so it's executed in the context of a user with the DROP permission.
https://mariadb.com/kb/en/
mariadb/create-procedure/
From: Maria-discuss [mailto:maria-discuss-bounces+
rhys.campbell =swisscom.com@lists.launchpad.net ] On Behalf Of Lukas Lehner
Sent: Monday, October 24, 2016 3:18 PM
To: Maria Discuss <maria-discuss@lists.launchpad.net >
Subject: [Maria-discuss] workaround for MDEV-9688
Hi
is there a workaround for this issue?
We need it for DBaaS
Lukas
_______________________________________________
Mailing list: https://launchpad.net/~maria-discuss
Post to : maria-discuss@lists.launchpad.net
Unsubscribe : https://launchpad.net/~maria-discuss
More help : https://help.launchpad.net/ListHelp