[go: nahoru, domu]

Jump to content

Data independence

From Wikipedia, the free encyclopedia

This is an old revision of this page, as edited by 201.243.206.245 (talk) at 18:51, 23 April 2005. The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

(diff) ← Previous revision | Latest revision (diff) | Newer revision → (diff)

It is only the type of data transparency that is important within the context of a centralized DBMS. It refers to the immunity of user applications to changes in the definition and organization of data, and vice-versa.

There are 2 levels of Data Independence:

First Level The logical structure of the data and is known as the schema definition. In general, if a user application operates on a subset of the attributes of a relation, it should not be affected later when new attributes are added to the same relation.

Second Level The physical structure of the data and it is referred to as physical data description. Physical data independence deals with hiding the details of the storage structure from user applications. The application should not be involved with these issues, since there is no difference in the operation carried out against the data.