Difference between revisions of "External schema"
Jump to navigation
Jump to search
| Line 1: | Line 1: | ||
An External schema (also called view schema) is created with the intention to deal with how the end users of a system "view" the data. Thus "external" is differentiated here from the | An External schema (also called view schema) is created with the intention to deal with how the end users of a system "view" the data. Thus "external" is differentiated here from the | ||
| − | conceptual and internal schemas. This is inline with the [https://en.wikipedia.org/wiki/Three-schema_approach Three schema approach] which is also applied in the | + | conceptual and internal schemas. This is inline with the [https://en.wikipedia.org/wiki/Three-schema_approach Three schema approach] which is also applied in the [https://en.wikipedia.org/wiki/Multitier_architecture#Three-tier_architecture Three tier architecture] and a proven and widespread way of designing systems. |
In the following diagram depicting a multitier-architecture. The external schema would be adapted to the Clients, the conceptual schema to the business/application logic and the internal schema to | In the following diagram depicting a multitier-architecture. The external schema would be adapted to the Clients, the conceptual schema to the business/application logic and the internal schema to | ||
the database. | the database. | ||
Revision as of 17:01, 16 February 2023
An External schema (also called view schema) is created with the intention to deal with how the end users of a system "view" the data. Thus "external" is differentiated here from the
conceptual and internal schemas. This is inline with the Three schema approach which is also applied in the Three tier architecture and a proven and widespread way of designing systems.
In the following diagram depicting a multitier-architecture. The external schema would be adapted to the Clients, the conceptual schema to the business/application logic and the internal schema to
the database.
