I agree that it’s nice if the different concerns can be kept separate, but I’m not sure how that would happen cleanly.

For example, with Hibernate, you can already plug in any kind of 2nd level cache, but I don’t know if you could get automatic 1st level caching if it wasn’t built in. And having to manually query and manage a cache on every DB lookup seems tedious and error-prone. And is page caching really the same as entity-caching?

Lazy-loading I don’t see at all how it could be decoupled from your ORM. Who would determine the lazy-loading behaviour and trigger the queries?

By query-batching, I didn’t mean batch jobs, but Hibernate’s ability to group several events (such as updates to a single entity made at various points in a transaction) into a single sql update.

My experience seems to have been the opposite of yours: I’ve found using ORM very easy, and managing hand-rolled SQL very hard (not so much the actual SQL, as the “do I have/need the whole graph?” kind of questions)

In all your anti-ORM posts, I’ve never seen you mention these capabilities. What do you make of them? Are they unimportant to you?

print map{(“Fizz”)[$_%3].(“Buzz”)[$_%5]||$_,”\n”}1..100;

Btw did not code this myself, found it on codepad.

your => you’re
blocked => I’ve blogged