Re: Long Life Objects

On Mar 27, 1:45 pm, timeisfi...@xxxxxxxxxxx wrote:
Hi Lahman
Thanks for responding. I enjoy reading your posts and understand at
least 9% of them with my current knowledge :-)

What problem is the application trying to solve?

It is a warehouse application that includes a basic contact management
element. One Use Case extract might be "A Customer Contact phones the
Company to order a next day delivery Service for a stored pallet of
goods."

I am getting hung up on the terminology here (e.g., "Dictionary"). It
sounds very much like you are trying to emulate an RDB and the
Dictionaries are just surrogates for table indices.

So I am. One of your other posts taught me the valuable lesson of
solving the problem without considering RDB persistence, which should
be handled in isolation.


Well, you have been taught bullsh8t from excessive OOP zealots. And
RDB's are not just about "persistence". They standardize and package
common attribute-management and collection-oriented idioms, AKA
"reuse".


Before this I would drive the design from the
database and I now see how this is a poor approach. I suppose that the
reason I have unwittingly created an application RDB is because my
thought process for the implementation of the Use Case above, for
example, is:

[snip]



-T-
oop.ismad.com

.

Relevant Pages

  • Re: Zinda
    ... rkusenet wrote: ... First you have to prove that AP walked out RDB and watched ... Take his urine, or my crap now. ... You just can't desist from such statements in any of your posts, ...
    (rec.arts.movies.local.indian)
  • Re: Searching OO Associations with RDBMS Persistence Models
    ... The problem is that not all OO purists agree to this. ... I suggest that you read the posts from HS Lahman in this thread. ... An RDB has a lot of behvior too, integrity checking, transactions, etc. ...
    (comp.object)