Talk:ADO.NET Entity Framework
From Wikipedia, the free encyclopedia
"The disadvantage of this approach is that if this schema is changed the application is not shielded from the change."
This is not the disadvantage of tying app code to db schema, this is a myth. DB schemas should NOT change in ways that break apps. And if/when they do (such as during development), it's probably because the app is required to change accordingly, so being "shielded" from the change is besides the point.
The greatest disadvantage of code being tied directly to the db schema model is cognitive: db physical schemas rarely represent the domain model well, yet the latter is what we'd like to work with in OO code.
[edit] Better Word Than "Format" ?
"It is geared towards solving the mismatch between the formats in which data is stored in a database and in which it is consumed in an object-oriented programming language or other front ends."
I think "formats" is the wrong word. It goes beyond what most people think of as formatting. Better would be something like "architecture", or "organizational structure", etc.
Larry Leonard (talk) 22:42, 8 April 2008 (UTC)
