Bug #88327 DROP TRIGGER patch and other super_read_only fixes
Submitted: 2 Nov 2017 8:40 Modified: 9 Nov 2017 18:21
Reporter: Laurynas Biveinis (OCA) Email Updates:
Status: Not a Bug Impact on me:
None 
Category:MySQL Server: Options Severity:S3 (Non-critical)
Version:5.6 OS:Any
Assigned to: CPU Architecture:Any
Tags: Contribution

[2 Nov 2017 8:40] Laurynas Biveinis 
Description:
This is to contribute a DROP TRIGGER fix for super_read_only and other minor improvements as implemented in Facebook 5.6 patch

How to repeat:
This is to contribute a DROP TRIGGER fix for super_read_only as implemented in Facebook 5.6 patch
[2 Nov 2017 8:40] Laurynas Biveinis 
FB 5.6 super_read_only fixes

(*) I confirm the code being submitted is offered under the terms of the OCA, and that I am authorized to contribute it.

Contribution: super_readonly_percona.diff (application/octet-stream, text), 5.03 KiB.
[2 Nov 2017 9:19] MySQL Verification Team 
Hello Laurynas,

Thank you for the report and contribution.

Thanks,
Umesh
[9 Nov 2017 18:21] Omer Barnir 
Thanks for the contribution. After reviewing (with the Facebook contribution) it turns out that the 'super_read_only' implementation added in 5.7 covers both, so there is no need for both patches