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)
Please give the possibility to filter CheckIn Files by name with wildcards and also with Object-Type.
Filter to exclude certain type of Obects to List and check in
I’ve been working on this in an experimental branch and it’s almost ready for testing. If you want to get involved drop an email to me at email@example.com.
This allows objects to be filtered based on type or substrings (both include and exclude).
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.
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?
Thanks for your request, we're researching this at the moment. It would really help if you could be more specific about why you'd like this and what you're hoping to achieve.
Are you simply trying to make life easier on the Check In tab? Or perhaps trying to exclude certain objects from ever making it into source control?
If it's the latter, I'll merge this idea with the following: