Public Synonyms

Brian.Lieb

Hello,

I work on an oracle database that makes heavy use of public synonyms. Is there any way using schema compare for oracle to compare PUBLIC synonyms.

I can't seem to find a way to do that.

Brian

richardjm

This was an issue I noted recently myself, we do support synonyms for the database itself but not public synonyms.

I'm still learning all the tools and trying to fix many existing issues, this one is already on my list but I can't give you an estimation of when we might support it.

Currently we're concentrating on adding more granular storage options, object mapping in Data Compare and updating Source Control.

The best way to get your feature supported is to make use of our uservoice page.

http://redgate.uservoice.com/forums/174014-oracle-tools

I appreciate this isn't quite the answer you're looking for. I may do it earlier depending on the size of the work involved but I can't make any promises.

richardjm

Just found a related issue for Source Control in user voice (generally if it's supported by the Schema Compare Engine it's supported in both tools).

https://redgate.uservoice.com/admin/for ... -objects-a

Elizabeth_Keen

See this link for the use of synonyms in Oracle database..

http://www.dba-oracle.com/concepts/synonyms.htm

For innovative web designs and apps visit: http://www.ati-erp.com[/url]

Brian.Lieb

I voted for public synonym support.

As for the link about synonyms, it doesn't really help to hear about how public synonyms are bad practice.

I work on a large system that was developed 10-15 years ago, and synonyms play a large role, including thousands of lines of pl/sql. Dropping synonyms is not a simple undertaking, and without an easy way to track changes via source control, it is made more difficult.

richardjm

[Blatant Product Plug]
You may want to try out our Source Control for Oracle product then
[/Blatant Product Plug]

I think if we did full public synonym support it would slow down population a lot as we'd have to populate all the public synonyms in the database and then work out which are relevant to the schemas selected. This is one of the reasons we tend to avoid database-level objects.