Re: The wisdom of the object mentors (Was: Searching OO Associations with RDBMS Persistence Models)

I don't see how the issue of proprietary SQL is any different than a proprietary app language. How is being married to Java worse than being married to Oracle? Your argument seems to be "we will use a prioprietary app language to wrap/escape a proprietary query language". You cut off your left hand to save your right hand.

The query/SQL house indeed needs a lot of cleaning, and perhaps an overhaul. However, the alternatives are grappling with similar problems.

The fact that SQL is somewhat standardized is a *bonus*, not a fault. I've had to switch and learn new programming languages often enough that it is not fun anymore. However, one of the few semi-constants is SQL. I change app language but SQL is there almost just as it was in the with last app language that fell out of style.

If OO'ers had their way, they would probably fracture the query market the same way they fractured the GUI market -- a different GUI engine for each different OO language. OO API's have failed to find a way to be app-language neutrual (without bloated verbose adaptors).

-T- Received on Wed May 31 2006 - 18:50:20 CEST