Re: Long Life Objects
- From: timeisfire8@xxxxxxxxxxx
- Date: 28 Mar 2007 03:37:05 -0700
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".
Thank you for your post topmind. I enjoyed reading your website and
these two extracts in particular are what triggered my original post:
-----Quoted from oop.ismad.com
"Also note that in many cases classifications are given by the users
via an interface, and not done by programmers via programming code.
Accountants build and maintain actual accounting code categories for
example, and not the programmers, except in special cases."
"Users often maintain real-world hierarchies, such as product
categories and accounting codes, via hierarchy edit interfaces, and
not programmers writing subclasses. In other words, the hierarchy
nodes are stored in a database, and not in program code."
-----End quotes
My AddressType and Service categories are indeed given by the users
via an interface and I am struggling to find the 'correct' OO way to
handle them.
.
- Follow-Ups:
- Re: Long Life Objects
- From: topmind
- Re: Long Life Objects
- References:
- Long Life Objects
- From: timeisfire8
- Re: Long Life Objects
- From: H. S. Lahman
- Re: Long Life Objects
- From: timeisfire8
- Re: Long Life Objects
- From: topmind
- Long Life Objects
- Prev by Date: Re: OO and Extending (Was: Is Procedural Paradigm a basis of OO Paradigm?)
- Next by Date: Separation of concerns
- Previous by thread: Re: Long Life Objects
- Next by thread: Re: Long Life Objects
- Index(es):
Relevant Pages
|