Hello first post - currently using 4.29.1 with Oracle
Any time there is a space included after a delimiter (I use forward slash ‘/’) the changeset will fail. We’ve gotten better at troubleshooting when this happens but sometimes it still bites us since you can’t see the space normally. Has this been addressed or are there plans to address? Nothing came up in related searches. Ideally Liquibase would just ignore any superfluous spaces.
Are you using SQL Changelog format?
We are also using Oracle, but I cannot remember having seen issues with space after delimiter. But in my experience the SQL changelog format has more issues than other formats (I mainly use yaml format, and sometimes XML, I haven’t tried json).
We currently use liquibase 5.0.1. We did use 4.29.1 for a short period of time, and then were stuck on 4.29.2 for quite a long time due to bugs in subsequent versions.
yes, SQL format
I generally have to use Notepad++ and turn on all characters in order to find the spaces. An inexperienced dev can certainly spin their wheels troubleshooting since everything “looks” good
