46 results found
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
There is no functionality to update an existing project GIT repository or DB URL.
I have to update it under :
ConnectionStore.xml and LinkedDatabase.xml1 vote
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
Ability to tick multiple items and resolve when faced with lots of conflicts1 vote
Why should the direction of update have to be selected by a tab? Why not have just one view with two buttons, one for "Apply to Source" and the other for "Apply to Database"?1 vote
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 vote
Currently, 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.
- Don't see your idea?