No, preconditions should be checking the schema name as well. If you’ve been looking at it and could submit a patch, that would be great. Otherwise, you can create an issue on liquibase.jira.com and I’ll try to get to it before long.
Nathan
No, preconditions should be checking the schema name as well. If you’ve been looking at it and could submit a patch, that would be great. Otherwise, you can create an issue on liquibase.jira.com and I’ll try to get to it before long.
Nathan
Liquibase 2.0.1
I think defaultSchema is ignored in preconditions. Tests suggests that and I couldn’t find in code where precondition is accessing defaultSchema. In changes there are often lines like:
String schemaName = getSchemaName() == null ? (database == null ? null: database.getDefaultSchemaName()) : getSchemaName();
but precondition is simply reading property. Is it intentional?
Was this ever resolved?
And 3.0 is now available
Nathan
Wohaa! How did I missed that? So… is there a chance for 2.0.6 in near future? 
My current plan is to focus on the 3.0 and 3.1 releases. Ideally everyone can just upgrade from 2.0.5 to 3.0.0 but if there are cases where people cannot upgrade but there are blocking bugs in 2.x I can definitely look at releasing additional 2.x versions with very targeted fixes.
Nathan