Design pattern to handle queries using multiple models
- by coderkane
I am presented with a dilemma while trying to re-designing the class structure for my PHP/MySQL application to make it more elegant and conform it to the SOLID principle.
The problem goes like this:
Let as assume, there is an abstract class called person which has certain properties to define a generic person, such as name, age, date of birth…
