[MSSQL] MSSQLDatabase#setDefaultSchema that is different from current user schema
Description
Environment
SQL Server 11
Activity
Show:
Former user December 7, 2018 at 10:07 AM
We're also having this problem. This issue has not been acknowledged or responded to in the 7 months since it was raised.
Are there plans to support this under 3.6 or do we need to stick to the 3.5 branch forever? We are using a single unprivileged db user (with default schema dbo), but need to have different applications use different default schemas.
https://github.com/liquibase/liquibase/commit/d0f6f75ae1e0f8b38fe3f5eedc63b56c0fd74d32
This commit made impossible to do the following test scenario:
1. Login as a super user, which default schema is, say, 'dbo'
2. Create the schema you want to apply changelog on, say, 'test_schema'
3. Create
which is MSSQLDatabase
4. Call
5. Apply changelog
Before 3.6.0 it worked like a charm, but then this limitation appeared.
Or am I supposed to create another user setting the created previously schema as his default and then acquire another connection