I've never been able to fully understand this drive, beyond the obvious. If you want object-relational access, write stored procedures.

It appears from the ORDB argument and from the primary arguments against stored procedures, that many of the folks that develop software and create the need for databases don't seem to understand that the data, although used by their application, perhaps even the primary driver for the storage of the information, are not the owners of that information. And the owner of that information may have other uses for that data beyond the scope of the original application. Enterprise Data Warehousing being one example. Manufacturing Automation, although less obvious, being another.

I can see where someone might create a wizard or some other technology similar to the query analyzer that will recommend or even automatically configure OR functions (.Net or Java?) or stored procedures, but to sacrifice orthoganility for the convenience of the developer--? Isn't that rather short-sighted?