What ORMs have taught me: just learn SQL (2014)

Re:What ORMs have taught me: just learn SQL (2014) by PeCaN on Sunday June 26, 2016 @07:29PM (#11983339)

> If you write some code, then you have just written an ORM.

What? No, I've written code to query a database. Not an Object-Relational Mapper.

  my $q = $db->prepare("get_my_stuff_by_name(?);");
  $q->execute($name);

or with fancy metaprogramming:

  use DBMagicStuff 'postgres://…';
  get_my_stuff_by_name($name);

That's not really an ORM.

[ Parent | on HN ]

Re:What ORMs have taught me: just learn SQL (2014) by intrasight on Sunday June 26, 2016 @08:46PM (#11983589)

You are both partially right. An ORM deals with the black magic of connections, parameters, transactions, etc. If you don't use an ORM, then you still have to deal with those semantics. But I do agree that you aren't writing an ORM.

[ Parent | on HN ]

Re:What ORMs have taught me: just learn SQL (2014) by PeCaN on Sunday June 26, 2016 @09:07PM (#11983651)

> connections, parameters

The database driver takes care of that, not the ORM.

(It's also not black magic.)

> transactions

Huh? That's a database feature. BEGIN/COMMIT/ROLLBACK are ANSI SQL.

ORM is an _Object Relational Mapper_. You're confusing it with a database driver (or, in the case of transactions, just a database in general).

[ Parent | on HN ]