Database Impedance Mismatch

[From ImpedanceMismatch.]

Database ImpedanceMismatch:

(In our community, "ImpedanceMismatch" refers to database issues more often than electrical issues. -- JeffGrigg)

[with Object Oriented languages...]

See ObjectRelationalMapping for more information.

See the white paper "Mapping Objects To Relational Databases" by ScottAmbler for a detailed explanation of these issues:

Examples: Unfortunately, the article and the author suffer from impedance mismatches themselves. Readers beware and learn to distrust the "impedance mismatch" kind of people. The profound root of the issue is a severe ObjectRelationalPsychologicalMismatch, which basically says that many "object gurus" are complacent in a very superficial understanding (if it can be called that way) of relational databases, and on the larger scope of what ComputingScience is about. Illustrative from that article:

Why does a technological impedance mismatch exist? The object-oriented paradigm is based on proven software engineering principles. The relational paradigm, however, is based on proven mathematical principles. Because the underlying paradigms are different the two technologies do not work together seamlessly.

Of course to suggest that mathematics and software engineering are in such a dire conflict that they give birth to impedance mismatch, is utterly ridiculous. See ProgrammingIsMath.

The article is also littered with confusions and bad terminology (meaning not adhering to the consecrated terminology in databases, but rather one's own redefinitions). For example what is there considered "physical data model" is properly called "logical data model", or even simpler "logical schema", or just schema.

[General issues, with all host languages...]

See RelationalHostLanguageImpedanceMismatch, ObjectRelationalPsychologicalMismatch, TablesAndObjectsAreTooDifferent, ObjectRelationalImpedanceMismatch, TrueRelationalToPseudoRelationalImpedanceMismatch

View edit of November 28, 2008 or FindPage with title or text search