静态吸气剂/固定器的缺点

Question

I don't know if this question fits this site, but I'll ask anyway: What are the downsides of using static getters? For my website, I use CodeIgniter and I coded a "finder" function in MY_Model.php. The individual Models use this model as a parent and just kind of mirror the database. I would use my finder method to get an object of a model and then with the static getter - also declared in MY_Model.php - get the attributes. Like so:

<?php
$article = Article::find(array(
    'id' => $someId,
));
echo Article::get($article, 'title');

or for example if I have to edit an entry, I can just do it like this:

<?php
$article = Article::find(array(
    'id' => $someId,
));
Article::set($article, 'title', $theTitle)
       ->set($article, 'text', $theText);
if (!$article->update()) {
    return false;
}
return true;

The first real downside I know is, that it completely goes against the 'Thin Controller, Fat Model' principle, since I'd only declare the variables in the model, mirroring the table fields plus maybe some individual functions. But it completely erases the necessity to write getter and setter functions for every attribute.

Answer 1

You could go for magic methods as well and have getters and setters as object methods this way.

However, I don't know if I got the point of your question. In my opinion, what you're trying to do is ORM somehow. ORM is not the same as a Model. Models don't care about things like a persistence layer and reflecting one, they don't even know it.