26 results found
-
Add support to ORACLE_LOADER and ORACLE_DATAPUMP access drivers
Add support to ORACLELOADER and ORACLEDATAPUMP access drivers to fix some bugs related to external tables (see http://www.red-gate.com/MessageBoard/viewtopic.php?t=16543)
1 voteexternal tables were included in v1.0.0.707
-
Allow source control in sub-folders of repository
Allow for saving of database versioning in a sub-folder of the subversion repository rather than just the root of the repository.
4 votesThis should now be fixed in the beta released yesterday (21 Feb), please do let us know if there are still issues!
-
Put package header and body in seperate files.
When a repository is created from the database, both the package header and the package body are placed in a single file. It would be more usable if the spec and body were in separate files in the same folder with a .pks or .pkb extension respectively.
9 votesthis will be in the next release of Schema Compare and Source Control for Oracle
-
Allow us to choose the schema prefix
We noticed that all objects have a prefix in front of it.
The prefix happens to be the same as your folder name. I would prefer it if it was the same as the schema name, or NULL. Preferably give us the right to choose a prefix name.9 votesI believe you can do this in the latest version of Source Control.
Either you can make your schema name the same as the folder when you setup your project.
Or you can now access the options via right-click on the project on the projects page and select “Edit comparison options…” and use the option “Exclude schema names”
-
SID is limited to 8 characters
The SID for my oracle instance is 10 characters. The connection wizard only allows 8 characters so can't use the product.
3 votesshipped via check for updates today
-
Match source when creating repository files.
When checking in a new package from the database, the schema name in references throughout the package is changed to have double quotes around it. Then when a change is made on the file, the entries from the database without the double quotes do not match the entries from source control with the double quotes. It seems that this difference alone isn't enough to show the comparison as different, but when another difference exists, these entries are all flagged as different. To resolve this, the double quotes should not be created in the first place.
1 voteThanks Leigh. We believe this is fixed in the latest beta release, please do advise.
- Don't see your idea?