Best way to design OO classes

[eluser]mihailt[/eluser]
in my point of view, you need to define your Customer class, and model will be responsible for fetching,processing and saving changes. in simple words you need to follow Data Mapper pattern.

so in model you would have methods like, fetch($params),proccess($object),save($object).
and your customer class would probably be a custom data type, with get and set methods.

that way there will be no difference with working with one customer entry or many.

take a look at this link : http://martinfowler.com/eaaCatalog/dataMapper.html