[aus-dotnet] Many instance variables inside a class

[Grant Maw]

Hi all

I have a situation where I have a class called "Person" which, rather
obviously, holds the data and methods for working with the Person
entity in our app.

The DB entry for a person has some 70 columns and this has translated
into 70 properties of the Person class. There is one method to load
the data rom the DB, and another to update it. The update method does
all the validation and throws exceptions if any of the data violates
business rules.

The class works well so maybe I'm over-reacting here, but having a
class with such a large number of properties just feels wrong. I
haven't found anything in MSDN that explicitly deals with this
situation.

Is there a better way of dealing with situations where an entity has
lots of different properties?

Cheers

- Grant
_________________
You are a part of the Australian "dotnet" mailing list.
To unsubscribe send "unsubscribe dotnet" or to re-subscribe send "subscribe dotnet Your Name" in the body of the email to: imailsrv@xxxxxxxxxxx
List managed by: http://www.stanski.com