Package com.sas.metadata.remote

Interface SecuredTable

All Superinterfaces:
Classifier, CMetadata, DataTable, MdObjectBase, MdObjectBaseUtil, MdObjectBaseXML, PhysicalTable, PrimaryType, RelationalTable, Remote, Root
public interface SecuredTable extends PhysicalTable
A SecuredTable object is created for a physical SAS data set when a data set with the same name is first created in a metadata-bound library. Subsequent data sets created with the same name will find and bind to an existing SecuredTable object under the SecuredLibrary object. The location of the SecuredTable object is stored in the physical SAS data set such that the SAS system will not access the SAS data set without first establishing an authenticated identity and connection to the metadata server and obtaining the identity's data permissions for this object. These data permissions then determine what actions the SAS system will allow that identity to perform on the physical data. SecuredTable objects should not be created or manipulated by any code other than the AUTHLIB procedure or the SAS I/O subsystem. The physical data will not be accessible if an existing SecuredTable object is modified by other means.

Attributes of SecuredTable are:

Associations of SecuredTable are:

Usage

To create an instance of this SecuredTable, use the factory create methods.
Example: create a SecuredTable with name "SecuredTable_Object", in repository "AAAAAAAA".
 // create a store to contain your objects for this change. If you do not have an existing object
 // or store to use.  You may obtain the store from another object by using Object.getObjectStore().
 MdFactory factory; //where "factory" is a valid MdFactory instance
 MdObjectStore objectStore = factory.createObjectStore();
 SecuredTable myObject = (SecuredTable) factory.createComplexMetadataObject(objectStore, "SecuredTable_Object", MetadataObjects.SECUREDTABLE, "AAAAAAAA");
 myObject.updateMetadataAll();  // Write object to server
 objectStore.dispose();  // dispose of the object store if it is no longer needed

Behavior

  • Attributes and associations for this object can be retrieved by using the methods in MdOMIUtil.
  • When changes are made to the object, either by setting an attribute or adding objects to a particular association, they can be persisted to the metadata server with the updateMetadataAll method.
  • If an object needs to be deleted, the delete method can be used. This will flag the object as being deleted on the client, and will require an update call to persist the change to the server.

Dependencies

This class depends on objects being contained in an MdObjectStore. Object stores should be disposed of when they are no longer needed as this will help clean up memory. Disposing an object store will dispose of all objects contained within that store.

Since:
9.0