Making PHP Classes Play Nicely With Each Other (OOP Pattern Question)

[centenial]

Hi all,

 

I have a PHP OOP design question. I've done some searching in google, but wasn't able to turn up anything concrete. I'm hoping some experts can point me to the most elegant solution.

 

I have a set of classes. All of my classes "extend" an abstract class called Base. (This class reads a config file, has a basic set of common methods, and sets up needed parameters)

 

Most of my classes need a class called Mysql to perform database operations.

 

Is the best way to access the Mysql class to pass it in the __constructor in each of my child classes, or to instantiate it in my Base class, and assign it to a public property? Or perhaps there is a better way altogether?

 

I'm really looking for the best way to do this, so thanks in advance for your advice!

 

 

[corbin]

A singleton or registry is usually how I get my DB object.

[Liquid Fire]

Personally i prefer the singleton pattern over the registry pattern and all my singleton pattern have a static get instance() method.  I never got what the registry pattern provide as a benifit over the singleton pattern.

[keeB]

I usually have a BaseDao class which contains the connection to my database. All of my Data(base) Access Objects extend from BaseDao which contains methods like: find(), findUnique(). UserDao (an extension of BaseDao) would defined methods like: getUser(User $person) { $this->findUnique($person); }