...
- Use the Datical DB GUI to choose
warnorfailin thestoredLogicValidityActionoption. If set to fail, the deployment halts and prints an error when the stored logic validity check returns errors. - Use the CLI to set
invalidsActiontowarnorfail.
...
| Description | |
|---|---|
| DAT-1924 | SQL Parser: Quick Deploy still calls SQL Parser. |
| DAT-2018 | Doc + Test: Add documentation of hammer runRules to Datical CLI References page. See CLI Commands#runRules. |
| DAT-2116 | Ignore version 0 change sets from status operations |
| DAT-2122 | In the deploy report, ID column is overwriting the Author column when sql filename is long |
| DAT-2214 | DOC + TEST: Work around instructions for when packager has forecast errors due to SQL Parser limitations. See "Debugging Procedures..." in Using SQL Parser. |
| DAT-2236 | "Full Output" link in forecast report not working if forecast was successful |
| DAT-2396 | DOCUMENTATION ONLY: Provide instructions on how to add labels using the logical operators AND and OR in the dbDef settings See new instructions and examples: Datical Liquibase Enterprise Labels |
| DAT-2509 | Packager: Convert_sql should not run stored logic validity check |
| DAT-2773 | DOC + TEST :: Set NLS_LANG for Oracle Sqlplus Character Issues. See updates in Writing SQL Scripts for Datical DBLiquibase Enterprise. |
| DAT-2801 | DOC & TEST :: Configuration of Schema Name for Multi-Catalog. Always use fully-qualified object names in SQL scripts for multi-database projects. See updates: |
| DAT-2873 | DOC & TEST: Update ALPHANUMERIC packagerOrderStrategy with a useful example (attached) See example in Choosing a Packaging Method. |
| DAT-2946 | Spaces in SQL file names fails to forecast and deploy in higher DbDefs |
| DAT-2953 | Implement Oracle Backup/Restore Using Datapump Packages. See Configuring Deployment Packager to Use the Oracle Datapump API for Backup and Restore. |
| DAT-2963 | DOC - GUI crashes / cannot access existing projects after installing new 2019.2.x GUI |
| DAT-3018 | Add new project property :: storedLogicValidityAction. See storedLogicValidityAction in Configuring Project Settings |
| DAT-3093 | As a user, when I successfully package a valid cleanup change set, I get an error (only in my daticaldb.log) which is misleading and confusing |
| DAT-3111 | DOCUMENTATION ONLY: As a user, I need to know how to increase RAM performance used by Datical on Windows OS |
| DAT-3227 | DOC Infrastructure - move back to centralized doc space |
| DAT-3239 | GUI: "Identifier" field in "Edit Connection" dialog is not properly reverting or saving data |
| DAT-3271 | Liquibase checksum mismatch for Unique Constraint changes deployed prior to 2019.2.2 - See Known Issues, "Checksum Errors..." |
...
Datical now notes version matching for clients working on the same release pipeline. See Datical DB Liquibase Enterprise Version Requirements.