PHP MVC Model with inheritance?

Question

I am trying to migrate a project into an MVC framework (deciding between CI and Yii).

Now, I have, for the sake of argument, two objects, text and image, which I would like to build based on an object class.

Parent:

class Object() extends Somemodel{
protected $x;
protected $y;
protected $page;
...
methods()...
}

And children:

class Image() extends Object{
protected $width;
protected $height;
...
methods()...
}

class Text() extends Object{
protected $text;
protected $font;
...
methods()...
}

Now as I understand this is a nice approach becasue some common functions like getting x/y coordinates etc. will be placed in the Object while all specific things will be placed in the children classes.

I was hoping to have one table in the database to store the Object.

However frameworks are giving me hard time to try and make it work... which makes me think, that probably I am doing something wrong, because if everyone was doing it like this then, I suppose, frameworks would support that easily.

Any thoughts?

The object you code for your application logic (business models) are independent to database models in CI or YII. You can re-use data in your models that comes from database models however. Maybe that's the missing link? — hakre
– hakre, Commented Oct 4, 2011 at 10:31
Just try DooPHP. It dosnt have any major rules witch you have to folow and its easy to maintain. — Ernestas Stankevičius
– Ernestas Stankevičius, Commented Oct 4, 2011 at 10:34
hakre: Please elaborate (I am fairly new to MVC concept), possibly in a form of an answer so I can accept it if its good :). — RandomWhiteTrash
– RandomWhiteTrash, Commented Oct 4, 2011 at 10:56

Community · Accepted Answer · 2021-01-18 12:34:40Z

3

You should not be doing this. You are violating Liskov Substitution principle (quick picture to explain it), which basically says that you should be able to replace instance of any child class , with instance of parent class.

P.S. this is only my opinion , but i would warn you away from both of the frameworks you mentioned. They both have major design flaws and other issues. (if you want details, visit php chat room .. no point in flaming here)

edited Jan 18, 2021 at 12:34

CommunityBot

11 silver badge

answered Oct 4, 2011 at 10:32

tereško

58.5k26 gold badges100 silver badges151 bronze badges

Sign up to request clarification or add additional context in comments.

Comments

halfer · Accepted Answer · 2011-10-04 10:42:09Z

1

Your question makes sense if one imagines that every framework rolls its own ORM. However I think Symfony had the right idea: integrate with good, separately maintained, ORM systems, so that the core team can concentrate on the framework itself.

So I would look at Propel or Doctrine (both are well-maintained, and both support model inheritance afaik), and then choose your framework based on which offers a good level of integration with your choice of ORM.

answered Oct 4, 2011 at 10:42

halfer

20.2k20 gold badges111 silver badges208 bronze badges

1 Comment

halfer Over a year ago

Incidentally, although I recommend Symfony, I don't intend to suggest that's your only choice. I believe people have got CI to work with both the ORMs I mention, for example.

Collectives™ on Stack Overflow

PHP MVC Model with inheritance?

2 Answers 2

Comments

1 Comment

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

Comments

1 Comment

Your Answer

Sign up or log in

Post as a guest

Related