Content deleted Content added
m Comp.arch moved page Talk:Object-relational mapping to Talk:Object–relational mapping |
No edit summary |
||
Line 3:
==Introduction==
"This creates, in effect, a "virtual object database" that can be used from within the programming language." I don't think this is the only way for ORM mechanisms/frameworks/tools. Instead, I will say that this is a common implementation for ORM solutions. "Mapping" as relating objects to rows could be solved by creating "hybrid" objects (objects with PK or FK attributes), but also with a real external mapping without changing or mixing ___domain classes with records. [[Special:Contributions/63.128.77.30|63.128.77.30]] ([[User talk:63.128.77.30|talk]]) 17:00, 16 March 2015 (UTC)
"technique for converting data between incompatible type systems" sounds like a contradiction in terms. Compatible means two types are able to be converted between, so if they're incompatible, you can't convert between them.
==Relational vs. Non-Relational==
| |||