Nathan Voxland

From Liquibase's standpoint, as a library we try hard not to introduce dependencies on external libraries such as log4j. Therefore, we build off the java.util.Logger but do have a lightweight...

Yes, I will keep the rest of the team up on this discussion. I think that making log4j-api a required part of our API or standard logging implementation is a...

Yeah, @dbyron-sf, I hear your request for best effort functionality. What makes it a larger feature request is that we want it to be something that is useful and makes...

Yes, you are right. Thanks for finding the right one

I'd like to expand this ticket to be a more broad "support best-effort in general" ticket. Currently, the way Liquibase is set up is that it follows what the changelog...

Until the enhancement gets released, beyond the options of: - Remove the problem attributes completely - Use modifySql with dbms attribute - Create two changesSets, one with `dbms="h2"` and one...

#3537 had some similar discussion on this issue. A suggestion there is to use the existing `strict` flag to control whether to count some of these as validations as optional....

That is probably the best description. It is really just used currently when checking the liquibase.properties file and environment variables to fail if there are settings in them that do...

Thinking on implementation a bit, I'm thinking that a `` tag may be the best approach? - It's consistent in spirit with the existing `` - Having it in the...

> My mind is wandering to a place where postgres supports afterColumn one day...but that's probably unlikely. We have the same question on the "dbms" tag in general and figure...