RE: Suggestions for class design

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Anas Mughal <mailto:anasmughal@xxxxxxxxx>
    on Monday, September 19, 2005 4:02 PM said:

> The simplest way to solve this problem is as follows:
> 
> - Have your Customer class hold only attributes for a customer. This
> class would only have getter and setter methods. In the Java world,
> this is referred to as a JavaBean.  
> - Then, have a DAO class that does your data access functions.
> 
> Here is a sample DAO class:
[snip]

Ahh.. I guess this is the same thing that Michael Sims suggested?

> class CustomerDAO {
> 
> 
> function getCustomer(..) {
> ...
> //return a customer
> }

So I return a Customer object that has the set and get methods? And does
that mean I do the following?

->set_first_name()
->set_last_name()
->set_address_1()
->set_address_2()
->set_address_3()
->set_city()
->set_state()
etc.

Or is there a better way to handle it?

> function getCustomers(..) {
> ...
> // return a collection of customers
> }

How do I return a collection of customers?



Thanks,
Chris.

-- 
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php



[Index of Archives]     [PHP Home]     [Apache Users]     [PHP on Windows]     [Kernel Newbies]     [PHP Install]     [PHP Classes]     [Pear]     [Postgresql]     [Postgresql PHP]     [PHP on Windows]     [PHP Database Programming]     [PHP SOAP]

  Powered by Linux