Fujitsu UDS/SQL V2.5 사용자 설명서

다운로드
페이지 324
Coexistence
General information
36
  
 U929-J-Z125-9-76
2.2.4
Coexistence of the CODASYL and relational models 
A decision to use UDS/SQL is not a decision in favor of the CODASYL model and against 
the relational model. UDS/SQL supports both models within a single database system, 
which is consequently referred to as the coexistence model. Both SQL and CODASYL 
applications can work with the same data resources at the same time. 
The coexistence model also provides users with the advantages of both data models: 
a high degree of flexibility in regard to data structures for SQL applications, for example 
through the use of views, 
optimal performance for CODASYL applications and 
monitoring of referential integrity for CODASYL and SQL applications, provided set 
relationships were defined. 
UDS/SQL supports two forms of logical data organization: 
CODASYL data organization with set relationships between the record types 
relational data organization, in which record types are linked only via the contents of 
specific record elements 
The SQL interface to CODASYL data structures is supported by the BPSQLSIA utility, 
which generates a relational view for practically all of the system’s CODASYL structures 
(see the “
” manual). This is necessary because 
SQL statements require the use of explicit data elements which do not exist in the 
CODASYL database description; in the relational database description, primary keys are 
added to all owner record types, and foreign keys are added to member record types. 
The generation of the relational data description by the BPSQLSIA utility does not physi-
cally change the database. The additional data elements (primary keys and foreign keys) 
exist only logically. As the result of the generation, SQL application programmers receive 
a printout containing all the information needed to process a CODASYL database with SQL 
(e.g. table names, record element names, record element descriptions, etc.). SQL appli-
cation programmers can work exclusively with the relational schema, yet the CODASYL 
schema remains unchanged and available for use by CODASYL applications.