Re: The term "theory" as in "database theory"
Date: 27 Jan 2007 08:59:27 -0800
Message-ID: <1169917167.330553.205190_at_h3g2000cwc.googlegroups.com>
On Jan 27, 8:11 am, "JOG" <j..._at_cs.nott.ac.uk> wrote:
> Dawn wrote:
> > JOG wrote
> > > I still await a
> > > post without any agenda, or baiting, or getting drawn into business
> > > politics -
> > OK, it sounds like database theory is a profession that might want to
> > have no users or at least users with no requirements, right? ;-) IMore baiting. The 'harlequin' syndrome?
>
> > could use some of those myself. There is that joke about the librarian
> > who said that it was a wonderful day for the library because there were
> > only two books checked out and they were both due today. Maybe we
> > could write a similar joke about a database theorist? Just wondering
> > if I'm getting the picture.It doesn't look like you are. I would like to see posts from you
> without any agenda, or baiting, or getting drawn into business
> anecdotes. Should I not be holding my breath?
Dag nab it, mAsterdam -- I swear I posted this question in an attempt to start with the basics and not bring any opinions in until I was at the point of dialog with others. I didn't include any opinion in the OP at all, and agreed with many of the opinions of others on what I thought "theory" meant as in "database theory" -- but not until I heard the responses did I voice my own opinion. What would have been a more rigorous way to address this? I'm starting with the very basics of trying to understand the term "database theory."