Re: Mixing OO and DB
Date: Fri, 29 Feb 2008 12:10:55 GMT
"Marshall" <marshall.spight_at_gmail.com> wrote in message
> On Feb 28, 2:37 pm, Patrick May <p..._at_spe.com> wrote:
> > Tegiri Nenashi <TegiriNena..._at_gmail.com> writes:
> > >> For one thing, it decouples the application code and the
> > >> database schema. For another, as noted by Mr. Martin, it allows
> > >> the creation of a domain specific language that better reflects the
> > >> concepts in the problem and solution domains.
> > > Sure Mr. Martin is working on a "domain specific language" that
> > > would put SQL to shame?
> > Do you consider SQL to be the best possible language for all
> > problem and solution domains?
> Certainly not. SQL is only good for data management.
Can you help me out here, Marshall? My first take on your comment was that it was sarcasm. But then I thought that maybe you're not being sarcastic, and there's a serious thought here. I've always considered you a serious participant in the newsgroup.
I remember back when I first started reading you in cdt. You were, by your own assessment, somewhat ignorant about data management at that time, a "purebred programmer in recovery" in my words. I'm even more ignorant about OOP than you were about data management years ago. I read a few books, wrote a few trivial programs, and moved on.
My question is, "aside from data management, what else is there?" My intent is neither rhetorical nor sarcastic, although it's probably going to draw a torrent of snide repsonses from both cdt and co.
A little while back, I suggested that there are three things you can do with data that add value:
- You can store it.
- You can forward it.
- You can transform it.
As I see it, "data management", broadly interpreted, affects all three of the above. And combinations of these three describe all of computing, as near as I can tell. What am I missing?
Received on Fri Feb 29 2008 - 13:10:55 CET