Re: Retrieving unnecessary data
- From: topmind <topmind@xxxxxxxxxxxxxxxx>
- Date: Thu, 14 Feb 2008 13:00:13 -0800 (PST)
On Feb 14, 11:26 am, ShaneLM <shane.nieberg...@xxxxxxxx> wrote:
I'd like some advice on how to structure my classes. Let me use an
example to convey my situation. Pretend I am modeling a Car.
Class Car
{
String make;
String model;
Enum color;
List<People> passengers;
}
My problem arises because sometimes I'm just interested in the stats
of the car, and not the people in the car. Although in other
situations I do care about the people in the car.
If I'm writing a database access method, say GetCar(), I feel like
time is wasted retrieving info about the passengers that I will never
use in some situations. So I feel like I have a few alternatives:
A) Return the class with all fields filled out, regardless of whether
they will be used or not. This is OO, right?
B) Create overloads for GetCar where I indicate whether I want all
fields filled out for me. Ex: GetCar(bool fill_passengers);
C) Remove the passengers field, and retrieve them with another call.
I'd call GetCar(), and then if I want the passenger list, I'd call
GetPassengers(Car);
D) Make 2 classes - Car and CarWithPassengers (that can derive from
Car).
Does that make sense? I know it doesn't sound like retrieving a
passenger list is expensive, but I'm trying to keep this example
simple. Consider if the People class had lots of nested classes inside
of it, and all we wanted to know was the person's name? Same situation
occurs...
Which alternatives do you prefer? Is there anything else you would
suggest?
Thanks so much!!
Shane
These are the kinds of problems one encounters when they try to use
OOP to model domain nouns. Modeling domain nouns for business apps is
a road to bloat, hell, or both.
And, I've encountered OO fans who agree with me on this point. They
feel that OO is best used for things like GUI's and reporting idioms,
not domain nouns.
Let the DataBase model the domain nouns (business things) and get
*only* what you need from the DB for any given task. Life will be
simpler.
-T-
oop.ismad.com
.
- Follow-Ups:
- Re: Retrieving unnecessary data
- From: Robert Martin
- Re: Retrieving unnecessary data
- From: ShaneLM
- Re: Retrieving unnecessary data
- References:
- Retrieving unnecessary data
- From: ShaneLM
- Retrieving unnecessary data
- Prev by Date: Re: object-oriented programming explained in 51 lines
- Next by Date: Re: object-oriented programming explained in 51 lines
- Previous by thread: Re: Retrieving unnecessary data
- Next by thread: Re: Retrieving unnecessary data
- Index(es):
Relevant Pages
|
