Opinions Wanted: Permision Structure

From: Meyer Tollen <ParagonMT_at_email.msn.com>
Date: Tue, 9 Mar 1999 00:30:45 -0500
Message-ID: <urvcw4ea#GA.257_at_upnetnews03>

[Quoted] I am creating my first Oracle App (that others are going to use) . I created [Quoted] a user with DBA privies to create all of the tables, constraints, sequences, [Quoted] [Quoted] etc. Now I am creating the forms using Dev2000. From anybody's real world experience what is the best method to Allow others to log in with their account (not the account that owns the tables) access the tables, triggers etc with full permissions through the forms.

Specifically, should I:

1)create public synonyms for all objects and use those names in my code throughout the app. (query the data dictionary to find all objects owned by the creation user and create the synonyms programmatically)

[Quoted] 2)use the actual names of the tables and other objects and code with the schema.tablename context (as opposed to tablename).

[Quoted] 3)or is there a better organized way to approach this?

[Quoted] A reply would be most helpful, I understand how grants, and synonyms work but am not sure what the standard or best practice way to address this is. I [Quoted] would like to start out on the right foot with this application. Received on Tue Mar 09 1999 - 06:30:45 CET