Skip to content

Oracle

Welcome to our Oracle solution feature suggestion site. Find out more information about our current offering at www.redgate.com/oracle.

If you have any questions, need help, or have found a bug, please visit the forums at forum.red-gate.com/categories/oracle-tools.

Oracle

Categories

JUMP TO ANOTHER FORUM

(thinking…)

How can we improve our Oracle solution?

You've used all your votes and won't be able to post a new idea, but you can still search and comment on existing ideas.

There are two ways to get more votes:

  • When an admin closes an idea you've voted on, you'll get your votes back from that idea.
  • You can remove your votes from an open idea you support.
  • To see ideas you have already voted on, select the "My feedback" filter and select "My open ideas".
(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

8 results found

  1. check-in comment/message as mandatory field for commits to a repository

    Please provide an option for Source Control to make the check-in comment a mandatory field for all commits to a repository. Commits/check-ins without comment should be rejected. With the current Version of Source Control (5.3.1.2355) it is possible to commit changes without a comment to a git repository in Azure DevOps - even though a local git repository doesn't allow to commit without a message.

    24 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    0 comments  ·  Source Control  ·  Admin →

  2. Hanging/ all projects invalid

    Once upgraded to new version all my existing projects became invalid, would be nice if they all still worked. Then if I try to remove more than 1 the application hangs and I have to kill it.

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    0 comments  ·  Source Control  ·  Admin →

  3. Source Control for Oracle connection dialog does not seem to like service names instead of old-school SIDs

    and maybe other Oracle tools in addition to Source Control. I attempted to connect with a full service name e.g. XYZ.my.domain.gov
    and it said the SID was invalid. Well, umm, yes, because it is a SERVICE name not an SID, but perfectly legitimate in an Oracle connection nonetheless. This is related to the EZCONNECT suggestion I also posted.

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    3 comments  ·  Source Control  ·  Admin →
    declined  ·  Richard Mitchell responded

    If there is no oracle client install and located by the software then we can only connect via a sid. Often it can be issue with having a x64 client but running the x86 tool

  4. Respect svn:ignore in Source Control for Oracle

    Source Control for Oracle does not seem to respect svn:ignore property. Please include that in a future release s owe can exclude test tables, procedures, and the like.

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    0 comments  ·  Source Control  ·  Admin →
    declined  ·  Richard Mitchell responded

    The upcoming release adds a feature called “object filtering” which can be set on a project level and stored in source control. With this you can exclude whole object types or just objects that “contain” a substring e.g. “Test_” you can then override the exclude with another “contain” string setting e.g. “Test_Important” should too much be excluded.

    It’s got a simple UI accessed via the right-click menu on the main projects screen.

  5. bug on context index and xmltype column

    Refresh afte commit changes show incorrect changes with context index on xmltype column.

    For example:
    create table t1(col xmltype);

    create index idxtest on t1(col)
    indextype is ctxsys.context
    parameters ('datastore ctxsys.default    datastore
    filter ctxsys.nullfilter
    section group ctxsys.auto    section_group
    sync (on commit) memory 16m');

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    0 comments  ·  Source Control  ·  Admin →
    declined  ·  Richard Mitchell responded

    I’ve confirmed this issue and raised it as OSC-357 unfortunately as it was an anonymous submission I can’t respond to you directly.

    I’ve declined this as a feature as it’s a bug report

  6. get latest - mixing and matching use database version and use source control version

    Please note I am on version 2.x beta:

    There appears to be some issues when mixing and matching the following options "use source control version" and "database version". When I tried to check my changes in on the check-in tab i received an error "check-in failed some objects were out of date. Review changes and check in again". Tried to submit this as an error with the report button but I get a System.NullReferenceException.

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    0 comments  ·  Source Control  ·  Admin →

  7. Offer ways to customize extensions and folders to each object type

    Would be nice to be an option to customize the folder names and the object types related to this folders, same for the file extensions.

    6 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    1 comment  ·  Source Control  ·  Admin →
    declined  ·  Richard Mitchell responded

    I’m afraid this is too large a change to the structure of the engine to be supported.

  8. Support Mercurial

    54 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    4 comments  ·  Source Control  ·  Admin →
    declined  ·  AdminDavid Atkinson (Product Manager, Redgate) responded

    This item will be closed. You can now use Mercurial by using “Working folder” which saves changes to disk and allows you to use external tools to commit and retrieve your changes. This requires use of your own Mercurial client tool, but feedback indicates that this is preferred as it grants more control over commits and pushes, and allows atomic commits. Please get in touch if you have any questions.

  • Don't see your idea?