Unified Database Language (UDL) is language that supports all three of the well known approaches – relations, hierarchies, networks in a uniform and consistent manner. It is not a self-contained language, rather it is explicitly intended as “tightly coupled” set of database extensions to existing programming languages such as COBOL, PL/I. Mostly PL/I is used for implementation.
It is independent on any one specific host programming language, it can be incorporated into a variety of programming languages with suitable syntactic modifications. In addition to supporting all three approaches UDL also provides both record-at-a-time and set-at-a time operations for each of them as shall we see.
- The set level is desirable for reasons of productivity and ease of programming.
- The record level serves as bridge to existing function in the host language.
Unified Database Language :
- Information Sytem
- Data management System
- Database Design and Models
- Query languages
- Theory of Computation
- Theory and algorithms for computer domains
- Database Theory
- Database Query languages (Principles)
- Self-contained language.
- Use of existing programming languages.
- Independent of a host programming language.
- Easy to use and flexible.
- The Software Architecture Must Be Communicated Effectively.
- Use of limited languages.
- Formal Notation is Not Necessary
- Less information is available on different domains of UDL as research is going on.
- Ascending Degree of Complexity.
Attention reader! Don’t stop learning now. Get hold of all the important CS Theory concepts for SDE interviews with the CS Theory Course at a student-friendly price and become industry ready.
- Software Engineering | Database application system life cycle
- Software Testing | Database Testing
- Difference between Database Testing and Data warehouse Testing
- Development Phases of Database System
- Software Engineering | Introduction to Software Engineering
- Software Engineering | MOCK (Introduction)
- Client-Server Software Development | Introduction to Common Object Request Broker Architecture (CORBA)
- Introduction of Software Design process | Set 2
- Introduction to Pervasive Computing
- Introduction To Malware Analysis
- Introduction of JIRA
- Introduction to Mercurial
- Introduction of Technical Report
- An Introduction to Software Development Design Principles
- Introduction to Business Process Re-engineering
- Introduction of Test Artifacts
- Refactoring - Introduction and Its Techniques
- Introduction of Holdout Method
- Introduction to ERP
- Introduction to Exploratory Style of Software Development
If you like GeeksforGeeks and would like to contribute, you can also write an article using contribute.geeksforgeeks.org or mail your article to email@example.com. See your article appearing on the GeeksforGeeks main page and help other Geeks.
Please Improve this article if you find anything incorrect by clicking on the "Improve Article" button below.