46 results found
-
object history
I would like to have the option (like in TortoiseSVN) to be able to check all revisions in which the indicated object was changed (either by name or by click). The history of the specified object would be very helpful.
1 voteCurrently, in the tool, we only show all the history. If you use TortoiseSVN or another VCS client or command line, you can see the history for a particular object by locating that object's file in the repository and viewing that file's history.
-
Include option to create refresh groups (like Refresh Group X)
Would be nice to be able to include projects into fresh groups -- so group or similar projects could be refreshed together.
Individual refreshes may become tedious, and the Refresh All may be too broad.
Alt as a simpler implementation provide the ability to exclude projects from a bulk (Refresh All) -- e.g. by marking a project as inactive.
Example:
If I have 15 projects total:
- 5 defined as belong to Group A,
- 4 belong to Group B,
- 4 are unaffiliated
- 2 are inactiveWould like to be able to:
- refresh Group A (project count:…3 votes -
Project Display Order
Allow for manual ordering (e.g. drag and drop and/or move up / move down functionality) for Source Control Projects (vs. by name only)
3 votes -
Multi-Select for conflict resolution
Ability to tick multiple items and resolve when faced with lots of conflicts
1 vote -
GIT should not download the entire repository
When I look at RedGates local files, it has downloaded my whole solution. Shouldn't it just be getting the files in the database folder I specified? For bigger projects this takes a long time.
1 vote -
DB or Version Control URL update functionality
There is no functionality to update an existing project GIT repository or DB URL.
I have to update it under :
ConnectionStore.xml and LinkedDatabase.xml
1 vote -
Add support for Git Push and Pull requests
Add the ability to perform push and pull requests through the Source Control for Oracle GUI
23 votesIn our new migrations-based solution, Redgate Change Control, we treat Git as a Distributed Version Control system with Push and Pull capabilities.
We are working towards merging these tools into 1 tool to meet all your database versioning needs. At that point, we should be able to provide push and pull for Git for state-based projects.
For more information about version control in Redgate Change Control, see https://documentation.red-gate.com/dso/redgate-change-control/version-control.
Please let me know if you have any questions. Thank you!
-
Please add ssuport for oracle CONTEXT object
The Oracle CONTEXT object is not seen by Source Control.
9 votes -
Include support for ignoring ignored items in subversion
Include support for ignoring ignored items in subversion
This is NOT the same as filtering out objects. Once an object is in the svn:ignore it is supposed to be dead to subversion until revived.
2 votes -
Merge grants (or similar)
Here is the issue we are having.
Two developers are working on different instances of the same database schema. If both of them add grants to the same user or role to different objects an issue arises when trying to commit to the repository.
The user that commits second will have a conflict.
If they choose the repository's grants for that user, they will lose their changes on their instance.
It they choose the database's grants for that user, they will overwrite the other user's changes in the repository.It would be really nice to have one of these options…
5 votes -
Edit a project
Please add a way of editing an existing project
116 votesIn Source Control for Oracle v5.7, you can update your database credentials – https://documentation.red-gate.com/soco/release-notes-and-other-versions/source-control-for-oracle-5-7-release-notes.
In 2019, we released Redgate Change Control, which is our migrations-based solution for versioning database changes. We are working towards merging these 2 tools into 1 tool for all your database versioning needs. At this time, we’ll hope to have a better way to edit other project information.
Please let me know if you have any questions. Thank you!
-
Add database objects to source control
Please allow us to add database level objects to source control (schemas/roles/profiles/quotas/objects)
30 votes -
Provide a merge option for conflicts
Instead of take database version, or take source control version, we sometimes wish to merge the two changes.
(If you vote on this idea please also mention any tools you use for merging files in source control)
54 votes -
Make Working With Many Schemas Easier in the Project Creation Wizard
We have dozens of schemas in our shared test database, and they're all part of the same project, so they would be versioned together.
The current flow of the project creation wizard makes adding all these schemas one at a time to the new project a real pain.
So, at the moment, when creating the project, we have to choose a single schema from Step 3 (Choose a Schema), then type in the name of the schema to serve as the folder name in Step 4 (Choose a Folder), then click "Add another schema..." and do the same thing again…
53 votesIn Redgate Change Control, our migrations-based versioning tool, users can specify multiple schemas in a comma separate list. We’re working to merge these tools together and have 1 tool for versioning database changes. When we do this, we’re hoping to make working with multiple schemas easier.
Please let me know if you have any questions about this.
-
Share project with others
It would be convenient to be able to share source control projects with other users. Without this you either have to only have one person managing the sync between the database and source control system or each person has to create a project on their machine with the same settings.
47 votesIn 2019, we launched Redgate Change Control, our migrations-based versioning tool, which has a way to Open a project that you get from version control. We’re working to merge these tools together and have 1 tool for versioning database changes. When we do this, we’re hoping to make sharing projects with others easier.
Please let me know if you have any questions about this. Thank you!
-
78 votes
The Linux cmdlines for Schema Compare for Oracle, Data Compare for Oracle, and Code Analysis for Oracle are now available on Linux. These can be downloaded from https://documentation.red-gate.com/dso.
We are also working on merging our Source Control for Oracle tool (our state-based database versioing tool) with Redgate Change Control (our mibrations-based database versioinng tool) to handle all your database versioning needs. This will be available on Linux. More information about Redgate Change Control is available at https://documentation.red-gate.com/dso/redgate-change-control/getting-started-with-redgate-change-control.
Please let me know if you have any questions. Thank you!
-
Add Versioning Support for Directory Objects
It would be nice if SC for Oracle could add versioning support for directory objects and their privileges.
These are the directory objects that are created like this:
CREATE OR REPLACE DIRECTORY temp AS 'c:\temp';
and the list of directory objects comes from sys.alldirectories and their permissions from alltab_privs, like this:
SELECT alltabprivs.*
FROM alldirectories
JOIN alltabprivs ON (alltabprivs.tableschema = 'SYS' AND alldirectories.directoryname = alltabprivs.table_name);8 votes -
Revert to a previous version
Please add the ability to revert my schema(s) to a previous from the history tab.
I understand this is currently possible by checking the version out to a folder, and using Schema Compare to deploy changes, but it would be much more convenient (and cheaper!) from within Source Control.
5 votes -
Formatting...
Without wishing to start a religious war, am I really alone in disliking all-caps formatting for keywords? I don't want to be shouted at when looking at scripts ... and in our modern era of editors with colour coding it's unnecessary.
And the use of quotes for column names when it's not necessary?
And the inclusion of "NULL" for table columns when it could be left out?
And, for readability, I normally format table creation scripts (and others) so the column names line up, the column types line up, the "not null" clauses (if present) line up, etc.
And any…
12 votes -
Repository Change History is not Respected
On git when new Features are merged into Develop Branch , Source Control take Database Schema as Good and not the new changes on Develop. If like don't considerate last DDL TIme of an object to diff between new and old.
One example are Hot Fix merged on Develop branch, when a horfix was resolved and you are going to integrate changes in Develop Database, Source Control consider Develop Database as Good schema and not the new Hot Fix Change merged into Develop Branch. Generating Check In changes and not Get In Updates.
3 votes
- Don't see your idea?