...
- Caveat: If you are not using SQL Parser, then only sqlrules would apply in sql_direct folder. (Other types of rules and forecast modeling do NOT apply in the sql_direct folder if you are not using SQL Parser for Oracle.)
- If you are using Oracle with a recent version of Liquibase Enterprise/Datical DB 7.6 or higher x, you could consider using SQL Parser for Oracle to add forecast modeling and forecast rules.
- When you enable the SQL Parser for Oracle project setting, SQL Parser is applicable by default to the data_dml folder (packageMethod=data_dml) and sql_direct folder (packageMethod=direct) and sql folder (packageMethod=sqlfile).
- You could also opt to set packageMethod=direct for your ddl folder so that folder would also use SQL Parser. Using SQL Parser with packageMethod=direct for ddl would be faster than using the packageMethod=convert for ddl (convert is the default for ddl). You can change the packageMethod for the ddl folder in the metadata.properties file for the ddl folder.
- If your DML scripts are quite large, you could disable SQL Parser for the DATA_DML folder for performance reasons. You can disable SQL Parser at the folder level by setting disableSqlParser=true in the metadata.properties file for the DATA_DML folder. Note that you only need to set disableSqlParser=true for DML in older Datical versions 7.5 and below. Parser is already disabled for DML by default in newer Datical versions 7.6 and higher.
- There were improvements to SQL Parser for Oracle in versions 6.15, 7.6, and 7.8. We recommend upgrading to a recent 7.x version if you are using SQL Parser for Oracle.
- Please see these pages:
...