Specifically, Vic feels that using an ORM framework to write SQL just wrenches too much control out of the developer's hands, and ties said hands too tightly to one (not necessarily long-lived) ORM system. Excerpted, his objections come down to these:

Using an ORM feels clunky, slow, vendor-locked, and difficult to debug. Additionally, with any system of size, you are going to have to write some large SQL queries. I feel mixing ORM code and hand-written SQL is ugly...

I do not buy into the argument an ORM lets you switch databases easily. The ORM might facilitate that, but I have never worked on a project of any non-trivial size that after being put into production had its database changed. My fulltime job has a PostgreSQL database with 550+ tables, 220+ stored procedures, and 110 or so triggers. Migrating that to different database software would never happen.

It's worth noting that Vic doesn't object to ORM in principle, so the mapping itself doesn't locate his concern. Rather, he says, the practice of writing complex SQL is, at the moment, something ORM's just can't handle. (This parallels my experience with MSAccess, incidentally, even in relatively small (~100 tables) databases.)

But not all queries are that complex. And the PHP Data Object (PDO) syntax can sometimes get a little verbose for really basic querying. So instead of using ORM for the simple and hand-coding the complex -- a chemistry disaster waiting to happen -- Vic created a very small wrapper to make simple queries much easier.

The rest of the code is freely available on his site, along with one example of a controller action that reads much more like scalar data access than like object-oriented anything. Definitely worth filing away for the future.