Actually I'm suggesting that the mapping is highly custom to the specific project to the point where a comprehensive framework is not possible. The attempts to accommodate all of the nuances and edge cases just makes for a gigantic mess in the middle.
It also violates both encapsulation and loose coupling, which to me makes it a non-starter in the first place. Automatic updating of the mappings tries to hide this but it just adds even more complexity to the mess.
ORM is the product of architecture astronauts who thought regular old database interactions were beneath them and their mad architecture skillz.
Typical web application schemas are very basic compared to even simple business application schemas.
The ORM gun, so to speak, can kill a squirrel but will just piss-off a bear.
