Re: Object-oriented thinking in SQL context?

On Jun 9, 7:53 am, Jan Hidders <hidd..._at_gmail.com> wrote:
> On Jun 9, 3:27 pm, Bernard Peek <b..._at_shrdlu.com> wrote:
>
>
>
> > In message
> > <61940522-4566-4b27-be4f-ad8afcbf8..._at_o18g2000yqi.googlegroups.com>,
> > cim..._at_hotmail.com writes
>
> > >Snipped
>
> > >> The database community can handle this in a couple of ways:
>
> > >> 1) Close in on yourself and mock people who do not have the
> > >>    insights you have.
> > >> 2) Recognize the problem and help sort out the misunderstandings
> > >>    and snags.
>
> > >> Over the past couple of days I have got a clear impression about
> > >> what approach seems to be preferred by the regulars here.
> > >Let me get this straight.  You need help from the database community
> > >for a design exercice but you need that help to be done according to
> > >the principles you believe are universal (whatever these may be).  All
> > >I have seen so far are goodwill people who wanted to help you by
> > >advising you to do some reading necessary to understand some basic
> > >principles of database design.  In a word, you ask a question and
> > >because you don't like the answer you now imply that the *regulars*
> > >have closed themselves and mocked you.
>
> > >Don't you think this is a hasty harsh judgment on your part ?
>
> > I've been reading and posting to this newsgroup on and off for years. I
> > think his analysis is pretty accurate.
>
> Unfortunately it is.
>
> -- Jan Hidders

Lemme add my voice to the amen chorus.

"i don't know anything about quantum mechanics I only know about how to build a chicken hutch can you guys help me understand background radiation and hawking radiation and stuff and please use words i know from build chicken hutches" Received on Tue Jun 23 2009 - 04:30:13 CEST