biergit

Note that this is not a backward compatible solution to https://liquibase.jira.com/browse/CORE-3208 Before this bug was introduced `SOME_SEQUENCE.nextval;1;1` was valid CSV data to import to Oracle. With https://github.com/liquibase/liquibase/pull/944/commits/3df26067ffd15d3605ee6d48e8778af832301953 `SOME_SEQUENCE.nextval` would be...

Sorry, basically I just wanted to point out that while `SOME_SEQUENCE.nextval;1;1` was resolved to `NULL` it will result in an exception with your change. The whole problem of the wrong...

I'm currently updating from `3.5.3` and I'm facing the `NULL` problem and came here in hope of finding a fix for it. The sequence reference is classified as computed value...

You are definitely moving in the right direction. I hope https://liquibase.jira.com/browse/CORE-3208 will be addressed soon too :)

I see a lot of open PRs here. Regarding your change wouldn't it be better if the computer parameter was not determined by an extra roundtrip to the DB but...

Hey @ro-rah thank you for the quick and thorough heads-up. I would love to see the focus on fixing the regressions and preventing them in the future with better tests...

Hey @zbynekvavros I suggest you take a look at the patch supplied at https://liquibase.jira.com/browse/CORE-3208 Setting the computed value by using `setObject` does not work as for example a value `SOME_SEQUENCE.nextval`...

Sorry, I am no JS expert. This is what I did: ``` formatter: function (messages, context) { const first = messages[0] if (messages[0]) { messages[0] = new Date().toUTCString() + '...

Hey @rstoyanchev on another thought there is also the "title" member for which having an equally convenient i18n measure may be nice. What do you think? Then I read about...

Hey @filipelautert and @MalloD12 could you confirm that https://github.com/liquibase/liquibase/pull/944#issuecomment-618939540 works now?