Allow Locking feature to work with automatic re-compiles due to PL/SQL invalidation
It would be awesome if the tool would let automatic re-compiles work with Locked objects when a package spec/body is invalidated by a change to another package. As it is now - and automatic re-compile (without a code change) is blocked by the REDGATE.CHECK_LOCKS database trigger.
Could Red Gate be changed to allow automatic re-compiles (as opposed to code change compiles)? Perhaps performing a checksum between the code and the Subversion repository could work (though this would require the database instance to communicate with the repository).
Anonymous shared this idea