title: liquibase formatted sql file containing multiline rollback statements to allow Oracle PL/SQL
body: <p>I am using Liquibase version 3.5.3, writing "formatted sql" files that need to execute PL/SQL (to our Oracle 11g database).</p>
  
  <p>The changeset uses the "endDelimiter:/" option to allow this.</p>
  
  <p>--liquibase formatted sql
      --changeset mike:51.9 endDelimiter:/
      /* --  'Create/Modify triggers for FIN_PLANS' -- */
      BEGIN
         HIST_PKG.TRIG_HIST_TAB('FIN_PLANS');
      END;
      /</p>
  
  <p>The rollback for this changeset similarly needs to execute PL/SQL, however despite numerous searches I can not find a way to do this. 
  I have tried specifying multiple rollback statements, but each rollback line is executed individually (as in "sql statements") and I don't know how to make it recognise it is a PL/SQL "block".</p>
  
  <p>I've tried the endDelimitor option on the rollback but it is not recognised.
  I've tried assuming that the endDelimitor option for the changeset also applies to the rollback, but alas no.</p>
  
  <p>What I want is something like ...</p>
  
  <pre><code>--liquibase formatted sql
  --changeset mike:51.9 endDelimiter:/
  /* --  'Create/Modify triggers for FIN_PLANS' -- */
  BEGIN
     HIST_PKG.TRIG_HIST_TAB('FIN_PLANS');
  END;
  /
  --rollback endDelimiter:/
  --rollback BEGIN
  --rollback  HIST_PKG.TRIG_HIST_TAB('FIN_PLANS');
  --rollback END;
  --rollback /
  </code></pre>
  
  <p>My searches have turned up 
  <a href="http://forum.liquibase.org/topic/issue-with-pl-sql-and-rollbacks" rel="nofollow noreferrer">http://forum.liquibase.org/topic/issue-with-pl-sql-and-rollbacks</a>
  But this solution is using "format xml" (not "format sql").
  Also <a href="https://liquibase.jira.com/browse/CORE-1608" rel="nofollow noreferrer">https://liquibase.jira.com/browse/CORE-1608</a> was created but this has since been closed, as it also points out it can be done with "format xml".</p>
  
  <p>So is it possible to write liquibase rollbacks in "formated sql" files that support calling PL/SQL code?</p>