shantstepanian
shantstepanian
Currently, the permission scheme is only applied to objects when they are created. If a scheme is modified, it won't affect existing objects It would be nice to detect changes...
For general how-to questions or feature requests, please ask away. For bugs/errors, please provide the following if feasible: * Description of problem * Steps to reproduce the issue (e.g. the...
This is meant as a convenience utility for users to clean up their existing databases of unwanted objects
* Do the comparison of object name from the file name vs. file content (e.g. checking the create view statement) * Checking the file name if it is multipart and...
### Expected Behavior When a migration change is dropped, it should be left as inactive in the DB. This is desirable for a couple reasons: 1) if it were accidentally...
(comment 2020-06-23 - this may already be fixed. We should verify this via RollbackScenarioTest)
We don't want to build releases on any tags, just for releases
The NEWREVENG command had performance issues for schemas with large # of files (we had a SQL Server use case with ~23,000 objects). Upon profiling, looks like the "replaceSnippet" call...
The Rollback detection logic (see DefaultRollbackDetector class) has a sanity check to verify that all schemas in a deployment have the same rollback behavior. i.e. if schemas are managed in...