What ORMs have taught me: just learn SQL

Re:What ORMs have taught me: just learn SQL by zak_mc_kracken on Tuesday August 05, 2014 @08:43AM (#8136578)

ORM is "Object Relational Mapper".

If you are taking data out of a relational database and mapping it into objects, you are implementing an ORM.

Seems like I'm sticking to the exact definition of an ORM, aren't I?

[ Parent | on HN ]

Re:What ORMs have taught me: just learn SQL by dragonwriter on Tuesday August 05, 2014 @10:08AM (#8136936)

> If you are taking data out of a relational database and mapping it into objects, you are implementing an ORM.

No, ORM is a particular approach to doing that; the query abstraction approach described upthread is closer to the DAO pattern, to which ORM is an alternative. People were using RDBMSs to provide a persistence layer for OO programs before ORM was a thing, but as you have broadened the term any use of an RDBMS to store/retrieve data used in an OO program would be "ORM".

[ Parent | on HN ]

Re:What ORMs have taught me: just learn SQL by zak_mc_kracken on Tuesday August 05, 2014 @07:58PM (#8140221)

Now you're the one using a nonstandard definition of ORM. Here is how Wikipedia defines it:

    Object-relational mapping (ORM, O/RM, and O/R mapping)
    in computer science is a programming technique for
    converting data between incompatible type systems
    in object-oriented programming languages.

[ Parent | on HN ]

Re:What ORMs have taught me: just learn SQL by dragonwriter on Tuesday August 05, 2014 @08:06PM (#8140251)

"is a technique for" does not mean "includes every technique for".

Spearfishing is a technique for catching fish, but not every technique for catching fish is spearfishing.

[ Parent | on HN ]