Sujet : Re: VMS x86-64 database server
De : ldo (at) *nospam* nz.invalid (Lawrence D'Oliveiro)
Groupes : comp.os.vmsDate : 12. Jul 2025, 01:35:37
Autres entêtes
Organisation : A noiseless patient Spider
Message-ID : <104sako$1p3b8$5@dont-email.me>
References : 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24
User-Agent : Pan/0.162 (Pokrosvk)
On Fri, 11 Jul 2025 19:43:59 -0400, Arne Vajhøj wrote:
The main point of ORM is to avoid boilerplate code like iterating and
result sets and stuff them into the object data structure.
Those are just up to the DB API, taking advantage of features of the
language. Like the query iterator I posted elsewhere.
The point of the ORM is supposed to be to get away from SQL altogether,
and let you operate in terms of language-native objects.
Some ORM's operate with a dirty concept and automatically save changed
objects.
How do you map between OO objects and SQL tables? That’s called the
“impedance mismatch”, which tends to cause more problems than it solves.
Some ORM's provide identical syntax for doing things even though the
underlying databases have different SQL syntax for it, which help making
the application more portable.
More commonly you want to support different programming languages
accessing the same back-end DBMS containing the common enterprise-wide
data, rather than move a program between different back-end DBMSes. ORMs
are language-specific, so they don’t help with that.