Re: Is a Query langauge really necessary in an OODB?
In article <38E18A9D.1EF87DD7_at_California.com>, Jim McKay
>> I know (from other posts/threads) you don't have much use for
>> an overriding principle of good OO design is: Object shall
>> their own behavior. The current crop of tools have it
>> Rather than the report generator using some method (SQL) to
>> inside my object (record),
>An SQL call is not reaching 'inside your object (record)', it's
making a call
>to (usually) the DB engine. This is not anti OOP.
Are you sure you want to open the messy door about what "OO" is and is not? (The definition seems to be a continuum IMO. IOW, it is not all-or-nothing. For example, many agree that Smalltalk is "more OO" than Java.)
>> my object should create and pass a view of
>> itself to the report generator (which is responsible for
>> the 'generic' capability is not dependent upon a standard
>> of violating encapsulation.
>> Brian Price
- Sent from RemarQ http://www.remarq.com The Internet's Discussion Network * The fastest and easiest way to search and participate in Usenet - Free!