Sharing Objects with Other Vision Developers

When you create an application or application component, such as a form, Vision recognizes you (that is, your account) as its owner. In this way, Vision protects the integrity of individual users' objects in a common database.

These guidelines describe how Vision handles the ownership of the following types of objects, and how you access another user's objects:

Any user can access an application, but cannot have access to the necessary objects to run the application.

Access any objects owned by the database administrator (DBA) for the database, if you do not have an object with the same name. Vision searches for an object owned by you first. If it does not find an object owned by you, then it searches the objects owned by the DBA.

You can access a table or a database procedure if the owner of the object (or another privileged user) has granted you the privileges to access them.

You must indicate the owner when you specify the table or procedure, unless the table or procedure is owned by the DBA and you do not have an object with the same name. For more information about object ownership, see the SQL Reference Guide.

If you are working with other developers, use one of the following methods to ensure that all Vision developers can share objects:

• If the DBA approves, log in directly to the DBA account before you start Vision.

• Alternatively, have the system administrator create a new user account. Each user then must log in to Vision through this account rather than a personal account.

Any objects that a user creates in this account become available to all other users of the account. However, there is no way to tell what a specific user of the account does.

• If you have sufficient Ingres privileges, start Vision from your own account, assuming the identity of the DBA. To do this, use the vision command with the -u option:

Represents the database name. If you are using a PC, you must specify nodename::dbname, which is the name of the remote node on which the database is located.

The -u command option lets you create objects belonging to the user whose name you specify--in this case, the DBA.

• Create a master application owned by the DBA or another user. Developers can create objects in their own versions of the application, in their own accounts. The developers can then use iiexport and iiimport to merge the objects into the master application. The iiimport utility considers all imported objects to be owned by the owner of the master application.