46 results found
-
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).
Thanks!
1 vote -
Keyboard Shortcuts
The tool does not support keyboard shortcuts so a user must rely on slowly moving the mouse around to configure the app. An example is that to add multiple schemas, I have to click
Edit Project --> put my hands on the keyboard to search --> back to mouse to select Next --> Next --> Move mouse and select Edit Project... continueMany developers rely on keyboard shortcuts to speed work and it is common in most UIs.
1 vote -
Do not check CheckIn-Scripts for errors optionaly
Please give the possibility to CheckIn Scripts without error-checking optionaly!
5 votes -
Performance
The step where the product (Source Control for Oracle) accesses the Oracle instance to return a list of schemas is taking a long time to run, and in one of my development instances, it actually fails to finish.
It seems to be running the following SQL
(SELECT username, 'TRUE' as isempty from allusers
minus
select owner, 'TRUE' as isempty from allobjects)
union all
( SELECT username, 'FALSE' as isempty from allusers
intersect
select owner, 'FALSE' as isempty from allobjects)if the query accepts parameter(s), it should speed up that part tremendously.
(SELECT…
4 votes -
Add database objects to source control
Please allow us to add database level objects to source control (schemas/roles/profiles/quotas/objects)
30 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!
-
View the parameters used in the creation of the project
Once created, there is no easy way to see which parameters were used (and none for things like username, and what the user connected as)
2 votes -
Support for IBM Rational ClearCase
Please add support for IBM Rational ClearCase to Source Control for Oracle
6 votesRichard Mitchell respondedYou can now use any source control system in the v3 release of the tool by using “Working folder” which saves changes to disk and allows you to use external tools to commit and retrieve your changes.
-
Support for Serena PVCS
Please add support for Serena PVCS Version Manager (PVCS VM)
http://www.serena.com/index.php/en/products/pvcs-vm/3 votes -
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 -
Undo changes before they are checked in
Please add the ability to undo changes to an object in the check in screen. They should be undone to the latest version in source control.
Much like this feature in SQL Source Control: http://www.red-gate.com/supportcenter/content/SQL_Source_Control/help/3.1/SSC_Undo
7 votesFor any objects that are CREATE OR REPLACE, highlight the code under “Source Control” in the check-in screen and execute it in your schema to get back to the version in source control.
This will not work for tables and please keep voting/commenting here if you need this.
-
Support versioning Java within the Oracle database
Please add support for versioning Java source code within the Oracle database, for example Java Stored Procedures
7 votes -
Maven plugin
With a maven plugin developers could easily automate deploys. The plugin should be configureable, but include the possibilites of first pulling from a developer database into svn. Then pushing the changes from svn (including other changes registered in SVN) towards a deploy test database.
36 votes -
Extend the project defintition
Source Control for Oracle could also become apart of the deployment project. This way you would like to have connections towards different databases in the same project. For instance I would like to have a connection towards development, test, qa and maybe even production for the same project. This way I could develop, pull changes to svn, push changes to test, then to QA, and at last to production.
It could also be very handy to be able to change the SVN (or have several SVN connections) for instance to a tag (release) library.
Then you could easily rollback to…1 vote -
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 -
Add support for Vault to Source Control for Oracle
Please add Vault support
7 votesRichard Mitchell respondedYou can now use any source control system in the v3 release of the tool by using “Working folder” which saves changes to disk and allows you to use external tools to commit and retrieve your changes.
-
Option to automate check-ins
We would like to have an option to enable automated check-ins. Basically, this should poll the database after every "x" minutes and see if there are any pending changes and use a automated comment like -
"Changed these objects on [date/time] by [xyz] -
table1,
view1,
package1,
package2
function1"(Please add any more relevant data you feel would be necessary)
Ideally, we would want to check in every script as soon as it is deployed in the database. But since, for doing that you would need an extension in our IDE, automated polling would be sufficient as well. The aim…
21 votesRichard Mitchell respondedI’m not sure how generally useful this feature would be. I’m trying to understand your use case to see what problem you’re trying to solve.
Could you give me more details?
-
Display who made each change in the check-in screen
In a shared development database, all users can see every change, but not who made each one. Please show who made each change, and consider hiding those not made by me (or de-selecting them for check-in by default).
9 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.
- Don't see your idea?