Filter objects added to source control
In our schema(s) there is a mixture of third party code that we don't touch, and our own code where we'll amend and add objects. Please add a way to filter out the third party objects.
(If you vote on this, please let us know if the objects concerned are named in a particular way that would make filtering easier)
Anonymous
shared this idea
This is now available via check for updates or to be downloaded from our website.
This allows objects to be filtered based on type or substrings (both include and exclude).
-
Anonymous
commented
We have Oracle Ebusiness Suite. We have a few hundred custom objects which we need to source control but due to Oracles Ebusiness security limitations they have to reside in the Oracle Apps schema. This schema has so many objects (30,000+) that Red Gate Source Control cannot even load the entire list of objects.
We need to be able to pre-filter by object name so that Red Gate will only try to list and source control objects that meet the filter criteria (IC_%).
We use other tools...TOAD and SQL Developer that have this capability, so it seems like it should be possible.
-
Antonio
commented
Hello,
I think this is a great feature. Currently I am testing this application in our environment and we have several tables that we do not need to have under control version. It would be nice if there is an option to filter what you want to include (or exclude) from the versioning.In our case, the objects are usually named with an specific prefix or suffix. Allowing filtering as in SQL with the "like" operator could be enough.
-
Michael Waybright
commented
If a defect is identified and has priority to be deployed to the next environment then filtering any ongoing effort to provide the deployment branch for the unplanned defect has value.
-
Tim Purvis
commented
This would be useful for filtering out SYSNT tables. Is there ever a case where these should be included in the repository?