anchor.diff:  | Location
   
   |db2
  -|jbpm-installer/db/ddl-scripts/db2
  +|jbpm-db-scripts/db/ddl-scripts/db2
   
   |derby
  -|jbpm-installer/db/ddl-scripts/derby
  +|jbpm-db-scripts/db/ddl-scripts/derby
   
   |h2
  -|jbpm-installer/db/ddl-scripts/h2
  +|jbpm-db-scripts/db/ddl-scripts/h2
   
   |hsqldb
  -|jbpm-installer/db/ddl-scripts/hsqldb
  +|jbpm-db-scripts/db/ddl-scripts/hsqldb
   
   |mysql5
  -|jbpm-installer/db/ddl-scripts/mysql5
  +|jbpm-db-scripts/db/ddl-scripts/mysql5
   
   |mysqlinnodb
  -|jbpm-installer/db/ddl-scripts/mysqlinnodb
  +|jbpm-db-scripts/db/ddl-scripts/mysqlinnodb
   
   |oracle
  -|jbpm-installer/db/ddl-scripts/oracle
  +|jbpm-db-scripts/db/ddl-scripts/oracle
   
   |postgresql
  -|jbpm-installer/db/ddl-scripts/postgresql
  +|jbpm-db-scripts/db/ddl-scripts/postgresql
   
   |sqlserver
  -|jbpm-installer/db/ddl-scripts/sqlserver
  +|jbpm-db-scripts/db/ddl-scripts/sqlserver
   
   |sqlserver2008
  -|jbpm-installer/db/ddl-scripts/sqlserver2008
  +|jbpm-db-scripts/db/ddl-scripts/sqlserver2008
   
   |sybase
  -|jbpm-installer/db/ddl-scripts/sybase
  +|jbpm-db-scripts/db/ddl-scripts/sybase
   |===
   
   
  
positive.code: 
  [NOTE]
  ====
  If you use MySQL 5.7 or earlier (MariaDB 10.2.3 or earlier), you also need to run [path]_jbpm-installer/db/ddl-scripts/mysql5/mysql-jbpm-amend-auto-increment-procedure.sql_
  
  This script creates a procedure for jBPM tables (ProcessInstanceInfo/WorkItemInfo/Task) to protect AUTO_INCREMENT counter. Without the procedure, ID values of those tables could be reset on MySQL/MariaDB restart (https://dev.mysql.com/doc/refman/8.0/en/innodb-auto-increment-handling.html#innodb-auto-increment-initialization). It would introduce further side effects.
  
  
negative.code: 
  [NOTE]
  ====
  If you use PostgreSQL with jBPM, you also need to run jbpm-db-scripts/db/ddl-scripts/postgresql/postgresql-jbpm-lo-trigger-clob.sql
  
  This script creates triggers for jBPM tables to protect CLOB references of large objects. Without the triggers, vacuumlo tool (https://www.postgresql.org/docs/9.4/static/vacuumlo.html) deletes active large objects so causes an issue to jBPM. If you are already running jBPM without the triggers, you also need to run the following SQLs after applying the triggers to protect existing CLOB.
  [source,xml]
  