所有的扩展不需要任何更改都可以运行在magento1.6上.并且magento可以运行在各种RDBMS(关系型数据库)上,不单单只支持mysql了.
题外话:Magento1.6已经不支持旧的演示数据
As far as Magento 1.6 adds support for more RDBMS (not only MySQL) and makes using DB more abstract, the ‘Mysql4′ resource models were renamed to the ‘Resource’ models. Same way Core modules renamed the nodes in config.xml, that they are using to resolve alias (e.g. ‘catalog/product’) to find out real class name (e.g. Mage_Catalog_Model_Resource_Product).
The usual place for resource models information in Magento 1.6 is ‘global/models/{module}_resource’, while in Magento 1.5 it was ‘global/models/{module}_mysql4′
The only possible problem there could be with customizations/extensions, that overwrite Core resource models by placing ‘
Now Magento not only checks the resource model node, but also checks path in ‘
Starting from Magento 1.6 the recommended practice is to use ‘global/models/{module}_resource’ nodes in config.xml to overwrite Core resource models. However extension developers are free to use old paths too, and Magento will find and correctly use that models. This change is backwards compatible and doesn’t require any modifications from extension developers.
P.S. The original conversation was about node paths. But more information about resource models is asked there. In fact, resource models are backwards compatible too. The newer abstraction engine allows to write cross-db compatible resource models. However, all old operations (methods) are left, and extensions, that do not care about cross-db-compatibility, can use them to issue direct SQL queries. So, older extensions are compatible with newer RDBMS scheme.
原文请见:http://www.magentocommerce.com/answers/What-do-I-Need-to-do-with-my-Model-Resources-for-the-Magento-1.6-Release/
