Impedance mismatch is basically the term used to refer to the problems that basically occurs due to differences between the database model and the programming language model. The practical relational model basically has 3 components these are:
- Attributes and their data types
Following problems may occur due to the impedance mismatch:
- The first problem that may occur is that is data type mismatch means the programming language attribute data type may differ from the attribute data type in the data model.
Hence it is quite necessary to have a binding for each host programming language that specifies for each attribute type the compatible programming language types. It is basically necessary to have different data types, for example, we have different data types available in different programming languages such as data types in C are different from Java and both differ from SQL data types.
- The second problem that may occur is because the results of most queries are sets or multisets of tuples and each tuple is formed of a sequence of attribute values. In the program, it is necessary to access the individual data values within individual tuples for printing or processing.
Hence there is a need for binding to map the query result data structure which is basically a table to an appropriate data structure in the programming language. A mechanism is needed to loop over the tuples in a query result in order to access a single tuple at a time and to extract individual values from the tuple.
The extracted values are typically copied to appropriate program variables for further processing by the program.
A cursor or iterator is a variable which is basically used for looping over the tuples in a query result. Individual values within each tuple are basically extracted into different or unique program variables of the appropriate datatype.
Impedance mismatch is less of a problem when a special database programming language is designed that uses the same data model and data type as a database model for example Oracles’sPL/SQL.
Example – UGC NET CS 2016 Aug – III | Question 7
- DBMS | Advantages of DBMS over File system
- Need for DBMS
- Starvation in DBMS
- Deadlock in DBMS
- Disadvantages of DBMS
- DBMS | Interfaces
- DBMS | Log based recovery
- DBMS | Conflict Serializability
- DBMS | Nested Queries in SQL
- ACID Properties in DBMS
- Last Minute Notes - DBMS
- DBMS | Recoverability of Schedules
- DBMS | OLAP vs OLTP
- DBMS | Why recovery is needed?
- DBMS | Schema Integration
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.