RE: Avoid a synonym

  • From: Katz.C@xxxxxxxxxxxx
  • To: DWILLIAMS@xxxxxxxxxxxxx, nsouto@xxxxxxxxxxxxxx, oracle-l@xxxxxxxxxxxxx
  • Date: Tue, 2 Nov 2004 17:05:07 -0500

You could avoid synonyms by creating the views in the users' schemas :-)

-----Original Message-----
From: DENNIS WILLIAMS [mailto:DWILLIAMS@xxxxxxxxxxxxx]
Sent: Tuesday, November 02, 2004 11:58 AM
To: nsouto@xxxxxxxxxxxxxx; oracle-l@xxxxxxxxxxxxx
Subject: RE: Avoid a synonym

Nuno - Good point (as always). My reasons are as follows:

1. The application group has their strategy built around public synonyms.
2. My boss likes public synonyms.
3. As I recall, it was Jonathan Lewis who mentioned that public synonyms
could cause performance problems, and I have passed that along to my boss..
If anyone has a personal horror story to share, that might make an impact..

-----Original Message-----
From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx]
On Behalf Of Nuno Souto
Sent: Monday, November 01, 2004 6:52 PM
To: oracle-l@xxxxxxxxxxxxx
Subject: Re: Avoid a synonym

On Tue, November 2, 2004 7:16 am, DENNIS WILLIAMS said:
> I have a group of users that should only see a subset of data in certain
> tables. They share a role. I will create a view that implements that, and
> add it to their role. Then, to allow them to use the same queries as other
> users, I will have them individually create private synonyms that point to
> their views. Does anyone know of a better way, where each user won't have
> create several private synonyms? This is Oracle 9i.

Sorry to ask the obvious question, but
*why* don't you just use private synonyms?


Other related posts: