Magento Stack Exchange is a question and answer site for users of the Magento e-Commerce platform. It only takes a minute to sign up.
Sign up to join this community
Is it appropriate for a Block class to retrieve data through a function in a ResourceModel class, rather than a Model class?
Or should the Block call the Model which then passes the call to the ResourceModel?
Going direct from Block to ResourceModel is simplest and avoids duplication of possible quite a few functions, but would you consider it to be bad form, breaking best practice patterns?
This is perfectly acceptable. In fact, other than instantiating Resource Models in controllers, this is how it's intended to work. A Resource model is a special type of Model in Magento - one that populates its data from a data source.
If you examine Magento core you will see many instances of using Resource Models in Blocks. Many times you don't realize that's what's happening because often this is written like:
Mage::getModel('catalog/product')->getCollection();
A block's method will provide it to the template to utilize - usually to iterate.
Mage::getResourceModel('log/visitor')->getStartOfLog() in a Block? Would that not bypass the (domain) Model layer?
– fris
Jul 5 '15 at 3:58
Theoretically, I think it's bad form because someone could have changed the resource model class (very unlikely). But it depends. One practical example is the category and product resource models (and resource collections). If you instantiate them directly, you might not get the appropriate model (flat or normal). I think that's the only instance of where it would actually matter though.
