Closed augensalat closed 5 years ago
Hi, thanks! I'll have a look at this soon: hopefully within the next ten days. I will definitely be happy to make this behavior more consistent and reliable, since as you noted, there's a bunch of reports about it!
Hi, thanks! I'll have a look at this soon: hopefully within the next ten days. I will definitely be happy to make this behavior more consistent and reliable, since as you noted, there's a bunch of reports about it!
Reminder!
Summary
Implement a more robust SQL splitter upon SQL::SplitStatement
BEGIN stmt1; stmt2; END
blocksDELIMITER
#
or--
in stringsDo not remove "false" transactions
Do not create DDLs with surrounding
BEGIN
/COMMIT
just to remove anything that seems to be a transaction later in the deployment phase (which currently reliably fails with PROCEDUREs, TRIGGERs and everything else that uses theBEGIN
keyword).This feature is off by default to keep backwards-compatibility.
References
Fixes
47
68
72
... and probably a few more