Jump to content

Help with DAO design pattern


carlg

Recommended Posts

I'm trying to create some PHP code and I'm trying to cleanly organize everything.

Let's assume I have an account object.  I'm trying to figure out (from a design perspective) the best way to do this:

 

Here is approach #1.

 

class Account {
      public $id;
      
      function getAccounts ()
     {
          // I know this code doesn't work, but it demonstrates the point
           mysql_query ("Select * from Account");
     }
}

 

 

Approach #2:

or is is better to have the getAccounts in a separate DAO class (called AccountDAO) so in my main program I would declare an Account object and an AccountDAO object?

 

I'm really trying to figure out the preferred way to structure my application.

 

 

 

Link to comment
Share on other sites

This thread is more than a year old. Please don't revive it unless you have something important to add.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.